3 ms·
It's not really clear to me what the difference between .NET Core 3 and a '.NET Framework 5' would be. For users, having to install .NET Core 3 runtime (if the
by gregmac 8y ago
It's not really clear to me what the difference between .NET Core 3 and a '.NET Framework 5' would be.
For users, having to install .NET Core 3 runtime (if the app doesn't ship it internally) doesn't seem like a different thing than having to install .NET Framework 4.x when it first came out.
It wouldn't be surprising if future versions of Windows started shipping with .NET Core pre-installed.
Why is .NET Core so different from this perspective?
- sebazzz 8y agoThe full framework is part of Windows, and contains shared components such as COM activation, and is also part of IIS when applicable etc.
- WorldMaker 8y ago> It wouldn't be surprising if future versions of Windows started shipping with .NET Core pre-installed. The UWP .NET stack seems close enough to .NET Core (esp. when using .NET Native) to posit that this is already the case. (Though there are still subtle differences between UWP .NET and .NET Core, they seem very close to converging.)
- piaste 8y agoThe .NET Core runtime (for a specific platform) can be bundled with the application so the user doesn't need to install it, and every application can ship with the exact version it prefers. This wasn't possible with the .NET Framework, it needed a global install and, from 4.0, it upgraded in-place only.
- cm2187 8y agoExactly, to ensure critical vulnerabilities do not get patched in your app when one patches the machine! One would have thought Microsoft would have learned from the experience of java...
- sebazzz 8y agoIn .NET Core you have the option. You can do a standalone deploy or depend on the system wide installed version of .NET Core. In the latter case it is an sysadmin issue.