3 ms·

When 4.8 is installed, 4.7 is going away. Here .net 5 will not replace .net 4.8, it will exist side by side (if I understand correctly). That's two frameworks t

by cm2187 8y ago

When 4.8 is installed, 4.7 is going away. Here .net 5 will not replace .net 4.8, it will exist side by side (if I understand correctly). That's two frameworks to me.

ticmasta 8y ago
>> When 4.8 is installed, 4.7 is going away. That's not true at all. You can run any version of the framework side-by-side all the way back.
- cheerlessbog 8y ago
  You can only have a single 4.x version on the box. They all install into the same folder.
WorldMaker 8y ago
The VB6 runtime is still installed on Windows 10, but no one (should) considers that a viable Framework to target in 2019. Maybe a better analogy is that .NET Framework 1.x and .NET Framework 2-4.x are side-by-side installed still in Windows 10. If you wanted you could still target .NET 1.0 and it will run in an entirely different runtime (.NET 1.x and 2.x are hugely different). .NET was designed for that sort of side-by-side deployment, they just haven't done it in a while. Yet I've not met a developer that still sees .NET 1.x as a viable Framework recently. Do you want .NET 4.8 applications to just break? What do you expect here? The "current framework" is always a combination of marketing and support and this article seems pretty clear that all marketing and support effort will be on .NET 5, and .NET 4.8 is "done".
dragonwriter 8y ago
Yes, major versions install side-by-side (except v2-v3) because they aren't perfectly backward compatible and this is necessary for legacy app support. So, you can need all of .NET Framework 1.1, 3.5, and 4.8 now, and in the future .NET 5.x is added to the list.
coldtea 8y ago
That's just 2 frameworks installed on a machine. You can have .NET 2 or whatever older on the same machine too. Doesn't change the fact that .NET 5 will be the single official .NET release onwards, where development efforts will be concentrated, etc. It's not like MS will support 2 different frameworks (except one as a legacy release).

by cm2187 8y ago

When 4.8 is installed, 4.7 is going away. Here .net 5 will not replace .net 4.8, it will exist side by side (if I understand correctly). That's two frameworks to me.

ticmasta 8y ago

>> When 4.8 is installed, 4.7 is going away. That's not true at all. You can run any version of the framework side-by-side all the way back.

cheerlessbog 8y ago
You can only have a single 4.x version on the box. They all install into the same folder.

WorldMaker 8y ago

The VB6 runtime is still installed on Windows 10, but no one (should) considers that a viable Framework to target in 2019. Maybe a better analogy is that .NET Framework 1.x and .NET Framework 2-4.x are side-by-side installed still in Windows 10. If you wanted you could still target .NET 1.0 and it will run in an entirely different runtime (.NET 1.x and 2.x are hugely different). .NET was designed for that sort of side-by-side deployment, they just haven't done it in a while. Yet I've not met a developer that still sees .NET 1.x as a viable Framework recently. Do you want .NET 4.8 applications to just break? What do you expect here? The "current framework" is always a combination of marketing and support and this article seems pretty clear that all marketing and support effort will be on .NET 5, and .NET 4.8 is "done".

dragonwriter 8y ago

Yes, major versions install side-by-side (except v2-v3) because they aren't perfectly backward compatible and this is necessary for legacy app support. So, you can need all of .NET Framework 1.1, 3.5, and 4.8 now, and in the future .NET 5.x is added to the list.

coldtea 8y ago

That's just 2 frameworks installed on a machine. You can have .NET 2 or whatever older on the same machine too. Doesn't change the fact that .NET 5 will be the single official .NET release onwards, where development efforts will be concentrated, etc. It's not like MS will support 2 different frameworks (except one as a legacy release).