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
{{ message }}
This repository was archived by the owner on Jan 23, 2023. It is now read-only.
@@ -28,9 +28,9 @@ or always fully qualify the path to dotnet in the root of this folder for all th
28
28
29
29
After setting up dotnet you can verify you are using the newer version by:
30
30
31
-
`dotnet --info` -- the version should be greater than 2.0.0-*
31
+
`dotnet --info` -- the version should be greater than 2.1.0-*
32
32
33
-
For another small walkthrough see [Dogfooding .NET Core 2.0 SDK](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/dogfooding.md).
33
+
For another small walkthrough see [Dogfooding .NET Core SDK](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/dogfooding.md).
34
34
35
35
## Create sample self-contained application
36
36
@@ -50,13 +50,13 @@ shared framework. In order to do that you will need to add a `RuntimeIdentifier
50
50
```
51
51
<PropertyGroup>
52
52
...
53
-
<RuntimeIdentifier>win7-x64</RuntimeIdentifier>
53
+
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
54
54
</PropertyGroup>
55
55
```
56
56
57
-
For windows you will want `win7-x64` but for other OS's you will need to set it to the most appropriate one based
57
+
For windows you will want `win-x64` but for other OS's you will need to set it to the most appropriate one based
58
58
on what you built. You can generally figure that out by looking at the packages you found in your output. In our
59
-
example you will see there is a package with the name `runtime.win7-x64.Microsoft.NETCore.Runtime.CoreCLR.2.0.0-beta-25023-0.nupkg`
59
+
example you will see there is a package with the name `runtime.win-x64.Microsoft.NETCore.Runtime.CoreCLR.2.1.0-beta-25023-0.nupkg`
60
60
so you will want to put whatever id is between `runtime.` and `Microsoft.NETCore.Runtime.CoreCLR`.
61
61
62
62
Next you need to restore and publish. The publish step will also trigger a build but you can iterate on build by calling `dotnet build` as
@@ -67,21 +67,17 @@ dotnet restore
67
67
dotnet publish
68
68
```
69
69
70
-
After you publish you will find you all the binaries needed to run your application under `bin\Debug\netcoreapp2.0\win7-x64\publish\`.
70
+
After you publish you will find you all the binaries needed to run your application under `bin\Debug\netcoreapp2.1\win-x64\publish\`.
71
71
To run the application simply run the EXE that is in this publish directory (it is the name of the app, or specified in the project file).
Thus at this point publication directory directory has NO dependency outside that directory (including dotnet.exe). You can copy this publication
78
78
directory to another machine and run the exe in it and it will 'just work' (assuming you are on the same OS). Note that your managed app's
79
79
code is still in the 'app'.dll file, the 'app'.exe file is actually simply a rename of dotnet.exe.
80
80
81
-
**NOTE**: Normally you would be able to run the application by calling `dotnet run` however there is currently tooling issues which lead to an error similar
82
-
to `A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in ...` so to workaround that for
83
-
now you have to manually run the application from the publish directory.
84
-
85
81
86
82
## Update CoreCLR from raw binary output
87
83
@@ -97,7 +93,7 @@ you wish to update the DLLs. For example typically when you update CoreCLR you e
97
93
* System.Private.CoreLib.dll - If you modified C# it will end up here.
98
94
99
95
Thus after making a change and building, you can simply copy the updated binary from the `bin\Product\<OS>.<arch>.<flavor>`
100
-
directory to your publication directory (e.g. `helloWorld\bin\Debug\netcoreapp2.0\win7-x64\publish`) to quickly
96
+
directory to your publication directory (e.g. `helloWorld\bin\Debug\netcoreapp2.1\win-x64\publish`) to quickly
101
97
deploy your new bits. In a lot of cases it is easiest to just copy everything from here to your publication directory.
102
98
103
99
You can build just the .NET Library part of the build by doing (debug, for release add 'release' qualifier)
@@ -138,10 +134,10 @@ this by simply listing the name of the Microsoft.NETCore.Runtime.CoreCLR you bui
138
134
and you will get name of the which looks something like this
0 commit comments