Bug 12134 - XS or MD doesn't know how to read projects with imported properties
Summary: XS or MD doesn't know how to read projects with imported properties
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 4.0.4
Hardware: PC Mac OS
: Lowest enhancement
Target Milestone: master
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-05-07 10:57 UTC by Dale Ragan
Modified: 2017-09-26 12:14 UTC (History)
2 users (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 Dale Ragan 2013-05-07 10:57:28 UTC
When opening a solution which contains projects that import common properties, XS and MD doesn't import the properties and therefore throws exceptions when trying to view or change the properties in the project options dialog.

To see the issue, clone down the ScriptCS project:


Open the solution in XS or MD. After opening, right click the ScriptCs.Core project and choose Options. When the dialog pops up, Click the General item under the Build section. After clicking an exception is thrown. I looked into why and it's because it's missing the TargetFrameworkVersion in the csproj file. After investigating a little further I noticed they're importing a file at the top called ScriptCs.Common.props. You'll also notice the projects grayed out in the Solution Explorer, because it doesn't think there's a build configuration selected for them even though there is. The build configuration is stored in the same file. Basically this allows you to store common values for options so you have one spot to change them instead of visiting every project. I'm not totally sure of the full experience in VS, but I do know that it's able to read the values without throwing exceptions.

The experience should mirror VS.
Comment 2 Marius Ungureanu 2017-09-26 12:11:52 UTC
From what I know, imported targets/props files are now taken into account. This bug can be marked as fixed.
Comment 3 Marius Ungureanu 2017-09-26 12:14:18 UTC
Just verified this issue, it is definitely not occurring anymore.