10 ms·
>> Single files apps no longer extract any core runtime assemblies to temporary directories I might be ignorant here but if you're not specifically pointing ou
by kreeben 5y ago
>> Single files apps no longer extract any core runtime assemblies to temporary directories
I might be ignorant here but if you're not specifically pointing out what version DLL's you want, aren't you in fact publishing a dynamically linked executable instead of a statically linked one?
Doesn't these single-file apps rely on the GAC?
- sedatk 5y agoThe whole runtime gets included in the binary.
- BiteCode_dev 5y agoDoes this mean you need one binary per OS so that the runtime matches, or do they do some magic so that one single binary can run on all Oses ?
- sebastienros 5y agoYou create one binary per OS.
- jonathanlydall 5y agoYou create a single binary which has the runtime and dependencies self contained within. You of course have to choose your target platform for this as it makes .exes for Windows, ELFs for Linux, etc. If you want you can still choose to distribute IL DLLs and users then use their already installed dotnet on their machine to run them.
- e12e 5y ago> You of course have to choose your target platform for this (...) https://github.com/jart/cosmopolitan https://github.com/jart/cosmopolitan (but, yeah, you probably want one version per target, even if hacks are cool)
- kingcharles 5y agoThis actually makes sense in 2021 since we have the resources to allow things like this. 20 years ago this might have seemed insane.
- vidanay 5y ago30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.
- justin66 5y agoOn the contrary, 30 years ago we were using Windows 3.0, which is about when dll hell started being a real thing. (DLL hell stopped being a problem a lot sooner than you probably think, too...)
- nisegami 5y ago>DLL hell stopped being a problem a lot sooner than you probably think, too Does not match my experience at work unfortunately.
- justin66 5y agoIf you're seeing this on any version of Windows made in the last 22 years or so, it's because a software developer fucked up in a really creative way. My condolences. Sometimes the issue is that people have tended to conflate "dll hell" and "dependency hell." That's an old pet peeve of mine and I realize it doesn't matter...
- ourmandave 5y ago"Insert floppy disk 435 of 880 and press [Enter] when ready..."
- vidanay 5y agoInvalid media type Abort, Retry, Fail? FFFFFFFUUUUUUUUCCCCCCKKKKK!!!!!!
- Rebelgecko 5y agoHow much does this add to the binary's size?
- aha_throwaway 5y agoIn my case about 60MB
- ripley12 5y agoSomething like 60MB if the application is not trimmed. Closer to 10MB if the application can be trimmed.
- voxic11 5y agoThere is no GAC. > .NET Core and .NET 5 and later versions eliminate the concept of the global assembly cache (GAC)
- backoncemore 5y agoInteresting. I haven't worked in .NET for several years now, but the GAC was always an absolute headache to deal with.
- exyi 5y agoThankfully they did not port this hell to Linux
- cm2187 5y agoSurely the binaries generated by the JIT still get cached somewhere?
- h3h3 5y agoyou can set a ReadyToRun flag on publish which pre jits your dlls https://docs.microsoft.com/en-us/dotnet/core/deploying/ready-to-run https://docs.microsoft.com/en-us/dotnet/core/deploying/ready...