You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/migrate_38.md
+15-4Lines changed: 15 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,12 @@ Migrating from 3.8.0 should be straightforward for most platforms.
9
9
10
10
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.
11
11
12
-
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.
12
+
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.
13
+
14
+
15
+
::: note
16
+
It is also recommended that you uninstall the older global versions of the .NET tools as described below.
17
+
:::
13
18
14
19
## WindowsDX, DesktopGL, and UWP
15
20
@@ -30,16 +35,22 @@ Then edit your MonoGame ```PackageReference``` to point to 3.8.1:
30
35
31
36
### Accessing MGCB and MCGB Editor without a global tool
32
37
33
-
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:
38
+
The MGCB Editor is no longer a .NET global tool, and does not 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:
34
39
35
40
```
36
41
dotnet tool uninstall dotnet-mgcb -g
37
42
dotnet tool uninstall dotnet-2mgfx -g
38
43
dotnet tool uninstall dotnet-mgcb-editor -g
39
44
```
45
+
46
+
::: tip
40
47
**Do not** run the ``` dotnet tool install ``` on 3.8.1, as it would break 3.8.1.
48
+
:::
49
+
50
+
You will also need to setup a dotnet-tools configuration file.
41
51
42
-
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:
52
+
- Next to your ```.csproj```create a folder named ```.config```
53
+
- Add a file within the folder named ```dotnet-tools.json``` with the following content:
43
54
44
55
```json
45
56
{
@@ -80,7 +91,7 @@ You will also need to setup a dotnet-tools configuration file. Next to your ```.
80
91
}
81
92
```
82
93
83
-
Please note that you can't use the ```3.8.1.*``` wildcard in the ```dotnet-tools.json``` file (tool versions have to be fully qualified). We strongly recommand that the versions match the MonoGame version referenced in your ```.csproj``` (if you're using the ```*``` wildcard, make sure that they don't end up mismatching if the nugets are updated without you noticing).
94
+
Please note that you cannot use the ```3.8.1.*``` wildcard in the ```dotnet-tools.json``` file (tool versions have to be fully qualified). We strongly recommand that the versions match the MonoGame version referenced in your ```.csproj``` (if you are using the ```*``` wildcard, make sure that they do not end up mismatching if the nugets are updated without you noticing).
84
95
85
96
You will also need to add this to your ```.csproj```:
0 commit comments