Remove dependency on Owin.dll and merge in IAppBuilder
See original GitHub issueHi Chris,
Good to see this project moved to github 😃
As we know Owin.dll
had its controversy… As a major release allows breaking changes, I suggest merging in IAppBuilder
into Microsoft.Owin.dll
. The namespace Owin.
could be retained within the lib to minimise changes to libraries that depend on Microsoft.Owin
.
Cheers
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (10 by maintainers)
Top Results From Across the Web
UserManager dependency injection with Owin and Simple ...
Looking at your code: Startup.cs app.UseWebApi(httpConfig);. DependencyConfig container.RegisterWebApiControllers(GlobalConfiguration.
Read more >How to hide dependent Nuget .dll's from consuming parent ...
Merge or Repack dependencies using ILMerge or ILRepack: ... I am not sure if I I need to use ILMerge or Repack, it...
Read more >OWIN Startup Class Detection
This tutorial shows how to configure which OWIN startup class is loaded. For more information on OWIN, see An Overview of Project Katana....
Read more >Data Engine WebApi using Visual Studio Template
Owin.Host.SystemWeb" Nuget package in your Visual Studio application. "C1.Web.Api.DataEngine" gets added under the "dependencies" within project.json file ...
Read more >Autofac Documentation
The “Autofac” package has all the core functionality you'll need. ... To exclude types from scanning, use the Except() predicate: builder.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The irony is that the owin community at the time opposed
owin.dll
for this precise reason.Now there will not likely be a netstandard version of
owin.dll
thus freezing the entire chain of code that depends on it.Sad.
But we’re not going to support Katana on netstandard, we just don’t have the man power to support it.