One of the biggest challenges on this module thus far are the conflicts between installed NuGet packages and assemblies included in the Orchard lib folder. In particular, Microsoft.Owin and Microsoft.Owin.Host.SystemWeb, among others(Microsoft.Owin.Security, Microsoft.Owin.Security.Cookies, etc...). While I have the code working, it's difficult to get references resolved to run the module the first time.
This module makes use of several packages that all depend on Microsoft.Owin version 3.0.1.0. The version included in the Orchard lib folder is 3.0.0.0.
I've been working to determine the best way of resolving this problem. One thought I had was to update the version of Microsoft.Owin (and the other assemblies) in the Orchard lib folder and reference from that location. But that might cause other pain later. The only other alternative is to include binding redirects in the Orchard.Web web.config folder, and be vigilant about references to those assemblies.
One of the biggest challenges on this module thus far are the conflicts between installed NuGet packages and assemblies included in the Orchard lib folder. In particular, Microsoft.Owin and Microsoft.Owin.Host.SystemWeb, among others(Microsoft.Owin.Security, Microsoft.Owin.Security.Cookies, etc...). While I have the code working, it's difficult to get references resolved to run the module the first time.
This module makes use of several packages that all depend on Microsoft.Owin version 3.0.1.0. The version included in the Orchard lib folder is 3.0.0.0.
I've been working to determine the best way of resolving this problem. One thought I had was to update the version of Microsoft.Owin (and the other assemblies) in the Orchard lib folder and reference from that location. But that might cause other pain later. The only other alternative is to include binding redirects in the Orchard.Web web.config folder, and be vigilant about references to those assemblies.
Anyone have thoughts on this problem?