Bug 1557 - Plist editor should not show up in the project options anymore
Summary: Plist editor should not show up in the project options anymore
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
Depends on:
Reported: 2011-10-19 05:43 UTC by Alan McGovern
Modified: 2011-11-15 14:09 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 Alan McGovern 2011-10-19 05:43:19 UTC
Plist settings are no longer stored in the csproj file so we should not show the editor in the project options. This implies that the settings there are stored in the csproj instead of the Info.plist file which is not true.
Comment 1 Alan McGovern 2011-10-19 05:43:45 UTC
Michael, if this change makes sense to you I can trivially do it.
Comment 2 Mikayla Hutchinson [MSFT] 2011-10-19 15:19:14 UTC
Your point is a valid one - we did initially do it that way. However, users expected to find the settings in Project Options, so we made it available there too. It's not ideal, but I think the compromise made sense in this case.
Comment 3 Alan McGovern 2011-11-15 14:09:33 UTC
Sounds good!