141 votesunder review · 7 comments · General ASP.NET » General ASP.NET · Flag idea as inappropriate… · Admin →
The cleanest solution would probably be if ASP.NET included a custom HTTP module which handles ALL errors. Add a static event to it which can be subscribed to from the Application_Start.
You should probably make sure that the exception is retained over the customErrors redirect so it can be used in the custom error pages.
12 votesstarted · AdminScott Hunter (Director PM, .NET, Microsoft ASP.NET Future Feature Feedback) responded
We are actively working on a replacement of membership in general in ASP.NET. This work will solve the issues that you are bringing up, expect to see it in the Spring of 2013.
We are not sure about removing DotNetOAuth yet. We don’t want to write our own implementation of OAuth when there are community versions that exist today. But we will see what we can do
Using DotNetOAuth is great. You should however make the openauth an optional part of the provider (for instance an separate nuget package which would integrate openauth in the new membership system)
This is planned for a future version of ASP.NET MVC.
I've described how you can achieve that here: http://blog.gauffin.org/2012/05/griffin-mvccontrib-the-plugin-system/
But it would be better if the support was built in, since Razor gives a lot of warnings for some class libraries (it seems like it tries to compile the views as .NET 2)
3 votesJonas Gauffin shared this idea ·