6 ms·

The whole runtime gets included in the binary.

by sedatk 5y ago

BiteCode_dev 5y ago
Does 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 ago
  You create one binary per OS.
- jonathanlydall 5y ago
  You 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 ago
This 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 ago
  30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.
  - justin66 5y ago
    On 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 ago
        If 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 ago
    Invalid media type Abort, Retry, Fail? FFFFFFFUUUUUUUUCCCCCCKKKKK!!!!!!
- svick 5y ago
  Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime. Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.
- cm2187 5y ago
  Keeping in mind it's also a double edge sword. TLS deprecations alone will ensure your app will die after a few years if it doesn't run on an up-to-date CLR.
  - dotancohen 5y ago
    This sounds quite the argument for basing critical workflows only on software for which the user has both access and permission to modify the source code.
  - alasdair_ 5y ago
    Timezone and DST fuckery is another, I assume?
Rebelgecko 5y ago
How much does this add to the binary's size?
- aha_throwaway 5y ago
  In my case about 60MB
- ripley12 5y ago
  Something like 60MB if the application is not trimmed. Closer to 10MB if the application can be trimmed.

The whole runtime gets included in the binary.

by sedatk 5y ago

The whole runtime gets included in the binary.

Does 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 ago
You create one binary per OS.
jonathanlydall 5y ago
You 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 ago

This 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 ago
30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.
- justin66 5y ago
  On 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 ago
      If 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 ago
  Invalid media type Abort, Retry, Fail? FFFFFFFUUUUUUUUCCCCCCKKKKK!!!!!!
svick 5y ago
Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime. Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.
cm2187 5y ago
Keeping in mind it's also a double edge sword. TLS deprecations alone will ensure your app will die after a few years if it doesn't run on an up-to-date CLR.
- dotancohen 5y ago
  This sounds quite the argument for basing critical workflows only on software for which the user has both access and permission to modify the source code.
- alasdair_ 5y ago
  Timezone and DST fuckery is another, I assume?

Rebelgecko 5y ago

How much does this add to the binary's size?

aha_throwaway 5y ago
In my case about 60MB
ripley12 5y ago
Something like 60MB if the application is not trimmed. Closer to 10MB if the application can be trimmed.