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/getting_started/2_choosing_your_ide_vscode.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,9 +78,9 @@ The official Microsoft version includes proprietary features like settings sync,
78
78
79
79
## Setting up VS Code for development with MonoGame
80
80
81
-
1. Open Visual Studio Code
82
-
1. Open up its terminal window (`Ctrl` + `````)
83
-
1. Run the following command to install MonoGame Templates
81
+
1. Open Visual Studio Code.
82
+
1. Open up its terminal window (`Ctrl` + `````).
83
+
1. Run the following command to install MonoGame Templates:
84
84
85
85
```sh
86
86
dotnet new install MonoGame.Templates.CSharp
@@ -141,15 +141,15 @@ The .NET MAUI extension adds features for building mobile apps, including:
141
141
142
142
## Creating a new MonoGame project
143
143
144
-
1. Open up an empty folder in Visual Studio Code
145
-
2. Open up its terminal window (`Ctrl` + `````)
144
+
1. Open up an empty folder in Visual Studio Code.
145
+
2. Open up its terminal window (`Ctrl` + `````).
146
146
3. Run the following command to create an empty project for desktop platforms:
147
147
148
148
```sh
149
149
dotnet new mgdesktopgl
150
150
```
151
151
152
-
4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load
152
+
4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load.
153
153
5. You can now press F5, selectC# and then your projects name if Visual Studio Code asks you, and it should start up your brand new game!
154
154
155
155
## Update Project Tool references
@@ -159,8 +159,8 @@ The MonoGame Content Editor (MGCB) it a tool delivered through NuGet for your pr
159
159
Once you have created your project you should run the following terminal/command-line command to ensure the tool (and the pipeline) is setup and readfor your project:
160
160
161
161
```dotnetcli
162
-
dotnet tool restore
162
+
dotnet tool restore
163
163
```
164
164
165
165
> [!NOTE]
166
-
> If you ever change the version of the tools or want to upgrade them by editing the `dotnet-tools.json` configuration, you MUST run this command again to update te tools.
166
+
> If you ever change the version of the tools or want to upgrade them by editing the `dotnet-tools.json` configuration, you MUST run this command again to update the tools.
Copy file name to clipboardExpand all lines: articles/getting_started/tools/mgcb_editor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ dotnet mgcb-editor
29
29
```
30
30
31
31
> [!NOTE]
32
-
> You will need to buid the project at least once in order for the .NET system to download and register the tool with your project utilizing the `dotnet-tools.json` configuration file located in the `.config` folder, or use the `dotnet tool restore` command shown below.
32
+
> You will need to build the project at least once in order for the .NET system to download and register the tool with your project utilizing the `dotnet-tools.json` configuration file located in the `.config` folder, or use the `dotnet tool restore` command shown below.
0 commit comments