Trying to use msbuild with publish to create single file executable - but multiple files created and the executable does not work

Question

0.00/5 (No votes)

See more:

I want a single file executable capable of being run by itself and no other dll's, etc.

I ran msbuild /t:Publish

No error messages, but result is not what I want. Result is that in the Debug folder an app.publish folder is created containing a setup file, an executable, manifest file, and a folder('Application Files') with another folder containing two files ending in .deploy and .manifest.

When I try to run the executable(not the setup application created), the following exceptions happen:

Unhandled Exeception: System.TypeInitializationException
System.IO.FileNotFoundException: could not load file or assembly library12(dll) or one of its dependencies

The above exceptions pop up briefly in a black screen and then disappear.

What I have tried:

I tried modifying the csproj to set PublishSingleFile and IncludeNativeLibrariesForSelfExtract to true

but to no avail. Thank you guys again!

Posted 20-Aug-24 0:49am

Pada Temp

Updated 20-Aug-24 0:52am

v3

Add a Solution

Comments

[no name] 20-Aug-24 8:17am

If you just want a single executable program, then do not use "Publish". Just build your application and copy the executable that is produced.

Pada Temp 20-Aug-24 9:12am

I should have included the following detail in the post, but I have tried what you are suggesting, i.e. using Build and the executable file produced. The issue I confronted was that it creates files in addition to the executable (e.g. dll's, etc). I am looking for a way to have everything in just one (presumably larger sized) executable without any additional files/dll's. Thank you!

[no name] 20-Aug-24 9:22am

If your application targets DLL libraries then you need to include them with the executable. You probably need to forget what you are trying to do and use the proper tools provided by Microsoft.

Pada Temp 20-Aug-24 9:24am

Yes, DLL libraries are targeted and they should be included in the executable. I am using a Visual Studio, but is there another Microsoft tool that should be used?

[no name] 20-Aug-24 9:29am

DLL libraries are NOT included in executables. The whole point of them is that they are shared between multiple applications, so it does not make sense to build them into single applications.

Pada Temp 20-Aug-24 9:41am

Good to know. I guess I can just have the DLLs then. I guess I initially thought it might be possible to bundle everything as one executable (even the DLLs).

PIEBALDconsult 20-Aug-24 9:57am

Won't work. Unless the DLLs are built from your code, in which case you're in control anyway.

I have tried to embed third-part DLLs in an application and it was unsatisfactory.

Pada Temp 20-Aug-24 10:24am

Yep running into a roadblock here too. Thank you for sharing your experience.

PIEBALDconsult 20-Aug-24 10:37am

I should also note that I don't use msbuild; I just use the command line compiler (CSC) directly.

Dave Kreskowiak 20-Aug-24 9:46am

There's a couple of requirements for a single-file executable. First, you MUST be using .NET 6.0 or above, and second, you must enable the PublishingSingleFile option in your project .csproj file.

Be warned, this can generate very large executables, depending on your application. If you also include the SelfContained option, be prepared for MASSIVE executables.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Answer 1 · 2024-08-20T06:58:00

Assuming you are using .NET Core, take a look at the first answer and screendumps for the publishing settings here:
https://stackoverflow.com/questions/49967697/make-net-core-console-app-a-single-exe[^]
Make sure you have both the self-contained and single file options selected.

When using older .NET versions, e.g. 4.8 or older, you can use Fody Costura to generate a single exe:
GitHub - Fody/Costura: Embed references as resources[^]