Last post Oct 24, 2013 07:40 AM by Rstaylor
Oct 23, 2013 03:29 PM|Rstaylor|LINK
I have a website (not MVC) developed under VWD 2010 with membership pointing to a SQL db. All works very well. We've decided to redo the website under VS 2012 Express to take advantage of some additional new features and off
the bat we see issues with our membership settings.
In the 2010 site with membership provider was defined in the web.config as: <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider"....
In 2012, the membership is defined as: <add name="DefaultMembershipProvider" type="System.Web.Providers.DefaultMembershipProvider, ....
The difference being the "type" definition. I can't see our membership in the ASP Configuration web page at all... Nothing I see makes a difference unless I change the membership definition to match the 2010 definition, but then
we have troubles with oAuth. I can connect and use the db just great for general data sources but nothing for the membership, roles etc.
I have searched for hours and found several articles indicating a few NuGet packages might be part of the cause, but am wondering if I missing something more specific. Is there some issue using membership created under a previous
version of Visual Web Developer? There's an obvious difference in the "type" defined above. What do I need to do to get that existing user base membership into our new 2012 site?
Any help would be greatly appreciated!
Oct 24, 2013 04:03 AM|DemiWu|LINK
You can open the application of VS2010 in VS2012, it will auto convert it.
You can see the Compatibility:
Oct 24, 2013 07:40 AM|Rstaylor|LINK
Thanks for the reply DemiWu. I am aware that I can reopen the original website in VS 2012, but that does not convert or change the membership provider settings. Additionally, we're actually rewriting the site from scratch. When we create the membership settings
in 2012 it uses the new "defaultmembershipprovider" settings which uses different tables for the membership.
So I guess my real question should have been - How do I move the users from the old membership tables to the new membership tables automatically if possible? One more twist - the new membership tables use a different salt method. I know I can move the users,
but in doing so the passwords will be lost requiring every user to provide a new password (ridiculous!).
I am dumbfounded that a method to upgrade the membership is not provided by MS, at least not one I can see. Is there a conversion process I can use to solve this?