Bug 12735 - PCL project Target Framework options cannot be updated in the options dialog
Summary: PCL project Target Framework options cannot be updated in the options dialog
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: master
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-06-18 10:07 UTC by Atsushi Eno
Modified: 2017-02-15 10:14 UTC (History)
1 user (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 Atsushi Eno 2013-06-18 10:07:16 UTC
examined on Windows master - in MonoDevelop, portable library project has options: general - Target Framework, where we can select target platforms by checkboxes. They however does not work.

Repro steps:

- create a PCL project (C#).
- open the project option and go to general page. Check general tabpage.
- Make some changes on the checkboxes for Target Frameworks.
- Click OK, and go back to see the checkboxes again.

Actual results:
- The checkbox changes aren't reflected.
Comment 1 Matt Ward 2017-02-15 10:14:17 UTC
This looks OK with Xamarin Studio v6. So it looks like it was fixed at some point.