VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-10 10:00:57 +09:00
Code Activity

Some corrections in build documentation

Browse source 
Commit migrated from 0feb381533
This commit is contained in:
stakx 2018-05-03 17:49:32 +02:00
parent d74a06c5cf
commit 1f3a062eff
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/coreclr/workflow/UsingDotNetCli.md
View file

@ -121,7 +121,7 @@ C:\coreclr\helloWorld\helloWorld.csproj : warning NU1603: helloWorld depends on
### 6. Run the app
After you publish you will find you all the binaries needed to run your application under `bin\Debug\netcoreapp2.1\win-x64\publish\`.
After you publish you will find all the binaries needed to run your application under `bin\Debug\netcoreapp2.1\win-x64\publish\`.
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).
```
@ -148,7 +148,7 @@ the further steps needed to consume the runtime nuget package.
#### 1. Update BuildNumberMinor Environment Variable
One possible problem with this technique is that Nuget assumes that distinct builds have distinct version numbers.
Thus if you modify the source and create a new NuGet package you must it a new version number and use that in your
Thus if you modify the source and create a new NuGet package you must give it a new version number and use that in your
application's project. Otherwise the dotnet.exe tool will assume that the existing version is fine and you
won't get the updated bits. This is what the Minor Build number is all about. By default it is 0, but you can
give it a value by setting the BuildNumberMinor environment variable.

2
docs/coreclr/workflow/UsingYourBuild.md
View file

@ -140,7 +140,7 @@ The location is C:\coreclr\helloWorld\bin\Debug\netcoreapp2.1\win-x64\publish\Sy
## Using DotNetCli to run your .NET Core Application
If you don't like the idea of copying files manually you can follow [this instructions](UsingDotNetCli.md) to use dotnet cli to do this for you.
If you don't like the idea of copying files manually you can follow [these instructions](UsingDotNetCli.md) to use dotnet cli to do this for you.
However the steps described here are the simplest and most commonly used by CoreCLR developers for ad-hoc testing.
## Using CoreRun to run your .NET Core Application