Closed txwizard closed 4 years ago
You'll need to use the .NET Core SDK's dotnet
executable to run the program. You can get this here by selecting Download .NET Core SDK
.
Here is how you can use the dotnet
CLI:
cd Samples\CatalogReaderExample\CatalogReaderExample
dotnet run
Or:
cd Samples\CatalogReaderExample\CatalogReaderExample
dotnet build
dotnet .\bin\Debug\netcoreapp2.0\CatalogReaderExample.dll
Please let us know if you have any additional questions!
Thank you, @loic-sharma for that clear, concise answer.
The fact that the extension was .dll
suggested to me that it might need a character-mode program to host it. However, since I haven't done anything to date with .NET Core, it didn't occur to me that the required character-mode program was dotnet.exe
. Since I have the latest version of Microsoft Visual Studio and virtually every available SDK, I quickly found it in a directory that is already in my PATH list. I had only to enter 'where dotnet.exe` at a command prompt to find it.
Happy to help! Feel free to open another issue if you run into anything else :)
I cloned the NuGet Samples repository, built the debug configuration, and ran it successfully inside Visual Studio. Following is the console log.
The debugger output window listing follows.
The foregoing suggests to me that this is a .Net Core package. I have no prior experience with executing such assemblies. Next, I built the Release configuration, and tried to run it from a command prompt (cmd.exe) with the following outcome.
Examining the source code led me to believe that the assembly was a standard console program.
What fine point did I miss?