Some considerations for deploying an ASP. NET MVC Project on IIS

1. The published Web site cannot apply the Web. config configuration.

Workaround:

Permissions for the physical path folder of the Web site, if the IIS application pool is identified as applicationpoolidentify, you need to add the IIS_IUSRS user to the folder and allow 5 permissions in the

2.1 LocalDB database cannot be deployed

2.2 Databases created by EF cannot be managed through SQL Server Management Studio when using the LOCALDB database

Workaround:

Do not use the default instance, create a shared instance yourself, and add the appropriate user rights

Specific steps: (Take localdb2012 as an example)

1. Open cmd, execute the following three commands separately in order to create and enable shared instances (SqlLocalDB.exe generally in the "C:\Program Files\Microsoft SQL Server\110\tools\binn" directory)

" InstanceName "  "InstanceName" "shareinstancename "  " InstanceName "

2. Open SQL Server managerment Studio using Windows Authentication Connection (LOCALDB) \.\shareinstancename (note that the data source name format of the shared instance is a bit more than the normal instance)

3. Select "Security"----"Login name"----Right-------"New Login"

If the identity of the application pool for IIS uses "Applicationpoolidentify", use "IIS apppool\ application pool name" as the login name

Set the server role----check public and sysadmin

4. Remember to modify the data source name of the connection string in the project: source= (LOCALDB) \.\shareinstancename

Some considerations for deploying an ASP. NET MVC Project on IIS