Add 3.8.0 to 3.8.1 uninstallation info

Author: JakeLegendXIII

articles/migrate_38.md

@@ -9,7 +9,7 @@ Migrating from 3.8.0 should be straightforward for most platforms.
 
 The major difference is that 3.8.1 now requires .NET 6 and Visual Studio 2022. You can follow the [environment setup tutorial](getting_started/index.md) to make sure that you are not missing any components.
 
-The MGCB Editor is no longer a global .NET tool and we recommend that you use the new Visual Studio 2022 extension which helps accessing it without the need of CLI commands.
+The MGCB Editor is no longer a global .NET tool and we recommend that you use the new Visual Studio 2022 extension which helps with accessing it without the need of CLI commands. It is also recommended that you uninstall the older global versions of the .NET tools as described below.
 
 ## WindowsDX, DesktopGL, and UWP
 
@@ -30,41 +30,48 @@ Then edit your MonoGame ```PackageReference``` to point to 3.8.1:
 
 ### Accessing MGCB and MCGB Editor without a global tool
 
-MGCB Editor is no longer a .NET global tool, and doesn't need to be installed or registered.
+The MGCB Editor is no longer a .NET global tool, and doesn't need to be installed or registered. When migrating from 3.8.0, it is recommended that you uninstall the global versions of the tools. You can accomplish that with these commands:
 
-However, if you are migrating from 3.8.0, you will need to setup a configuration file. Next to your ```.csproj```, create a folder nammed ```.config``` and a file within it nammed ```dotnet-tools.json``` with this content:
+```
+dotnet tool uninstall dotnet-mgcb -g
+dotnet tool uninstall dotnet-2mgfx -g
+dotnet tool uninstall dotnet-mgcb-editor -g
+```
+**Do not** run the ``` dotnet tool install ``` on 3.8.1, as it would break 3.8.1.
+
+You will also need to setup a dotnet-tools configuration file. Next to your ```.csproj```, create a folder named ```.config``` and a file within it named ```dotnet-tools.json``` with this content:
 
 ```json
 {
   "version": 1,
   "isRoot": true,
   "tools": {
     "dotnet-mgcb": {
-      "version": "3.8.1.263",
+      "version": "3.8.1.303",
       "commands": [
         "mgcb"
       ]
     },
     "dotnet-mgcb-editor": {
-      "version": "3.8.1.263",
+      "version": "3.8.1.303",
       "commands": [
         "mgcb-editor"
       ]
     },
     "dotnet-mgcb-editor-linux": {
-      "version": "3.8.1.263",
+      "version": "3.8.1.303",
       "commands": [
         "mgcb-editor-linux"
       ]
     },
     "dotnet-mgcb-editor-windows": {
-      "version": "3.8.1.263",
+      "version": "3.8.1.303",
       "commands": [
         "mgcb-editor-windows"
       ]
     },
     "dotnet-mgcb-editor-mac": {
-      "version": "3.8.1.263",
+      "version": "3.8.1.303",
       "commands": [
         "mgcb-editor-mac"
       ]

articles/whats_new.md

@@ -20,6 +20,8 @@ MonoGame 3.8.1 now comes with an optional Visual Studio extension which will ins
 
 This extension is available for Visual Studio 2022, and Visual Studio 2022 for Mac.
 
+If you are migrating from 3.8.0 it is recommended to uninstall the existing global MGCB .NET tools. It would be a good idea to review the [Migrating from 3.8.0](migrate_38.md) documentation, as there are changes to how 3.8.1 works with the .NET tools and the new extension.
+
 ## Visual Studio 2019 and prior are no longer supported
 
 Since .NET 6 is not supported by Visual Studio 2019, starting with MonoGame 3.8.1 it will no longer be possible to build games with it.