Skip to main content

Publish a console app as a single executable

I created a small console application that automatically adds the application pool users on your local IIS server to the correct groups on the web server so that performance counter data is correctly send to Application Insights.

You can find some extra content, the original announcement and the source code here:

So what is the reason for this post?

When you publish the tool, it resulted in a combination of an exe and multiple DLL’s:

This means that you need to copy all these files to be able to run the tool. It would be nice if there was only a single executable.

Let’s see how to get this done…

Switch to single file publish

Open up the csproj file and add the following line:

The resulting csproj file looks like this:

If we now try to publish our application again through dotnet publish we only have a single executable:

Remark: Notice that we also have a runtime identifier set. If you don’t set this, you need to specify this when calling the dotnet publish command, e.g. dotnet publish -r win-x64

We can also get rid of the separate pdb file by changing the debugtype to embedded in the csproj:

More information

Create a single file for application deployment - .NET | Microsoft Learn

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.