|
1 | | -# How to get up and running on .NET Core 2.0 |
| 1 | +# How to get up and running on .NET Core |
2 | 2 |
|
3 | 3 | This document provides the steps necessary to consume a nightly build of |
4 | | -.NET Core 2.0 runtime and SDK. |
| 4 | +.NET Core runtime and SDK. |
5 | 5 |
|
6 | 6 | Please note that these steps are likely to change as we're simplifying |
7 | 7 | this experience. Make sure to consult this document often. |
8 | 8 |
|
9 | 9 | ## Install prerequisites |
10 | 10 |
|
11 | | -1. Acquire the latest nightly .NET Core SDK 2.0 by downloading the zip or tarball listed in https://github.com/dotnet/cli/blob/master/README.md#installers-and-binaries (for example, https://dotnetcli.blob.core.windows.net/dotnet/Sdk/master/dotnet-sdk-latest-win-x64.zip ) into a new folder. |
| 11 | +1. Acquire the latest nightly .NET Core SDK by downloading the zip or tarball listed in https://github.com/dotnet/cli/blob/master/README.md#installers-and-binaries (for example, https://dotnetcli.blob.core.windows.net/dotnet/Sdk/master/dotnet-sdk-latest-win-x64.zip ) into a new folder. |
12 | 12 |
|
13 | 13 | 2. By default, the dotnet CLI will use the globally installed SDK if it matches the major/minor version you request and has a higher revision. To force it to use the locally installed SDK, you must set an environment variable `DOTNET_MULTILEVEL_LOOKUP=0` in your shell. You can use `dotnet --info` to verify what version of the Shared Framework it is using. |
14 | 14 |
|
@@ -68,7 +68,7 @@ Rinse and repeat! |
68 | 68 | ## Advanced Scenario - Using a nightly build of Microsoft.NETCore.App |
69 | 69 |
|
70 | 70 | When using the above instructions, your application will run against the same |
71 | | -.NET Core 2.0 runtime that comes with the SDK. That works fine to get up and |
| 71 | +.NET Core runtime that comes with the SDK. That works fine to get up and |
72 | 72 | running quickly. However, there are times when you need to use a nightly build |
73 | 73 | of Microsoft.NETCore.App which hasn't made its way into the SDK yet. To enable |
74 | 74 | this, there are two options you can take. |
@@ -110,14 +110,14 @@ make it self-contained |
110 | 110 | <OutputType>Exe</OutputType> |
111 | 111 | <TargetFramework>netcoreapp2.1</TargetFramework> |
112 | 112 | <RuntimeFrameworkVersion>2.1.0-preview1-25825-07</RuntimeFrameworkVersion> <!-- modify build in this line --> |
113 | | - <RuntimeIdentifier>win7-x64</RuntimeIdentifier> <!-- make self-contained --> |
| 113 | + <RuntimeIdentifier>win-x64</RuntimeIdentifier> <!-- make self-contained --> |
114 | 114 | </PropertyGroup> |
115 | 115 | ``` |
116 | 116 |
|
117 | 117 | ``` |
118 | 118 | $ dotnet restore |
119 | 119 | $ dotnet publish |
120 | | -$ bin\Debug\netcoreapp2.1\win7-x64\publish\App.exe |
| 120 | +$ bin\Debug\netcoreapp2.1\win-x64\publish\App.exe |
121 | 121 | ``` |
122 | 122 |
|
123 | 123 | ## More Advanced Scenario - Using your local CoreFx build |
|
0 commit comments