phantomtypist

At a higher level, the .NET CAS Client project needs to cover the following scenarios: ## ASP.NET Identity (OWIN middleware) - MVC 6 / ASP.NET Core - .NET Framework 4.6...

At least we don't need to worry about supporting Web Forms on ASP.NET Core (ref https://github.com/aspnet/Home/issues/1961#issuecomment-286000755)

@garster ok that would be nice to see. I am curious as to whether or not you tried to just add .NET Core support to this existing project and were...

@garster FWIW, not sure if you have seen these other couple of implementations: - https://github.com/IUCrimson/AspNet.Security.CAS - https://github.com/JLewinski/dotnet-cas-client-with-core/ (this person forked our repo, but instead of adding the .NET Core functionality...

@garster your team can still share if they want, privately to us or publicly via PR. I'll leave it up to you. At the least if you want you could...

@MattHodgman got a link to that forked repo? Sometimes I gotta SMH why people that do this don't just talk with us and make the contributions in the core project.

I'm not sure I fully understand here. Can you clearly detail a reproduction scenario for me? Step by step please with as much detail as possible, clearly.

*sigh* I guess somebody was eventually going to bring this up... If this project was any more popular there'd be pitchforks and torches by now ;) 

Since all referenced assemblies of a strongly-named assembly must also be strongly-named, that leads to a problem with our NuGet "extension" packages discussed in #61 and #38. We'd have to...

A good discussion I found a long time ago was the one with regards to Octokit. Discussion: https://github.com/octokit/octokit.net/issues/405 Outcome: https://github.com/octokit/octokit.net/blob/master/docs/strong-naming.md