Bug 145 - Project '{0}' has different ToolsVersion than the containing solution.
Summary: Project '{0}' has different ToolsVersion than the containing solution.
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-08-02 07:43 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2012-01-05 13:40 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Rolf Bjarne Kvinge [MSFT] 2011-08-02 07:43:38 UTC
This error pops up if I open monotouch/monotouch.sln

This is recent (between yesterday and today I think).
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-02 08:02:07 UTC
It's a valid warning, in these cases VS would prompt you to upgrade the entire solution. In MD, it should be fixed automatically when you save the project.
Comment 2 Mikayla Hutchinson [MSFT] 2011-08-02 08:02:50 UTC
That said, looks like we're missing a format value in the message?
Comment 3 Alan McGovern 2011-09-23 09:44:55 UTC
*** Bug 571 has been marked as a duplicate of this bug. ***
Comment 4 Jeffrey Stedfast 2012-01-05 13:40:53 UTC
Looks like this has been fixed.