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 for Bug 1690 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 768 [details]
Monodevelop error message
A project developped in VS2010 on Windows loads correctly when it contains the following
<Reference Include="System, Version=$(VersionToUseInSharedLibs)">
The same project does not load in Monodevelop for Mac because of the Version part of the Inclulde. See attachement.
Removing it allows the project to load
Is there a way to handle the Version statement in Monodevelop ?
Additionnaly, the csproj files contain the following higher up
<VersionToUseInSharedLibs Condition=" '$(Platform)' == 'Android' ">220.127.116.11</VersionToUseInSharedLibs>
<VersionToUseInSharedLibs Condition=" '$(Platform)' != 'Android' ">18.104.22.168</VersionToUseInSharedLibs>
We currently don't have support for evaluating msbuild conditionals (or any other msbuild constructs) within monodevelop itself. As such, there's no simple way to do what you want without breaking features such as code completion. There's no ETA on when we expect to have support for this, but we'll update the bug when we know more.
MD supports most MSBuild projects by mapping them into its old internal build engine, which can't support arbitrary MSBuild constructs like this, However, it uses xbuild/MSBuild as the build engine for Android projects so those project can handle more advanced MSBuild features. There's experimental support to use MSBuild/xbuild as the build engine for other project types, and you can enable this in MD Preferences. When using xbuild, code completion should work correctly as it uses the assemblies resolved by xbuild.
That said, even though xbuild support would be able to build the project and provide correct code completion for this construct, it currently won't work for this particular case because MD can't load it, because the solution pad is trying to parse the reference ItemSpecs.
So if you have 1/2 the solution built (at least experimentally), would you be able to upadate the MD pad to handle this in an upcoming release ?
We don't have any immediate plans to do so, since it's nontrivial and there are other more commonly used xbuild features that need to be completed first. As a workaround, you could try duplicating the reference and using condition attributes directly on it.