3 ms·
But the topic is specifically freestanding executables, not compatibility in general. If it utilises an external DLL, or library then it isn't freestanding, as
by Someone1234 11y ago
But the topic is specifically freestanding executables, not compatibility in general. If it utilises an external DLL, or library then it isn't freestanding, as a .Net 3.5 program typically isn't (although I think Microsoft has a .Net native compiler now, but I don't know if that can be configured to push external dependencies into the executable package).
Don't misunderstand, I like .Net, I just think you've misunderstood what is being discussed.
- padobson 11y agoFrom the Windows 7 user's perpsective, there's no difference. It's understood that this article is meant to discuss zero-install applications that require nothing more than the standard C library. That said, if you're making and marketing software (as I would expect a few visitors of this thread might) and looking to accomplish something functionally similar with your C# or VBScript dev team, my comment can be helpful - which is why I wrote it. I've shipped a number of sub-5MB applications this way.
- Someone1234 11y ago> It's understood that this article is meant to discuss zero-install applications that require nothing more than the standard C library. No, they are zero install, including NOT requiring a C library. No libraries at all. They're communicating directly with kernel32 from userland. On Windows that's as "bare metal" as a non-driver can really get.