search

aspnet / AspNetKatana

Microsoft's OWIN implementation, the Katana project
Apache License 2.0
967 stars 334 forks source link

Support NetStandard 1.6 #27

Closed damianh closed 4 years ago

damianh commented 7 years ago

Use case: easy porting of lots of existing code without having to rewrite entire applications.

Would be happy to attempt a PR.

VictorBlomberg commented 7 years ago

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

Any input from maintainers?

Tratcher commented 7 years ago

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.

MaximRouiller commented 7 years ago

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

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

Tratcher commented 7 years ago

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.

MaximRouiller commented 7 years ago

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.

damianh commented 7 years ago

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

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

panesofglass commented 6 years ago

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

panesofglass commented 6 years ago

@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?

Tratcher commented 4 years ago

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