Compile a .NET Core application as an EXE file using Visual Studio 2017

by

Update 2019:

.NET Core 3.0+ projects will now include an executable for the platform you build on by default. This is just a shim executable and your main logic is still inside a .dll file.

But .NET Core 3.0 also introduced single-file deployments so deploying with

dotnet publish -r win-x64 -p:PublishSingleFile=True --self-contained false

will create a single .exe file containing all your dependencies. You can change --self-contained to true to also include the .NET Core Runtime as well so .NET Core does not need to be installed globally on the target machine.

Original

.NET Core applications are supposed to be .dllfiles. OutputType set to Exe in this case means “executable” and does everything necessary to ensure that the output is runnable (entry point from Main() method, .runtimeconfig.json file). The resulting DLL file is meant to be run using:

dotnet yourapp.dll

This DLL file works across all platforms that are supported by the .NET Core runtime (Windows, Linux, and macOS). This is called a “portable” or “framework dependent” deployment.

If you want really a .exe file, consider self-contained deployments. This will create an output that contains its own copy of the .NET Core runtime and an yourapp.exe file – but it also increases the size of the published application and it needs to be updated when new versions of the runtime are released.

Also, the resulting application only works on the operating system published for.

Refer to .NET Core application deployment for more details on the deployment options and how to set them up.

More Related Contents:

  1. How to get “Manage User Secrets” in a .NET Core console-application?
  2. Visual studio 2017 Update 3 – The SDK ‘Microsoft.NET.Sdk.Web’ specified could not be found
  3. Build .NET Core console application to output an EXE
  4. Equivalent to AssemblyInfo in dotnet core/csproj
  5. How do you multi-target a .NET Core class library with csproj?
  6. Assets file project.assets.json not found. Run a NuGet package restore
  7. Compatibility shim used by .NET Standard 2.0
  8. Auto Versioning in Visual Studio 2017 (.NET Core)
  9. Copy all dependencies from .Net Standard libraries to .Net Framework Console application
  10. ef core doesn’t use ASPNETCORE_ENVIRONMENT during update-database
  11. Should HttpClient instances created by HttpClientFactory be disposed?
  12. .NET Core app unable to start in IIS due to ErrorCode = ‘0x80004005 : 80008083
  13. Failed to find a valid digest in the ‘integrity’ attribute for resource in Blazor app
  14. Use HttpClientFactory from .NET 4.6.2
  15. How to read AppSettings values from a .json file in ASP.NET Core
  16. Return file in ASP.Net Core Web API
  17. SQL Server named instance with Visual Studio 2017 Installer project
  18. Where does Visual Studio 2017 store its config?
  19. dotnet core System.Text.Json unescape unicode string
  20. Visual Studio installer fails on AspNetDiagnosticPack.msi
  21. Automatic native and managed DLLs extracting from Nuget Package
  22. Windows Forms Designer and WPF Designer for .NET Core
  23. Send HTTP POST message in ASP.NET Core using HttpClient PostAsJsonAsync
  24. dotnet publish doesn´t publish correct appsettings.{env.EnvironmentName}.json
  25. Proper way to start and fire-and-forget asynchronous calls?
  26. .NET Core: Remove null fields from API JSON response
  27. System.Text.Json: Deserialize JSON with automatic casting
  28. Azure – Unhandled Exception: System.IO.FileNotFoundException
  29. How to get user information in DbContext using Net Core
  30. .NET Core equivalent to Thread.Abort

Leave a Comment