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 10516 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
After creating a Simple C++ application project, and a C++ Library project,
adding a reference from the application to the library writes an absolute path to the project inside the csproj file, making it impossible to build when moved or distributed.
Editing the csproj manually to use a relative reference causes MonoDevelop to search for the reference inside the MonoDevelop working dir, not the solution directory.
Using $(SolutionDir)/CppLib/... causes MonoDevelop to search for "$(SolutionDir)", instead of replacing the macro, and MonoDevelop fails to show the properties of the reference with an exception.
This behavior occurs on MonoDevelop 2.8 and on master.