Last post Jan 14, 2014 01:17 AM by Shawn - MSFT
Jan 03, 2014 01:38 PM|Andy32|LINK
In VS2012 and prior one could launch the configuration tool (which was great) for setting up roles and access rules, and adding users to roles but it is no longer available in VS2013. I have read that this tool can still be launched via the command line.
However, I'm guessing since their is no replacement wizard as far as I can see, there must be another way that roles are managed most naturally in VS2013.
Could somebody please explain in simple terms how to perform the functions of the removed tool without using it? Can you still define access rules in the web.config file? What about setting up the roles? It seems bizarre that this very easy and straightforward
feature of VS2012 and before has been removed without a simple and easy way to do it in VS2013.
I have read that one can use Simple Role Provider but cannot find an explanation anywhere of how this works.
Many thanks in advance
Jan 03, 2014 02:39 PM|ushanlokuge|LINK
Did you try the ASP.Net configuration manager tool?
Jan 03, 2014 03:17 PM|Andy32|LINK
Jan 06, 2014 06:06 AM|Shawn - MSFT|LINK
As many of you have noticed, the option to select “ASP.Net Web Configuration Manager” is no longer in Visual Studio 2013 Preview. This is due to the removal of the Visual Studio Development Server (or Cassini) from the product. However, we understand that
many people have gotten used to using the Tool, and so here are the steps by which you can still run the manager. Note that these instructions only work for sites running on the .NET Framework 4.0 and above.
Besides, for more information, you could refer to:
Jan 09, 2014 01:04 PM|Andy32|LINK
I had seen those pages you have linked to. I was wondering if there is a new way to do things in VS2013? Since it says "many of you people have got used to using the tool" this suggests to me that using the tool is only one option. I haven't been able to
find any information on the standard way to do it, now that the tool isn't available by default it seems that there is a move towards doing things differently in VS2013...
Jan 14, 2014 01:17 AM|Shawn - MSFT|LINK
Visual Studio 2013 offers several authentication options for the Web Forms, MVC, and Web API templates:
If you select No Authentication, the sample application will contain no web pages for logging in, no UI indicating who is logged in, no entity classes for a membership database, and no connection string for a membership database.
If you select Individual User Accounts, the sample application will be configured to use ASP.NET Identity (formerly known as ASP.NET membership) for user authentication. ASP.NET Identity enables a user to register an account, by creating
a username and password on the site or by signing in with social providers such as Facebook, Google, Microsoft Account, or Twitter. The default data store for user profiles in ASP.NET Identity is a SQL Server LocalDB database, which you can deploy to SQL
Server or Windows Azure SQL Database for the production site.
In Visual Studio 2013 these features are the same as in Visual Studio 2012, but the underlying code for the ASP.NET membership system has been rewritten. Advantages of the new code base include the following:
The new membership system is implemented automatically in the new templates, and it can be implemented manually in any project that targets .NET 4.5 or later.
ASP.NET Identity is a good choice if you are creating an Internet web site which is mainly for external customers. If your organization uses Active Directory or Office 365 and you want to create a project that enables single-sign-on for employees and
business partners, the Organizational Accounts option might be a better choice.
For more information about the Individual User Accounts option, see the following resources:
If you select Organizational Accounts, the sample application will be configured to use Windows Identity Foundation (WIF) for authentication based on user accounts in Windows Azure Active Directory (WAAD, which includes Office 365) or
Windows Server Active Directory. For more information, see
Organizational account authentication options later in this topic.
If you select Windows Authentication, the sample application will be configured to use the Windows Authentication IIS module for authentication. The application will display the domain and user ID of the Active directory or local machine
account that is logged into Windows but won't include user registration or log-in UI. This option is intended for Intranet web sites.
For more information, you could refer to: