Last post Mar 19, 2017 02:28 AM by Vince2010
Mar 18, 2017 01:46 PM|Vince2010|LINK
Mar 18, 2017 02:50 PM|bruce (sqlwork.com)|LINK
Mar 18, 2017 08:29 PM|Vince2010|LINK
Thank you for your reply...
However, what you told me is not altogether true.
Using the cmd line I ran "dotnet publish -r "RID" and it produced a folder that contained an EXE, named using my project name.
By clicking the EXE, the cmd prompt opens, and Kestrel runs on http://localhost:5000 and blocks the prompt while listening.
I also tested this on an empty VM, and it worked.
Nonetheless, I can run Kestrel without using "dotnet run", but the size of the published folder was 46MB.
When I attempted to delete a DLL that I considered irrelevant, the web server would not run.
I thought .NetCore was a modular framework that allowed you to pick and choose what was added to the final build.
If that is true, How do I achieve that?
Mar 18, 2017 09:54 PM|bruce (sqlwork.com)|LINK
all -r does under the covers is copy dotnet.exe to a new name and included all core runtime files (assumes .net core is not installed on the target system). all the dll's in the release folder are required. publish -r will be larger because it assumes
dotnet core is not installed on target system, and includes all runtime files in a dotnet runtime install.
what in the final build is controlled by which nuget packages are included in the project.
note: if you know dotnet is installed on the target system, don't use publish -r. just use:
dotnet publish -c release -o publishFolder
Mar 19, 2017 02:28 AM|Vince2010|LINK
It all makes sense now.