Merge pull request #6718 from umbraco/cloud-upgrade

Simplified steps in Major upgrades Cloud article

Author: eshanrnh

umbraco-cloud/.gitbook/assets/runtime-settings.png

@@ -60,10 +60,14 @@ Look for the "**Upgrade from/to Umbraco xx"** boxes. These boxes contain importa
 
 ## Step 1: Enable .NET
 
+Before proceeding, you must determine whether the .NET framework version needs to be updated for your project. If no changes to the .NET version are required, you can skip this step and proceed with Step 2.
+
+Refer to the [Choose the correct .NET version](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading#choose-the-correct-.net-version) section to identify whether a .NET version update is necessary for your upgrade.
+
 1. Go to the project in the Umbraco Cloud portal.
 2. Navigate to **Configuration** -> **Advanced**.
 3. Scroll down to the **Runtime Settings** section.
-4. **Ensure that the latest version of .NET is enabled** for each environment on your Cloud project, by selecting it from the dropdown.
+4. Select the appropriate .NET version from the **Change .NET framework runtime for your Umbraco install** dropdown for each environment in your Cloud project.
 
 <figure><img src="../../.gitbook/assets/runtime-settings.png" alt=""><figcaption><p>Runtime settings</p></figcaption></figure>
 
@@ -76,34 +80,30 @@ Look for the "**Upgrade from/to Umbraco xx"** boxes. These boxes contain importa
 
 ## Step 3: Upgrade the project locally using Visual Studio
 
-1. Open your project in Visual Studio - use the `csproj` file in the `/src/UmbracoProject` folder.
-2. Right-click your project solution in **Solution Explorer**.
-3. Select **Properties**.
-
-<figure><img src="images/Solution-Explorer.png" alt=""><figcaption></figcaption></figure>
+1. Open the `csproj` file located in the `/src/UmbracoProject` folder.
+2. Determine if you need to update the .NET version based on the changes made in [Step 1](major-upgrades.md#step-1-enable-net):
+   * **If the .NET version was updated:** Update the `<TargetFramework>` to match the version set in your Cloud environment.
+   * **If the .NET version was not updated:** Skip this step.
 
-4. Change the **Target framework** in the **General** section of the **Application** tab.
-   1. Choose the version you set on your Cloud environment in [Step 1](major-upgrades.md#step-1-enable-.net).
-
-![Target Framework](images/Target-Framework.png)
+<details>
 
-5. Go to **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution.**
-6. Navigate to the **Updates** tab.
-7. Select the version you are updated to, and follow the instructions:
+<summary>Upgrading to Umbraco 15</summary>
 
-{% tabs %}
-{% tab title="Umbraco 15" %}
 The following packages are no longer needed on the Cloud platform:
 
 * `Umbraco.Cloud.Cms.PublicAccess`
 * `Umbraco.Cloud.Identity.Cms`
 
-The references to these packages need to be deleted.
+Delete the `<PackageReference>` entries for these packages.
+
+</details>
 
-1. Open the `.csproj` file.
-2. Locate  `PackageReference` for the packages mentioned above.
-3. Delete the references and save the file.
+3. Go to **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution**.
+4. Navigate to the **Updates** tab.
+5. Select the version you are updated to and follow the instructions:
 
+{% tabs %}
+{% tab title="Umbraco 15" %}
 Update the following packages:
 
 * `Umbraco.Forms.Deploy`
@@ -164,11 +164,9 @@ Update the following packages:
 {% endtabs %}
 
 {% hint style="info" %}
-If you have more projects in your solution or other packages, make sure that these are also updated to support the latest .NET.
+Update all projects and packages in your solution to support the latest .NET.
 {% endhint %}
 
-![All packages checked in the Visual Studio Package manager and ready for update](images/check-all-packages-2.png)
-
 ## Step 4: Finishing the Upgrade
 
 1. Ensure the [Unattended Upgrades](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading#run-an-unattended-upgrade) feature is **enabled**.
@@ -291,20 +289,18 @@ The following steps involve setting a **content-freeze** period on the project.
 4. Import content using either of the following approaches:
    1. [Restore content and media](../deployment/restoring-content/) directly from the backoffice.
    2. Use the [Database Backup and Restore](../databases/backups.md) functionality in the Cloud Portal.
-5. Follow [Step 1](major-upgrades.md#step-1-enable-.net) for the next environment in the line.
-6. Deploy the upgrade from the left-most environment (Development).
-7. Verify and test all functionality on the upgraded environment.
-8. [Remove your custom hostname(s)](../set-up/project-settings/manage-hostnames/) from the production environment.
-9. Ensure the hostname(s) no longer point to the production environment.
-10. [Add the custom hostname(s)](../set-up/project-settings/manage-hostnames/) to the new environment (Staging).
-11. Follow [Step 1](major-upgrades.md#step-1-enable-.net) for the production environment.
-12. Deploy the upgrade to the production environment.
+5. Deploy the upgrade from the left-most environment (Development).
+6. Verify and test all functionality on the upgraded environment.
+7. [Remove your custom hostname(s)](../set-up/project-settings/manage-hostnames/) from the production environment.
+8. Ensure the hostname(s) no longer point to the production environment.
+9. [Add the custom hostname(s)](../set-up/project-settings/manage-hostnames/) to the new environment (Staging).
+10. Deploy the upgrade to the production environment.
     1. In case the upgrade is taking longer than expected, restore a backup of the Staging database on the production environment.
-13. Cancel **content-freeze**.
-14. Verify and test all functionality in the production environment.
-15. [Remove your custom hostname(s)](../set-up/project-settings/manage-hostnames/) from the Staging environment.
-16. Ensure the hostname(s) no longer point to the Staging environment.
-17. [Add the custom hostname(s)](../set-up/project-settings/manage-hostnames/) to the production environment.
+11. Cancel **content-freeze**.
+12. Verify and test all functionality in the production environment.
+13. [Remove your custom hostname(s)](../set-up/project-settings/manage-hostnames/) from the Staging environment.
+14. Ensure the hostname(s) no longer point to the Staging environment.
+15. [Add the custom hostname(s)](../set-up/project-settings/manage-hostnames/) to the production environment.
 {% endtab %}
 
 {% tab title="Without content freeze" %}