Updated article to include webdav info as troubleshooting section

15/umbraco-cms/fundamentals/setup/server-setup/iis.md

@@ -4,66 +4,164 @@
 
 # Hosting Umbraco in IIS
 
-## Configuring IIS for .NET
+## Install .NET Core Runtime
 
-* Install the [.NET Core Runtime](https://dotnet.microsoft.com/en-us/download/dotnet/) and download the **Hosting Bundle**. Ensure you download the correct .NET version as per the [requirements](../requirements.md).
-* Restart IIS (`net stop was /y` followed by `net start w3svc`)
-* Create a site in IIS and ensure that the .NET Common Language Runtime (CLR) version is set to `No Managed Code` for the Application Pool.
+* Download the .NET Core Runtime from the [Download .NET page](https://dotnet.microsoft.com/en-us/download/dotnet/).
+* Ensure you download the version that matches your project’s requirements, which can be found in the [requirements](../requirements.md) article.
 
-![IIS Application Pool](../../../../../10/umbraco-cms/fundamentals/setup/server-setup/images/iis-app-pool-core.png)
+## Install the Hosting Bundle
 
-### Publish website for manual deployment to IIS
+Download the [ASP.NET Core Runtime Hosting Bundle](https://dotnet.microsoft.com/en-us/download/dotnet/) to enable IIS to run ASP.NET Core applications.
 
-You can use the dotnet CLI to compile and collate all files required for hosting
+## Restart IIS
 
+After installing .NET Core Runtime, restart IIS to ensure the changes are applied.
+
+1. Open Command Prompt as Administrator.
+2. Run the following commands:
+
+```bash
+net stop was /y
+net start w3svc
 ```
-dotnet publish -o ../deployment-artefacts -f net7.0
+
+## Create the Site in IIS
+
+Next, create a new site in IIS for hosting Umbraco.
+
+### Set Application Pool
+
+1. Open IIS Manager.
+2. Right-click on **Application Pools** in the **Connections** panel.
+3. Select **Add Application Pool**.
+4. Enter the Name.
+5. Ensure the .NET Common Language Runtime (CLR) version is set to **No Managed Code**.
+6. Click **Ok**.
+
+![IIS Application Pool](images/iis-app-pool-core-v15.png)
+
+### Create a Site
+
+1. Open IIS Manager.
+2. Right-click on **Sites** in the **Connections** panel.
+3. Select **Add Website**.
+4. Fill in the **Site Name**, **Physical Path** (to your Umbraco installation), and the **Port**.
+5. Click **Ok**.
+
+![IIS Creating Site](images/create-site-in-iis.png)
+
+### Publish the Website
+
+You can either use the dotnet CLI or Visual Studio to publish your Umbraco website.
+
+#### Option 1: Use dotnet CLI for Manual Deployment
+
+1. Open the Command Prompt in the directory of your Umbraco project.
+2. Run the following command:
+
+```bash
+dotnet publish -o ../deployment-artefacts -f net9.0
 ```
 
-Alternatively, you can use the File Transfer Protocol (FTP) publishing in Visual Studio to compile and collate all the required files for the application to run.
+{% hint style="info" %}
+Make sure to replace net9.0 with the version of .NET you are using.
+{% endhint %}
+
+![Using dotnet CLI for Manual Deployment](images/dotnet-cli-command.png)
 
-In Visual Studio, select the Umbraco web project in the _Solution Explorer_ and choose the _Publish..._ command.
+#### Option 2: Use Visual Studio to Deploy
 
-![Publish...](../../../../../10/umbraco-cms/fundamentals/setup/server-setup/images/contextmenu-publish-command.jpg)
+1. Open your project in Visual Studio.
+2. Right-click on the Umbraco project in Solution Explorer.
+3. Select **Publish...**.
+
+![Using Visual Studio to Deploy](images/visual-studio-deploy.png)
 
 {% hint style="info" %}
- 
-**Deploy a website for automated deployment with Azure DevOps to IIS**
+To deploy Umbraco to IIS via Azure DevOps, you can use the [IIS Release task in Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/pipelines/release/deploy-webdeploy-iis-deploygroups). This task is a wrapper for `MSDeploy.exe` and can be configured as preferred.
+{% endhint %}
 
-You can use the [IIS Release task in Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/pipelines/release/deploy-webdeploy-iis-deploygroups) to deploy your website to your Web Server. This task is a wrapper for `MSDeploy.exe` and can be configured as preferred.
+### Configure Environment Variables
 
+In IIS, you can configure environment variables for Umbraco to store sensitive data such as your connection string.
+
+#### Configure Environment Variables in IIS
+
+1. Open IIS Manager and select your Umbraco site.
+2. Double-click **Configuration Editor** in the **Management** section.
+
+![IIS Website Configuration](images/iis-core-website-config-v15.png)
+
+3. Select `system.webServer/aspNetCore` in the **Section** dropdown.
+4. Select `ApplicationHost.config <location path='[YOUR-SITENAME]'>` in the **From** dropdown.
+
+This ensures your settings will be stored in a machine specific file. The configuration files might end in a public repository and should not contain sensitive data like Connection Strings or Simple Mail Transfer Protocol (SMTP) credentials. Additionally, by default the configuration file will be overwritten during each publish processes.
+
+5. Locate the **environmentVariables** line and open the dialog to add environment variables.
+6. Enter the values for `ASPNETCORE_ENVIRONMENT` and `ConnectionStrings__umbracoDbDSN`.
+
+{% hint style="info" %}
+* Variable names need to change the object structure form JSON by combining the segments with double underscore `__` For example: `ConnectionStrings__umbracoDbDSN`
+* Escaped backslashes `\\`  For example: `serverName\\databaseInstanceName` are replaced by single backslash `\` (`DATABASESERVER123\SQL2017`)
 {% endhint %}
 
-### Environment Variables in ApplicationHost.config
+7. Click **Add**.
+8. Click **Apply**.
+
+![IIS Configuration Editor](images/iis-environment-variables-v15.png)
+
+9. Restart IIS to apply the changes after updating the environment variables.
 
-In the _Management_ section you find the _Configuration Editor_:
+### IIS Hosting Models
 
-![IIS Website Configuration](../../../../../10/umbraco-cms/fundamentals/setup/server-setup/images/iis-core-website-config.png)
+IIS can host .NET applications using two different hosting models: In-process (default) and Out-of-process.
 
-One section is of particular interest:
+#### In-process Hosting (Default)
 
-* In the first, left hand dropdown list (_Section:_) choose: `system.webServer/aspNetCore` section.
-* In the second, right hand dropdown list (_From:_) choose: `ApplicationHost.config <location path='[YOUR-SITENAME]'>`. This ensures your settings will be stored in a machine specific file. The configuration files might end in a public repository and should not contain sensitive data like Connection Strings or Simple Mail Transfer Protocol (SMTP) configuration with username and password. Additionally, by default the configuration file will be overwritten during each publish processes.
+* [In-process hosting](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/in-process-hosting) runs the .NET application within the same process as the IIS worker process.
+* This is the default hosting model and is more efficient, as there is no inter-process communication between IIS and the application.
 
-![IIS Configuration Editor](../../../../../10/umbraco-cms/fundamentals/setup/server-setup/images/iis-environment-variables.png)
+#### Default Configuration
 
-Find the line named _environmentVariables_ and open the dialog to add environment variables. These work similar to the _launchSettings_. You can define `ASPNETCORE_ENVIRONMENT` and create an `appSettings.[ASPNETCORE_ENVIRONMENT].json` file. Or even better create environment variables for sensitive settings like passwords. There are some differences to `launchSettings.json` configuration:
+No changes are required to your application configuration for in-process hosting. It works automatically with the default IIS settings.
 
-* Variable names need to change the object structure form JSON by combining the segments with double underscore `__` e.g. `ConnectionStrings__umbracoDbDSN`
-* Escaped backslashes `\\` e.g. `serverName\\databaseInstanceName` are replaced by single backslash `\` e.g. `DATABASESERVER123\SQL2017`
+#### Out-of-process Hosting
 
-### IIS Hosting models
+* [Out-of-process hosting](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/out-of-process-hosting) allows the .NET application to run separately from the IIS worker process. IIS acts as a reverse proxy to the Kestrel server, which hosts the .NET application.
+* This model is useful when you need to run a .NET application in a separate process, for example, when the application requires more isolated resources or needs to scale independently from IIS.
 
-IIS can host .NET applications using 2 different hosting models
+#### Configuration
 
-* [In-process (default)](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/in-process-hosting?view=aspnetcore-7.0)
-* In-process hosting runs a .NET app in the same process as its IIS worker process
-* [Out-of-process](https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/out-of-process-hosting?view=aspnetcore-7.0) - to enable this model you need to edit your .csproj file and add:
+To enable out-of-process hosting:
 
-```js
+1. Open your Umbraco project.
+2. Locate the `.csproj` file.
+3. Add the following line:
+
+```xml
 <PropertyGroup>
   <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>
 </PropertyGroup>
 ```
 
-Out-of-process .NET apps run separately from the IIS worker process. The module controls the management of the Kestrel server and requests are proxied between them.
+4. Save the `.csproj` file.
+5. Rebuild your application.
+
+### Troubleshooting: Handling WebDAV Module Interference
+
+**Issue:** A 405 error may occur when attempting to save content items in Umbraco, due to the WebDAV module blocking PUT requests.
+
+**Solution:** If you encounter this issue, it may be because the WebDAV module in IIS is blocking the necessary PUT requests. This issue is not present on all IIS setups, but if you do have WebDAV installed, try disabling the WebDAV module.
+
+**Workaround:**
+
+1. Open the `web.config` file.
+2. Add the following code to remove the WebDAV module:
+
+```xml
+<modules runAllManagedModulesForAllRequests="false">
+    <remove name="WebDAVModule" />
+</modules>
+```
+
+3. Restart IIS.