Skip to content

Commit 02724f4

Browse files
authored
MSTest SDK doc: use latest released version (#43714)
* MSTest SDK doc: use latest released version * Update docs/core/testing/unit-testing-mstest-sdk.md
1 parent 5f1ff82 commit 02724f4

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/core/testing/unit-testing-mstest-sdk.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The MSTest SDK discovers and runs your tests using the [MSTest runner](./unit-te
1919
You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute of the `Project` node of your project:
2020

2121
```xml
22-
<Project Sdk="MSTest.Sdk/3.3.1">
22+
<Project Sdk="MSTest.Sdk/3.6.3">
2323

2424
<PropertyGroup>
2525
<TargetFramework>net8.0</TargetFramework>
@@ -31,7 +31,7 @@ You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute
3131
```
3232

3333
> [!NOTE]
34-
> `/3.3.1` is given as example as it's the first version of the SDK, but it can be replaced with any newer version.
34+
> `/3.6.3` is given as example and can be replaced with any newer version.
3535
3636
To simplify handling of versions, we recommend setting the SDK version at solution level using the _global.json_ file. For example, your project file would look like:
3737

@@ -52,7 +52,7 @@ Then, specify the `MSTest.Sdk` version in the _global.json_ file as follows:
5252
```json
5353
{
5454
"msbuild-sdks": {
55-
"MSTest.Sdk": "3.3.1"
55+
"MSTest.Sdk": "3.6.3"
5656
}
5757
}
5858
```
@@ -90,7 +90,7 @@ You can set the profile using the property `TestingExtensionsProfile` with one o
9090
Here's a full example, using the `None` profile:
9191

9292
```xml
93-
<Project Sdk="MSTest.Sdk/3.3.1">
93+
<Project Sdk="MSTest.Sdk/3.6.3">
9494

9595
<PropertyGroup>
9696
<TargetFramework>net8.0</TargetFramework>
@@ -109,7 +109,7 @@ Extensions can be enabled and disabled by MSBuild properties with the pattern `E
109109
For example, to enable the crash dump extension (NuGet package [Microsoft.Testing.Extensions.CrashDump](https://www.nuget.org/packages/Microsoft.Testing.Extensions.CrashDump)), you can use the following property `EnableMicrosoftTestingExtensionsCrashDump` set to `true`:
110110

111111
```xml
112-
<Project Sdk="MSTest.Sdk/3.3.1">
112+
<Project Sdk="MSTest.Sdk/3.6.3">
113113

114114
<PropertyGroup>
115115
<TargetFramework>net8.0</TargetFramework>
@@ -133,7 +133,7 @@ This property pattern can be used to enable an additional extension on top of th
133133
You can also disable an extension that's coming from the selected profile. For example, disable the `MS Code Coverage` extension by setting `<EnableMicrosoftTestingExtensionsCodeCoverage>false</EnableMicrosoftTestingExtensionsCodeCoverage>`:
134134

135135
```xml
136-
<Project Sdk="MSTest.Sdk/3.3.1">
136+
<Project Sdk="MSTest.Sdk/3.6.3">
137137

138138
<PropertyGroup>
139139
<TargetFramework>net8.0</TargetFramework>
@@ -211,7 +211,7 @@ Add the version to your `global.json`:
211211
```json
212212
{
213213
"msbuild-sdks": {
214-
"MSTest.Sdk": "3.3.1"
214+
"MSTest.Sdk": "3.6.3"
215215
}
216216
}
217217
```

0 commit comments

Comments
 (0)