Bug 10516 - C++ Project/Package references with relative path.
Summary: C++ Project/Package references with relative path.
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C Binding ()
Version: unspecified
Hardware: PC Linux
: Lowest normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-02-21 07:46 UTC by João Vitor
Modified: 2013-08-21 00:31 UTC (History)
2 users (show)

Tags: mono-community
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description João Vitor 2013-02-21 07:46:23 UTC
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.