寻求Windows Server 2016托管ASP.NET MVC应用及SQL Server部署指导

Hey Stefan, totally get how overwhelming diving into Windows Server for the first time can be—you’ve put in two weeks of effort, so let’s break this down into clear, actionable steps to get your ASP.NET MVC app with a database up and running on Windows Server 2016.

First, we need to set up the core tools to host ASP.NET apps:

• Install IIS (Internet Information Services)
  Open Server Manager → Add Roles and Features → Select "Web Server (IIS)" under Server Roles. Make sure to check the following role services:
  • ASP.NET 4.6 (matches most MVC 5 apps; adjust if you’re using .NET Core)
  • .NET Framework 4.6 Features
  • Management Tools (IIS Management Console is a must)
• Verify .NET Framework Installation
  If your app targets a specific .NET version (e.g., 4.7.2), go to Control Panel → Programs → Programs and Features to confirm it’s installed. If not, download and install the matching runtime.

Next, let’s get your database configured properly:

• Install SQL Server
  Grab the free SQL Server Express edition (or Developer edition for full features) and run the installer. During setup:
  • Choose "Mixed Mode (SQL Server authentication and Windows authentication)" so you can use a dedicated SQL user for your app.
  • Set a strong password for the sa account (you can use this later, but we’ll create a dedicated user too).
• Create Your Database and Dedicated User
  Open SQL Server Management Studio (SSMS) and connect to your server instance:
  1. Right-click "Databases" → New Database → Name it whatever your app uses (e.g., MyMvcAppDB).
  2. Go to "Security" → "Logins" → New Login:
     • Choose "SQL Server authentication", set a username/password (e.g., MvcAppUser).
     • Under "User Mapping", check your new database, and assign the db_owner role (this gives full permissions to manage the database—perfect for getting started).
• Quick Check
  Test the connection by logging into SSMS with your new MvcAppUser account to ensure you can access and modify the database.

Now let’s get your app onto the server:

• Publish Your App from Visual Studio
  Right-click your MVC project in Visual Studio → Publish → Choose "Folder" as the target, pick a local folder to export the deployment files, then click "Publish". This generates all files needed to host the app.
• Copy Files to the Server
  Transfer the published folder to your Windows Server (use a USB drive, shared network folder, or Remote Desktop file transfer). Place it somewhere accessible, like C:\inetpub\wwwroot\MyMvcApp.
• Configure IIS Site
  Open IIS Manager:
  1. Right-click "Sites" → Add Website:
     • Site name: MyMvcApp
     • Physical path: Point to the published folder on the server
     • Binding: Select your server’s local IP address (or * for all), port 80, leave hostname blank
  2. Adjust the Application Pool:
     • Go to Application Pools → Find the pool matching your site name → Right-click → Advanced Settings
     • Set ".NET CLR Version" to match your app’s target (e.g., v4.0.30319 for .NET 4.6+)
     • If using SQL authentication (our recommendation), leave "Identity" as ApplicationPoolIdentity—your app’s connection string will handle authentication.
• Update Connection String
  Open the Web.config file in your published folder. Find the connection string section and update it to point to your SQL Server:

  <connectionStrings>
    <add name="DefaultConnection" connectionString="Data Source=localhost;Initial Catalog=MyMvcAppDB;User ID=MvcAppUser;Password=YourStrongPassword;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  

  Replace values with your actual database name, SQL username, and password.

Time to see if it works:

• From the server itself, open a browser and go to http://localhost (or http://your-server-ip if you used a specific IP binding).
• From another computer on your local network, use the server’s local IP (e.g., http://192.168.1.100) to access the app.
• If you hit errors:
  • Check IIS logs: Go to your site in IIS Manager → Logging → Open the log file path (usually C:\inetpub\logs\LogFiles) to see detailed error messages.
  • Verify SQL Server is running: Open Services (run services.msc) and make sure "SQL Server (MSSQLSERVER)" is started.
  • Check firewall: Ensure Windows Firewall allows incoming connections on port 80 (for HTTP) and 1433 (for SQL, if needed).

• If you get a "500 Internal Server Error", enable detailed errors in IIS: Go to your site → Error Pages → Edit Feature Settings → Select "Detailed errors".
• If the app can’t connect to SQL, double-check the connection string and confirm your MvcAppUser has db_owner access.
• Make sure the application pool identity has read/write permissions to the app’s folder (right-click the folder → Properties → Security → Add IIS AppPool\MyMvcApp and give it Modify permissions if needed).

内容的提问来源于stack exchange，提问作者Stefan Ivovic