Bug 1817 - MonoDevelop break VS2010 compatibility in solution file
Summary: MonoDevelop break VS2010 compatibility in solution file
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Visual Studio Compatibility ()
Version: 2.6
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-01 19:43 UTC by bj.cardon
Modified: 2012-01-23 15:04 UTC (History)
1 user (show)

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 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.

Related Links:

Description bj.cardon 2011-11-01 19:43:24 UTC
I have recently been using MonoDevelop 2.6 alongside Visual Studio 2010 and noticed a somewhat annoying issue. Inside the solution file, VS2010 commonly adds the following line:

<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" />

For one reason or another, when MonoDevelop opens the same solution it adds the following line in addition to the previous line:

<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets" />

Afterwards, VS2010 cannot open the solution because the latter path does not exist on the machine with only VS2010 installed thereby breaking the solution file for VS2010 and requiring manual modification each time it is opened.
Comment 1 Jeffrey Stedfast 2012-01-23 15:04:39 UTC
Fixed in git master (will be 2.8.7)