Support NetStandard 1.6 about aspnetkatana HOT 9 CLOSED

There are discussions going for 1 and 3, but 2 isn't happening.

• 1. 3 could be replaced with Also the cookies middleware with its dependency on DPAPI is probably a no-go too.

(FYI I did this https://www.nuget.org/packages/KatanaNetStandard/ to unblock myself and team)

from aspnetkatana.

There hasn't been any progress and there are no plans to pursue this further. Closing.

from aspnetkatana.

This is a really important issue. Would be able to try to help, too.

Any input from maintainers?

from aspnetkatana.

This is a non-starter due to at least three critical net45 dependencies:

1. Owin.dll
2. System.Web
3. HttpListener

There are discussions going for 1 and 3, but 2 isn't happening.

from aspnetkatana.

From what I heard... 2 is an absolute no go.

It would break so many backward compatibilities it wouldn't be funny.

from aspnetkatana.

If you got Owin.dll then you can port most of the libraries/middleware. If you get HttpListener then you can run self-hosted apps. System.Web isn't going to happen though, so you can't convert IIS hosted apps.

from aspnetkatana.

The future is .NET Core if I got it right. Katana and Owin is all fun but if you want to run everywhere and be where the investment is? Core is the way to go.

from aspnetkatana.

Why can you not merge the interfaces from Owin.dll into this package? Also, where is that discussion?

from aspnetkatana.

@Tratcher can we transfer the owin.dll project to the ASP.NET org? You would still have publishing, etc; it just wouldn't be owned by owin anymore. Wouldn't that resolve all the issues?

from aspnetkatana.