-
Notifications
You must be signed in to change notification settings - Fork 45
[Announcement] Microsoft.AspNet.Cors version changed to 6.0.0 #38
Comments
@pranavkm aspnet/Announcements#73 still links to #24, which is closed. |
@henkmollema sorry about that. Fixed. |
Great! 😄 |
@pranavkm @Eilon I am having issues adding two dependencies to support "Microsoft.AspNet.Cors": "5.2.3", If I remove 1 the other fails. Is there a way to support both? |
Dnx does not allow a project to reference two versions of the same package. |
@pranavkm they cant be the same package because when I remove 5.2.3 I lose support for System.Web.Cors, but when I remove beta-8 I lose support for IApplicationBuilder.UseCors |
Ive created our own CorsPolicy which is implementing ICorsPolicyProvider which required Microsoft.AspNet.Cors": "5.2.3 |
Running ASP.NET 4.6 components inside of DNX isn't supported. You'd need to port your class library to target the policy provider in Microsoft.AspNet.Cors.Core - https://github.com/aspnet/CORS/blob/dev/src/Microsoft.AspNet.Cors.Core/ICorsPolicyProvider.cs |
Thanks @pranavkm does the dnx support ICorsPolicyProviderFactory? I am trying to set my cors using the method HttpConfiguration.SetCorsPolicyProviderFactory |
Add your custom provider to the DI container in Startup - public void ConfigureServices(IServiceCollection services)
{
services.AddTransient<ICorsPolicyProvider, MyCorsPolicyProvider>();
....
} |
@pranavkm thanks all set. |
We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have. |
Discussion thread for aspnet/Announcements#73
The text was updated successfully, but these errors were encountered: