Bug 51274 - [NuGetizer] Multiplatform library uses PCL Profile 151 instead of Profile 111
Summary: [NuGetizer] Multiplatform library uses PCL Profile 151 instead of Profile 111
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: Normal normal
Target Milestone: 4.3.0 (C9)
Assignee: Adrian Alonso
URL:
Depends on:
Blocks:
 
Reported: 2017-01-06 17:51 UTC by Manish Sinha
Modified: 2017-02-21 21:10 UTC (History)
6 users (show)

Tags: NuGetizer
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 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:
VERIFIED FIXED

Description Manish Sinha 2017-01-06 17:51:48 UTC
Steps to reproduce

1. Create a Multiplatform library, choose PCL
2. Unload the Portable project
3. Open the csproj

Expected: The PCL Profile should be 111 to match with Xamarin's preferred profiles
Actual: The PCL Profile is actually Profile 151

Using XVS 4.3.0.537
Comment 1 Shruti 2017-01-13 05:24:25 UTC
I have checked this issue with Latest Cycle 9 and Master Build of XVS and observed that the issue is fixed in both the lanes.

=======Supplement Info=======
Screencast: https://www.screencast.com/t/vyS9M2KtNFCC

C9 Envt Info: https://gist.github.com/Shruti360/b2c504b41ef46599b5f045023363d0bf

Master Envt Info: https://gist.github.com/anonymous/1f6e5921d0c191c09ca1c965f01fc40d

Hence, changing the bug status to verified fixed.

Thanks!
Comment 2 Parmendra Kumar 2017-02-01 16:37:10 UTC
I have checked this issue with VS 2017 and observed that this issue has been fixed, but this issue still exist with VS 2015.

Hence changing this status to Resolved Fixed and will verify when fixed merge in VS 2015.

EnvironmentInfo: 
Microsoft Visual Studio Enterprise 2017 RC
Version 15.0.26129.0 D15REL
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Enterprise
Xamarin   4.3.0.621 (7bbc66a)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android   7.1.0.30 (3cde9f7)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS   10.4.0.97 (2bcf787)
Visual Studio extension to enable development for Xamarin.iOS.