I have a ton of work that I started on .NET CAS client for .NET 4.5+ but I was never able to get it completed. I probably over-ambitiously attempted to maintain backward compatibility w/2.0 and it ends up being a little over-engineered as a result. I've been meaning to setup a branch for it. It still needs work + volunteers. I'm totally swamped and haven't had any time to dedicate to it lately.
I can share details for pushing updates to NuGet. On Wed, Nov 5, 2014 at 3:55 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: > > What is our plan of release strategy for the DotNet CAS Client? > > I cut a 1.0.2 in response to the recent URL encoding issue. Tarball is > available on the .NET wiki page: > > https://wiki.jasig.org/display/CASC/.Net+Cas+Client > > It's also tagged in GH: > > https://github.com/Jasig/dotnet-cas-client/tree/v1.0.2 > > > I would like to have the final artifact somehow show up on NuGet. > > Scott Holodak did the NuGet releases in the past, but I have no idea > how to do it and simply punted. Feel free to do that part if you find > it helpful. We really need to recruit volunteers to help out with the > .NET client. If anyone wants to lend a hand, please speak up. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scottt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
