Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
When attempting to use Windows.ApplicationModel.Package to gather assembly information, various attributes returned are incorrect using Xamarin.Forms UWP
When performing the same calls in a traditional UWP app, the values are returned as expected
UWP Traditional: https://www.dropbox.com/s/oh8j1e2k767n1bw/UWPClassicTest.zip?dl=0
# Steps to Reproduce
1. Download Forms sample above
2. Open in Visual Studio
3. Ensure UWP is set as startup project
4. Observe textblock on main page
5. Download UWP Traditional sample above
6. Open and run in Visual Studio
7. Observe textblock on main page
# Expected Results
Both textblocks should display app name as set in properties
# Actual Results
Forms app displays incorrect value
Microsoft Visual Studio Professional 2015
Version 14.0.25424.00 Update 3
Microsoft .NET Framework
Installed Version: Professional
LightSwitch for Visual Studio 2015 00322-40000-00000-AA256
Microsoft LightSwitch for Visual Studio 2015
Visual Basic 2015 00322-40000-00000-AA256
Microsoft Visual Basic 2015
Visual C# 2015 00322-40000-00000-AA256
Microsoft Visual C# 2015
Visual C++ 2015 00322-40000-00000-AA256
Microsoft Visual C++ 2015
Visual F# 2015 00322-40000-00000-AA256
Microsoft Visual F# 2015
Windows Phone SDK 8.0 - ENU 00322-40000-00000-AA256
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 7.1.00719.1
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2015.1 14.1.20624.0
ASP.NET and Web Tools 2015.1
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.2.40314.0
For additional information, visit http://www.asp.net/
Azure App Service Tools v2.8.1 14.0.11123.0
Azure App Service Tools v2.8.1
Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft .NET Core Tools (Preview 2) 14.1.20624.0
Microsoft .NET Core Tools (Preview 2)
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 14.0.60519.0
Microsoft SQL Server Data Tools
TypeScript tools for Visual Studio
Visual Studio Tools for Universal Windows Apps 14.0.25420.01
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Xamarin 184.108.40.206 (1b3e004)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Inspector Support 0.9.0.14 (4d868da)
Adds support for inspecting Xamarin and WPF apps.
Xamarin.Android 220.127.116.11 (4a7d97a)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 18.104.22.168 (a5ae61c)
Visual Studio extension to enable development for Xamarin.iOS.
I want to further define the issue after some research.
The issue appears to be not that those calls don't work, but rather that the values within the manifest are incorrect, and do not reflect the values defined at project creation.
A project named UWPSettings has a Package Display Name of FPCL.WIndows [sic] and a Display Name of FPCL.WIndows [sic]
This is not a Xamarin.Forms issue, so i will be closing as invalid.
So this has been fixed by the XVS team.
Should be in Cycle 8.