Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
We have /usr/lib/mono/xbuild/ExtensionsPath and /usr/lib/mono/xbuild/15.0/ExtensionsPath-ToolsVersion but we should only ship the **content** of those folders.
Relevant copying of the folders is here: https://github.com/mono/msbuild/blob/d15.4/install-mono-prefix.sh#L54-L55
@Jo: this seems to be an issue in 5.2 too so not a 5.4 regression (but still important to fix).
After spending time investigating a build failure, I discovered that the problem was with the ExtensionsPath folders, and found this bug already filed.
I wanted to comment here to point out the severity of this problem, in case it's not immediately apparent based on the original bug description alone.
With the extensions not being in the correct location, this completely breaks the ability of mono's MSBuild to be able to compile a net461-net47 project that references a netstandard2.0 assembly.
(In reply to Alexander Köplinger [MSFT] from comment #0)
> We have /usr/lib/mono/xbuild/ExtensionsPath and
> /usr/lib/mono/xbuild/15.0/ExtensionsPath-ToolsVersion but we should only
> ship the **content** of those folders.
> Relevant copying of the folders is here:
> @Jo: this seems to be an issue in 5.2 too so not a 5.4 regression (but still
> important to fix).
To be crystal clear:
/usr/lib/mono/xbuild/15.0/ExtensionsPath-ToolsVersion/Microsoft.Common.targets -> /usr/lib/mono/xbuild/15.0/Microsoft.Common.targets
/usr/lib/mono/xbuild/ExtensionsPath/Microsoft -> /usr/lib/mono/xbuild/Microsoft
@Jo: yes. We need to fix the install script in msbuild to not use "cp -r" as that works differently on Linux than on Mac.
Either use install(1), or `cp foo/*` instead of `cp foo`
Fixed package is currently propagating across all release branches. Will take a couple of hours to do unattended.
Which versions will this be fixed in?
How do those packages relate to the mono packages? Does that mean there will be a new mono release that I can update to and get the fixes?
If you are subscribed to the prealpha, alpha, beta, or stable package repositories, the fixed msbuild package will turn up in there shortly. If you subscribe to a snapshot version, that cannot be fixed.
Thanks, I've updated to the new MSBuild packages and can confirm that everything is working now.