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: docs/core/testing/unit-testing-mstest-sdk.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ The MSTest SDK discovers and runs your tests using the [MSTest runner](./unit-te
19
19
You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute of the `Project` node of your project:
20
20
21
21
```xml
22
-
<ProjectSdk="MSTest.Sdk/3.3.1">
22
+
<ProjectSdk="MSTest.Sdk/3.6.3">
23
23
24
24
<PropertyGroup>
25
25
<TargetFramework>net8.0</TargetFramework>
@@ -31,7 +31,7 @@ You can enable `MSTest.Sdk` in a project by simply updating the `Sdk` attribute
31
31
```
32
32
33
33
> [!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.
35
35
36
36
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:
37
37
@@ -52,7 +52,7 @@ Then, specify the `MSTest.Sdk` version in the _global.json_ file as follows:
52
52
```json
53
53
{
54
54
"msbuild-sdks": {
55
-
"MSTest.Sdk": "3.3.1"
55
+
"MSTest.Sdk": "3.6.3"
56
56
}
57
57
}
58
58
```
@@ -90,7 +90,7 @@ You can set the profile using the property `TestingExtensionsProfile` with one o
90
90
Here's a full example, using the `None` profile:
91
91
92
92
```xml
93
-
<ProjectSdk="MSTest.Sdk/3.3.1">
93
+
<ProjectSdk="MSTest.Sdk/3.6.3">
94
94
95
95
<PropertyGroup>
96
96
<TargetFramework>net8.0</TargetFramework>
@@ -109,7 +109,7 @@ Extensions can be enabled and disabled by MSBuild properties with the pattern `E
109
109
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`:
110
110
111
111
```xml
112
-
<ProjectSdk="MSTest.Sdk/3.3.1">
112
+
<ProjectSdk="MSTest.Sdk/3.6.3">
113
113
114
114
<PropertyGroup>
115
115
<TargetFramework>net8.0</TargetFramework>
@@ -133,7 +133,7 @@ This property pattern can be used to enable an additional extension on top of th
133
133
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>`:
134
134
135
135
```xml
136
-
<ProjectSdk="MSTest.Sdk/3.3.1">
136
+
<ProjectSdk="MSTest.Sdk/3.6.3">
137
137
138
138
<PropertyGroup>
139
139
<TargetFramework>net8.0</TargetFramework>
@@ -211,7 +211,7 @@ Add the version to your `global.json`:
0 commit comments