We've got a solution with 20 .NET Framework 4.5 .DLLs (say helloworld01.dll to helloworld20.dll) where we want to add Linux support (to each) in the near future. We think this means each of those needs to be recompiled as .NET Core 1.0 targets.Leaving source code porting aside and only looking at the organization/structure, what's the recommended practice to develop, build and release .NET Core 1.0 flavors alongside the .NET Framework DLLs? Entirely new .sln file + parallel folder structure for code? New project file each + parallel folder structure for code? New project file each + references into existing folder structure? Same project file + same folder structure + some msbuild based black magic? (I suspect not given the xml vs json proj files)some other wizardry?Bonus: Can you point to the open-source project that embodies such best practices?
Build and project patterns when targeting .NET Core and .NET Framework flavors?
c#;.net;visual studio;cross platform;.net core