Skip to main content

Return to Answer

Active reading [<https://en.wikipedia.org/wiki/Dynamic-link_library> <https://en.wikipedia.org/wiki/EXE> <https://en.wikipedia.org/wiki/Microsoft_Windows>]. Expanded.
Source Link
Peter Mortensen
Peter Mortensen
  • 31.4k
  • 22
  • 110
  • 134

For debugging purposes, you can use the dllDLL file. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exeEXE file, you have to generate a self-contained application.

To generate a self-contained application (exeEXE in windowsWindows), you must specify the target runtime (which is specific to the OSoperating system you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj .csproj file (list of supported ridRIDs):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purposes, you can use the dll file. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specify the target runtime (which is specific to the OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purposes, you can use the DLL file. You can run it using dotnet ConsoleApp2.dll. If you want to generate an EXE file, you have to generate a self-contained application.

To generate a self-contained application (EXE in Windows), you must specify the target runtime (which is specific to the operating system you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the .csproj file (list of supported RIDs):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64
Made grammar and sentence structure corrrections
Source Link
edit approved Apr 6, 2019 at 13:16
Raj Narayanan
edit approved Apr 6, 2019 at 13:16
Raj Narayanan
  • 3.6k
  • 7
  • 34
  • 62

For debugging purposepurposes, you can use the dll file. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specifiedspecify the target runtime (which is specific to the OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purpose, you can use the dll. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specified the target runtime (which OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purposes, you can use the dll file. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specify the target runtime (which is specific to the OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64
syntax-highlighting
Source Link
Frederik Struck-Schøning
Frederik Struck-Schøning
  • 13.3k
  • 9
  • 63
  • 70

For debugging purpose, you can use the dll. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specified the target runtime (which OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup> 
<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purpose, you can use the dll. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specified the target runtime (which OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64

For debugging purpose, you can use the dll. You can run it using dotnet ConsoleApp2.dll. If you want to generate an exe, you have to generate a self-contained application.

To generate a self-contained application (exe in windows), you must specified the target runtime (which OS you target).

Pre-.NET Core 2.0 only: First, add the runtime identifier of the target runtimes in the csproj (list of supported rid):

<PropertyGroup> <RuntimeIdentifiers>win10-x64;ubuntu.16.10-x64</RuntimeIdentifiers> </PropertyGroup>

The above step is no longer required starting with .NET Core 2.0.

Then, set the desired runtime when you publish your application:

dotnet publish -c Release -r win10-x64 dotnet publish -c Release -r ubuntu.16.10-x64
added 97 characters in body
Source Link
mklement0
mklement0
  • 452.5k
  • 68
  • 728
  • 988
added 201 characters in body
Source Link
meziantou
meziantou
  • 21.5k
  • 7
  • 73
  • 89
Source Link
meziantou
meziantou
  • 21.5k
  • 7
  • 73
  • 89