We have implemented ASP.NET Identity (new membership system) in VS2013. This system uses strings as PKs. You can also change the PK of the system. You can find more details http://blogs.msdn.com/b/webdev/archive/2013/06/27/introducing-asp-net-identity-membership-system-for-asp-net-applications.aspx
We are working on a new membership system that will be the same across all of ASP.NET. It will eventually replace the internals of SimpleMembership that you're using now. It will be able to take any type as the key for each user.
So you have a few options:
1. Grab the source code for SimpleMembership (part of ASP.NET Web Pages on http://aspnetwebstack.codeplex.com) and modify it to take a GUID and use your own build of it.
2. Move to the same AccountController and Views that MVC 3 used, which uses the old ASP.NET Membership providers.
3. Wait until we're done with this new provider and switch to it. We're targeting vNext for this.
All templates are now Bootstrap based and there are thousands of themes available online
Not sure what you're looking for here. We are HTML5 across the board in our templates out of the box. We also use CSS media queries so it resizes and looks good at lower resolutions like on mobile devices. Or do you mean something else?
We are currently working to get this into the Starter template for both MVC and Web Forms.
Our site is built on ASP.NET
ASP.NET's main site is built using Umbraco, which is built on ASP.NET. So yes!?!?
Sorry, which tutorial are you referring to?
Sure, I understand. There's no issue with them running together, but just to confirm...you're saying there's a lot of existing code you wouldn't want to move over?
There are no plans for this work (see comments on how to do it yourself).
Sorry. We'd rather be honest with you about our intentions for features than leave you hanging. At this time, we do not intend to implement this. I hear Brad might write up a cool blog post about it though. :)
We have updated the templates in VS2013. They are based on Bootstrap framework and demonstrate social login using OAuth, OPenId providers. To download VS2013 RC and learn more about this integration please check out http://www.asp.net/visual-studio/overview/2013/release-notes-(release-candidate)
Hey JarrettV, long time. :) So I'm going to give this one a yes, but no (hopefully that will make sense). In the Developer Preview of ASP.NET Web Pages 2 we introduced some new classes (and new functionality in our starter site template) that has Facebook & Twitter (OAuth), Windows Live and OpenID authentication out of the box (just plug in the right keys, uncomment a couple lines of code and go). We are also going to ship this in MVC 4 (in the next release).
As for the Twitter CSS stuff, we have no plans to do this. There will also still be an AccountController, but it will hopefully be simplified. Still working out the details.
I'll leave this open though if others want to vote on it and convince us we should do your other suggestions.
Check out the new Empty and Basic templates in ASP.NET MVC 4.
@Richard, we've already decided against including links to CDNs in the templates across the board. We want offline to work out of the box. That said, in the future we'll be investigating more resource/asset management features that could allow us to also include CDN paths with local fallback. Still working out the details, but thought I'd share.
For now, you should use ModelState.IsValidField. If you look at the starter template in WebMatrix Beta, this is how it does it.
However, we are looking at adding something on the ValidationHelper to make your scenario simpler so keep voting this one up, everyone.
Thanks for the suggestion!
Resource Management in MVC 4 and Web Pages 2 will replace the need to use @section to register scripts and other resources. If you have other needs for @section in partials, I’ll re-open this one.
We found the main reason for using @section in a partial is to register scripts. If you look at Web Pages 2 or MVC 4 Developer Preview you'll find the start of an API to manage scripts and other resources (works anywhere) to replace this need.
VS2010 and the next version of VS.NET will have this feature – “Project Roundtripping”
Please try ASP.NET Identity where we added support for OpenID, OAuth provides as first class support in membership. http://blogs.msdn.com/b/webdev/archive/2013/06/27/introducing-asp-net-identity-membership-system-for-asp-net-applications.aspx
I'm not sure I can mark this one as done or in progress or planned, but we do have some new providers that change everything so we can do these types of things.
In January, we shipped ASP.NET Web Pages and Razor v1. In it was a new feature called SimpleMembership that changed the structure for membership to allow for future types of authentication to be added.
In September, we released the v2 Developer Preview of Web Pages and Razor with added support to SimpleMembership for OAuth (1 and 2) and OpenID.
In our next update we will be adding support for SimpleMembership into MVC 4 and Web Forms vNext.
Check out SimpleMembership and see if it fits your needs.
Thanks everyone. We hear you!
314 votesErik Porter supported this idea ·
This is a really great idea and definitely a missing piece. Can't really promise this feature or anything at this point, but I just prototyped something up and it definitely isn't hard (for both Web Pages and MVC). Maybe I'll ship it as a NuGet package for now?!?!
Thanks for the suggestion and I'll discuss with the team!
Could you give some more details? Not exactly sure what you're asking for here.