Skip to content

Step-by-Step Deployment Process

This section outlines the standard deployment process for a new environment or major update.

1. Prepare the Web Server

  1. Install required Windows features (IIS, ASP.NET 4.8).
  2. Create an IIS Application Pool configured for .NET CLR v4.0, Integrated mode.

2. Deploy Application Files

  1. Create a folder on the web server (e.g. C:\inetpub\wwwroot\ConproSoft).
  2. Copy the /app contents from the solution package into this folder.
  3. Ensure web.config, touch-settings.json, and all subfolders are present.

3. Configure IIS Site

  1. Create a new IIS Site or Application:
  2. Physical path: the folder created above.
  3. Binding: set host name and port (e.g. conprosoft.yourdomain:443).
  4. Assign the previously created Application Pool to this site.

4. Restore or Deploy Database

  1. On SQL Server, create a new database or restore from backup.
  2. Apply any schema updates or migrations provided.

5. Update Configuration

  1. Edit web.config:
  2. Update the MyCompany connection string to point to the target database.
  3. Update <system.net><mailSettings> with SMTP details.

  4. Adjust any environment-specific appSettings.

  5. Edit touch-settings.json:

  6. Confirm appName and UI behaviour as required.

6. File Permissions

  • Ensure the IIS Application Pool identity has:
  • Read & Execute on the application folder.
  • Write access to any BLOB storage or temp folders.

7. Test

  • Browse to the site (HTTP/HTTPS).
  • Confirm login, navigation, and key workflows.
  • Verify email sending using a test action (if applicable).

Use the Go-Live Checklist to finalise the deployment once testing is complete.

Rollback — If Deployment Fails

If any step fails and the site is inaccessible or unstable after deployment:

Application Files

  • If files were corrupted or incomplete during the copy, redeploy from the validated /app package.
  • If the previous deployment was intact, restore from a file-level backup taken before deployment began.

Database / Connection String

  • Revert the MyCompany connection string in web.config to the previous working value.
  • Confirm database connectivity before restarting the Application Pool.

IIS Configuration

  • If the Site or AppPool was misconfigured, reset to the known-good settings:
  • .NET CLR Version: v4.0
  • Managed Pipeline Mode: Integrated
  • If the AppPool remains stopped after a restart, escalate to the hosting provider.

Smoke Test After Rollback

  • Confirm the site loads at the original URL.
  • Verify login and at least one key workflow (e.g. timesheet or requisition).
  • If rollback restores function, document the failure point before reattempting the deployment.