Is dotnet build being replaced by MSBuild Xplat?
Do we need mono for MSBuild Xplat on OSX/Linux if targeting core?
mikes-gh
All 5 comments
Yes but that's in the xplat branch. The msbuild in visual studio is hosted internally on tfs with a sort of manual copy process to master here and cannot be easily modified. Does this mean aspnetcore RTM. will use msbuild xplat. So visual studio will have 2 different versions of msbuild?
mikes-gh
on 20 May 2016
Not a microsoftie but my impression is that the cli tooling will remain largely the same on the surface, internally though dotnet build will probably call msbuild. I'm pretty sure that msbuild will run on .net core and also be included in the .net core sdk, so it wont really be noticeable. They are also making a bunch of improvements to msbuild and the project system itself, to not list all the files for example.
aL3891
on 20 May 2016
There will likely be more than one version of MSBuild for a while. The "Desktop MSBuild" or Full Framework MSBuild isn't going to run cross-platform and on .NET Core (there's also some information on our Roadmap). We have too many dependencies and legacy components (GAC, registry, ResolveAssemblyReference, TaskHost, etc.) that don't work well in .NET Core. We could eventually light up features at run-time, but it's not a priority right now. A bigger priority would be to build both of those (and the Mono configuration) out of a single branch which as pointed out isn't the case today.
As for Visual Studio, the MSBuild bits used in the internal builds of Visual Studio "15" right now are built from GitHub sources (currently master) and even include the commit id in the version number. You will be able to sync that exact version, modify, build, and use it in Visual Studio without too much trouble (right now I xcopy my build output).
AndyGerlicher
on 21 May 2016
Appreciate the detailed reply.
As for Visual Studio, the MSBuild bits used in the internal builds of Visual Studio "15" right now are built from GitHub sources (currently master)
I hadn't realised you were building from master now. Good progress.
Next step merging the branches 馃憤
mikes-gh
on 21 May 2016
I see a future where NuGet is the new GAC. working with msbuild and the coreclr to maintain the standard library. based on system type.
D
dhusemann
on 22 May 2016
Related issues
ackh
路
3Comments
vatsan-madhavan
路
3Comments
rokups
路
3Comments
ctolkien
路
4Comments
jaredpar
路
4Comments
Most helpful comment
There will likely be more than one version of MSBuild for a while. The "Desktop MSBuild" or Full Framework MSBuild isn't going to run cross-platform and on .NET Core (there's also some information on our Roadmap). We have too many dependencies and legacy components (GAC, registry, ResolveAssemblyReference, TaskHost, etc.) that don't work well in .NET Core. We could eventually light up features at run-time, but it's not a priority right now. A bigger priority would be to build both of those (and the Mono configuration) out of a single branch which as pointed out isn't the case today.
As for Visual Studio, the MSBuild bits used in the internal builds of Visual Studio "15" right now are built from GitHub sources (currently master) and even include the commit id in the version number. You will be able to sync that exact version, modify, build, and use it in Visual Studio without too much trouble (right now I xcopy my build output).