Hacker News Reader

Comment by badsectoracula | Hacker News Reader

Yes but will this 'required runtime provided by the system' be part of Windows like it is with .NET Framework 4 (that is also updated automatically via Windows updates) or something that the user will have to go out of their way to install like Java?

In many cases, this is the crucial difference between deciding to bundle the runtime yourself or not.

View on HN

This is already supported in dotnet core 2.2 so I would assume it will continue to be supported. https://docs.microsoft.com/en-us/dotnet/core/deploying/#fram...

> Starting with .NET Core 2.2, you can deploy your app as an FDE, along with any required third-party dependencies. Your app will use the version of .NET Core that's installed on the target system.

> Your app can be run by calling the published executable without invoking the dotnet utility directly.

Well, even at present there's no guarantee the end user has the version of .net framework and libraries you need. You might need 4.8.x stuff and they only have 4.7.x. Maybe they're on win8 and not 10, or they're behind on updates, etc.

Typically the solution for this is to either sense what's installed (and use an installer) or just ship it and let the error messages help them figure out what to do.

You can't even guarantee the user has a computer. But it's a very bad idea to throw error messages at the user mid-install, and it hurts to bundle an entire framework installer inside yours. If you can target 4.7 and know it will exist on computers with windows 10, that's much better.

Reply on news.ycombinator.com