Include .NET Core Workload

The .NET Core workload brings down the shared runtime component. That is needed when our core clr tests are run.
dotnet · Nov 30, 2017 · 5eb76b2 · nguerrera · Dec 1, 2017 · jaredpar
1 parent 17d6bcf
commit 5eb76b2
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/contributing/Building, Debugging, and Testing on Windows.md b/docs/contributing/Building, Debugging, and Testing on Windows.md
@@ -21,7 +21,7 @@ If a stack trace is displayed on .NET Framework older than 4.7.1 (e.g. by xUnit
 ## Developing with Visual Studio 2017
 
 1. [Visual Studio 2017 Update 3](https://www.visualstudio.com/vs/)
-    - Ensure C#, VB, MSBuild and Visual Studio Extensibility are included in the selected work loads
+    - Ensure C#, VB, MSBuild, .NET Core and Visual Studio Extensibility are included in the selected work loads
     - Ensure Visual Studio is on Version "15.3" or greater
 1. [.NET Core SDK 2.2](https://www.microsoft.com/net/download/core) (if you don't see the 2.1 SDK binaries there yet, the current previews are: [Windows x64 installer](https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.2.0-preview1-007622/dotnet-sdk-2.2.0-preview1-007622-win-x64.exe), [Windows x86 installer](https://dotnetcli.blob.core.windows.net/dotnet/Sdk/2.2.0-preview1-007622/dotnet-sdk-2.2.0-preview1-007622-win-x86.exe))
 1. [PowerShell 3.0 or newer](https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell). If you are on Windows 10, you are fine; you'll only need to upgrade if you're on Windows 7. The download link is under the "upgrading existing Windows PowerShell" heading.