Repository navigation
Move build to csproj/msbuild #3140
Description
This more of a placeholder issue than anything right now. Today, the build uses dotnet-cli and the project.json schema for managing the build. In the future, .NET Core is moving back to MSBuild, which we'll need to use if we want to leverage .NET Standard 2.0 (which we want to do in the 6.0.0 timeframe).
I have no idea what the work entails right now (or if we can get started yet), but I wanted to get it on everyone's radar.
Activity
iSazonov commentedon Feb 14, 2017
I see that .Net team is actively seeking the experience of such migration. Maybe they will be happy to provide direct assistance to us.
http://landinghub.visualstudio.com/migrate-dotnetcore
lzybkr commentedon Feb 14, 2017
The biggest issue is likely on our side - we depend on the
project.jsonfiles to produce the list of assemblies that go into our type catalog for type resolution. We have a proposed temporary solution - to just check in the generated type catalog - but that's not a long term solution because it won't work when we update which assemblies we pull in.We also need to merge #3066 to reduce the effort to migrate.
joeyaiello commentedon Feb 14, 2017
Jason Shirk (@lzybkr) can't we also solve the same problems that #3066 alleviates (namely, a dependency on Win10 SDK) by moving native binary compilation out of this repository? (i.e. since those aren't getting touched quite as much, build them in another repo and pull them in through a Nuget feed?)
lzybkr commentedon Feb 14, 2017
#3066 saves effort in migrating by building less and having simpler build files (one target -
netstandard1.xinstead of two.)Moving native binary compilation should also help (building less!), but it is slightly different.