phantomtypist

@sunnymoon my plan is to support whatever we can. Starting in version 1.1.0 of this project, we now support multiple target frameworks in the .NET CAS Client. Any of these...

To clarify, if you open the 1.1.0 version of this projects' nuget package, you'll see that there are four distinct assemblies in it, each compiled for a different target framework....

See my response on #84.... similar. Make separate repo for each of the tertiary NuGet packages. This way they are isolated both by code and contributors. We could end up...

We just have to agree on naming of the repos as per my comment in #84.

@TheHokieCoder I had @mmoayyed set up the new repos. The SQL Server service ticket provider will live over in https://github.com/apereo/dotnet-cas-client-mssql I'll scaffold out the project shell, solution, build scripts, AppVeyor...

@TheHokieCoder any progress on the MSSQL distributed cache provider?

That's okay, I've been MIA too. In no specific order: - Table names: I looked at some other implementations from other languages and it looks like the two tables (proxy...

^ w.r.t. the implementations take a look at the [release/1.0 branch](https://github.com/apereo/dotnet-cas-client-memcached/tree/release/1.0) and look at what I did for the two classes (proxy and service tickets.) An interesting problem I ran...

Good catch, I wrote it too quickly. `cas:MSSql:ConnectionStringName` is what I meant to say. As for the ticket character length it just so happened to be that my org has...

@TheHokieCoder FYI I think I have to quickly touch-up the Cake build script in the develop branch for you since Cake evolved a hair since I first put it in...