3 ms·

I'm still lost. What should I use and when "to go live"? We are small company with a lot of legacy code that wants to upgrade from 2.0 and 3.5. In 2016. Which .

by mcs_ 10y ago

I'm still lost. What should I use and when "to go live"? We are small company with a lot of legacy code that wants to upgrade from 2.0 and 3.5. In 2016. Which .NET should we use ?

WorldMaker 10y ago
Legacy code would probably stick on the .NET Framework (with maybe Mono as an option to try for some cross-platform reach) for now. New code is great in .NET Core when you have that option. If you are building NuGet libraries (which seems doubtful given 2.0 and 3.5, but possible) you should try to target .NETStandard rather than .NET Framework or the previous best option PCL. But if you can't target .NETStandard for some reason, things will get better (soon).