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 3063 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
The Export Solution command does not support solutions that reference projects outside the solution directory.
It's not clear how such items should be handled. Using the same relative path would be very strange for exports into new locations, since it could be ~anywhere relative to the original. Copying it into the solution directory would also be odd because it would break in-place exports and could collide with existing items, and might be unexpected. Converting the format for in-place exports would also be strange because the project is probably used in other solutions.
One way to support this would be to offer the user a choice (reference original project and convert, reference original project and do not convert, copy to solution directory, copy with same relative path). A sipler solution would be to simply omit affected projects and project references from the export, and change this from an error to a warning.