summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorDan Moseley <danmose@microsoft.com>2019-05-12 00:14:56 (GMT)
committerJan Kotas <jkotas@microsoft.com>2019-05-12 00:14:56 (GMT)
commitafe95bac41dbd65e623c2cdc8a776a18e6a6e789 (patch)
treed7fee30c2629d471c69786829d4f87eee1ccab11 /Documentation
parente0fd735a866861b35679ac503193809a305fac2b (diff)
downloadcoreclr-afe95bac41dbd65e623c2cdc8a776a18e6a6e789.zip
coreclr-afe95bac41dbd65e623c2cdc8a776a18e6a6e789.tar.gz
coreclr-afe95bac41dbd65e623c2cdc8a776a18e6a6e789.tar.bz2
Update UsingYourBuild.md (#24389)
Change MyGet to the custom feeds. I found that for dotnet new console to restore, I needed an ASP.NET feed as well.
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/workflow/UsingYourBuild.md33
1 files changed, 31 insertions, 2 deletions
diff --git a/Documentation/workflow/UsingYourBuild.md b/Documentation/workflow/UsingYourBuild.md
index 2624e60..da301c9 100644
--- a/Documentation/workflow/UsingYourBuild.md
+++ b/Documentation/workflow/UsingYourBuild.md
@@ -64,10 +64,23 @@ needed.
dotnet publish
```
-**Note:** If publish fails to restore runtime packages you need to configure custom NuGet feed. To do so you have to:
+**Note:** If publish fails to restore runtime packages you need to configure custom NuGet feeds. This is because you are using a dogfood .NET Core SDK: its dependencies are not yet on the regular NuGet feed. To do so you have to:
1. run `dotnet new nugetconfig`
-2. go to the `NuGet.Config` file and add `<add key="dotnet-core" value="https://dotnet.myget.org/F/dotnet-core/api/v3/index.json" />`
+2. go to the `NuGet.Config` file and replace the content with:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+ <packageSources>
+ <!--To inherit the global NuGet package sources remove the <clear/> line below -->
+ <clear />
+ <add key="nuget" value="https://api.nuget.org/v3/index.json" />
+ <add key="dotnetcore-feed" value="https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json" />
+ <add key="aspnetcore" value="https://dotnetfeed.blob.core.windows.net/aspnet-aspnetcore/index.json" />
+ </packageSources>
+</configuration>
+```
After you publish you will find you all the binaries needed to run your application under `bin\Debug\netcoreapp3.0\win-x64\publish\`.
@@ -128,6 +141,22 @@ Hello World from Core 4.6.26210.0 @BuiltBy: adsitnik-MININT-O513E3V @SrcCode: ht
The location is C:\coreclr\helloWorld\bin\Debug\netcoreapp3.0\win-x64\publish\System.Private.CoreLib.dll
```
+### If it's not using your copied binary
+
+Make sure you are running the exe directly. If you use `dotnet run` it will overwrite your custom binaries before executing the app:
+
+```
+.\bin\Debug\netcoreapp3.0\win-x64\publish\HelloWorld.exe
+```
+
+### If you get a consistency check assertion failure
+
+Something like this happens if you copied coreclr.dll but not System.Private.Corelib.dll as well.
+
+```
+Assert failure(PID 13452 [0x0000348c], Thread: 10784 [0x2a20]): Consistency check failed: AV in clr at this callstack:
+```
+
## Using DotNetCli to run your .NET Core Application
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.