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
Developer Community or GitHub 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.
Recently Xamarin.Mac fixed a bug where MSBuild would happily allow you to link in assemblies provided by the system Mono GAC in a XM .NET 4.5 project.
Because of this, we were consuming WindowsBase (via our NuGet dependency, which uses lots of System.IO.Packaging) from the system Mono (but appeared to be provided by XM itself).
With the MSBuild fix in place, Workbooks/Inspector is now broken, because WindowsBase no longer gets linked into our application bundle.
XM should provide WindowsBase (and System.Xaml). There's lots of good stuff there, and it is not UI platform dependent (lame that it's just coincidentally named "Windows"Base). It does not depend on WPF, System.Drawing, SWF, etc.
Providing this would allow XM applications to consume NuGet itself and any .NET 4.5 NuGets which themselves depend on functionality provided by WindowsBase (and there's a lot of it).
In doing some research, it appears that WindowsBase isn't maintained to the highest quality levels and we don't have MS source for it.
I don't really feel comfortable adding it to the "supported" list for XM, so I did this instead:
We could improve that future with something like this in the future: