4 ms·

>.NET 5 is a merger of everything into a single framework again Is it a merger or a replacement? I won't be able to just take my huge legacy .NET 4.7.2 app an

>.NET 5 is a merger of everything into a single framework again Is it a merger or a replacement? I won't be able to just take my huge legacy .NET 4.7.2 app and just change the runtime to .NET 5 and hit the go button right? Seems for the app I work on at least the upgrade path is a full rewrite :/

manigandham 6y ago
It's technically a merger. It's the next version of .NET Core after v3.0 but jumping ahead to v5.0 and dropping the "Core" designation, and then merging in parts of Mono, AOT toolchain, and even more of the (upgrade) bits of the classic framework. You might be able to get pretty far with just a framework switch. The RC is already out so try it. You'll probably have to update the csproj/sln files at a minimum and fix some known API differences but it's unlikely you need an entire rewrite.
- nullsense 6y ago
  >but it's unlikely you need an entire rewrite. My EF 5, EDMX, ancient dependencies and the like probably beg to differ.