❔ Net 7 How to output one exe without dlls

Halp $singlefile didnt worked

dotnet publish -c Release -r <runtime identifier> -p:PublishSingleFile=true
Use of -r|--runtime implies --self-contained true. Add --self-contained false to publish as runtime-dependent.
-r RID and -p:PublishSingleFile=true can be moved to .csproj as the following properties:

<RuntimeIdentifier>RID</RuntimeIdentifier>
<PublishSingleFile>true</PublishSingleFile>

but to target multiple RIDs, you have to use dotnet publish with the -r option for each RID.
You can also add -p:IncludeNativeLibrariesForSelfExtract=true to include native libraries (like Common Language Runtime dlls) in the output executable.
You might want to instead publish your application compiled Ahead Of Time to native code, see $nativeaot.
https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file
https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-publish

and the exe doenst run without the dll

sooo

what did you try?

dotnet publish -c Release -r <runtime identifier> -p:PublishSingleFile=true

you have to replace <runtime identifier> with a... runtime identifier

yes

i did

translate plz

done

Try adding --self-contained

Task "ResolveComReference" is not supported on .NET Core version of MSBuild. Use the MSBuild version of the .NET Framework. See

yeah idk what that's about :/

thaths because i have windows media player on proyect?

For context: the project was migrated from Fx 4.8 to .NET 7 using the Upgrade Assistant ( #❔ nul )

ah

finali i just created a new and do it all myself

Upgrade Assistant broke everything

the output is proyectname.exe and proyectname.dll

i just want both only one exe

oh

-c release

Doenst work :C

have you tried dotnet publish -c Release -r <rid> --self-contained -p:PublishSingleFile=true?

Also can you show your csproj file?

thath i was gonna do

because i was modifyng it befotre

Well afaik you can delete StartupObject, ApplicationIcon, and PlatformTarget, and you can also delete PublishSingleFile and RuntimeIdentifier since you can specify those when running dotnet publish

is that the entire file?

sry

Looks like this is the issue

<ItemGroup>
  <COMReference Include="WMPLib">
    <WrapperTool>tlbimp</WrapperTool>
    <VersionMinor>0</VersionMinor>
    <VersionMajor>1</VersionMajor>
    <Guid>6bf52a50-394a-11d3-b153-00c04f79faa6</Guid>
    <Lcid>0</Lcid>
    <Isolated>false</Isolated>
    <EmbedInteropTypes>true</EmbedInteropTypes>
  </COMReference>
</ItemGroup>

yes

but i need it for the music

<Exec Command="Obfuscar.Console.exe config.xml" />

are you... running an obfuscator

yes 😭

well you can get rid of that

why

obfuscation in .NET is literally useless

hmm

on framework works

yeah, the error message above says that COMReference isn't a thing you can use with modern versions of .NET

you can steale whole proyect with a single decompiler

yep

thaths because i use it then

you can still do that with obfuscated code

takes a bit more effort, but that ain't gonna stop a determined dataminer

$obfuscation

"Then finally, there is that question of code privacy. This is a lost cause. There is no transformation that will keep a determined hacker from understanding your program. This turns out to be true for all programs in all languages, it is just more obviously true with JavaScript because it is delivered in source form. The privacy benefit provided by obfuscation is an illusion. If you don’t want people to see your programs, unplug your server."
- Douglas Crockford
https://softwareengineering.stackexchange.com/a/155133

* Spend your effort on putting proprietary things in your api, and keeping the distributed code as empty as possible
* Use AuthN/AuthZ to control who/what/when/etc...
* Free obfuscation is worth the amount your paid for it -- it's already broken and most decompilers out there can make sense of it.
* Paid ofbuscation will bankrupt you unless you have a very strong revenue stream and can justify the additional cost with gained sales
* The "threat" of someone hijacking your UI and shimming it to make it provide them money is not a real threat. If this is legitimate software, you can ruin their business with lawsuits
- Cisien

ok so i cant use windows media player

yea i nkow

oh that's what WMPLib stands for lmao

yeah no I think you'll have to find some other way to play music in a console app (...?)

Naudio?

looks like a start

You probably want this
https://github.com/naudio/NAudio/blob/master/Docs/PlayAudioFileConsoleApp.md

thaths what i said

yes

(that specific tutorial)

this i think will be perfect

thanks

ok let me try again the compile with single file

dotnet publish -c Debug -r win-x64 -p:PublishSingleFile=true

i have to run this every time oln cimpile?

well, every time you want to publish your app

but just i want to compile in just one file

ex. when you release a new version

yeah, dotnet publish -c Release -r <rid> --self-contained -p:PublishSingleFile=true will publish your entire app into a single executable file

now i got another error

PM> Send a message on "Net 7 How to output one exe without dlls"
Submit : The term 'Submit' is not recognized as the name of a cmdlet, function, script file, or executable program. Check if you typed the name correctly, or if you included a path, check that the path is correct and try again.
Online: 1 Character: 1
+ Send a message on "Net 7 How to output one exe without dlls"
+~~
+ CategoryInfo : ObjectNotFound: (Send:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

oh nothing

im stupid

dotnet publish -c Debug -r win-x64 -p:PublishSingleFile=true --self-contained

wtf 147 MB of file

yeah, since single-file app have to pack all the DLLs as well as the entire runtime into the exe, the file sizes tend to be a couple orders of magnitudes larger than regular apps

and that's just an inherent part of single-file executables

on framework and costura fody was 2 mb

....

a couple

i got this error

i cant start thath

on framework worked

afaik you have to use the Powershell setting for Process to be able to start URLs

what

process start doenst have use shell executed enabled by default?

apparently not

but on framework yes

😭

idk

Framework is weird

there is no way to be packed as 1 file without packing whole net libraries

just the program dll and the nuget dependencyes

well, .NET libraries are essentially the same as Nuget dependencies

They're all just... DLLs

but