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 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.
# Steps to reproduce
1. Create a new Xamarin.Forms blank app. (In this particular case, I created a new "Blank XAML App - Xamarin.Forms Shared".)
2. Change the startup project to UWP.
3. Attempt to deploy to "Local Machine".
# Expected behavior
App deploys successfully, just like if I changed the default project to iOS or Android.
# Actual behavior
Cannot build or deploy, because the Run Configuration is set to neither build NOR deploy.
# Supplemental info (logs, images, videos)
Seems like the solution here is just to update the template to have a correct run configuration that sets it to Build & Deploy. For advanced Xamarin.Forms developers, this is an easy catch, but a small papercut. For new Xamarin.Forms developers, it can be tricky to figure out exactly what's wrong with their app without Googling around.
# Test environment (full version information)
Microsoft Visual Studio Community 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA140
Microsoft Visual Basic 2015
Visual C# 2015 00322-20000-00000-AA140
Microsoft Visual C# 2015
Visual C++ 2015 00322-20000-00000-AA140
Microsoft Visual C++ 2015
Visual F# 2015 00322-20000-00000-AA140
Microsoft Visual F# 2015
Application Insights Tools for Visual Studio Package 7.7.00920.6
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11107.0
ASP.NET and Web Tools 2015.1 (Beta8)
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/
Command Bus, Event Stream and Async Manager Merq
Provides ICommandBus, IEventStream and IAsyncManager MEF services for loosely coupled Visual Studio extension components communication and integration.
Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.4.4
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.25527.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.2060 (c4382f5)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 220.127.116.11 (0e59c36)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.0.0.6 (6c3fee4)
Visual Studio extension to enable development for Xamarin.iOS.
Is there any other information that could be potentially useful for debugging this issue? Want to make sure I capture this on my machine before the state is changed.
Yep, this is quite confusing. I found out that switching to the Android app, then to the UWP app properly switches the active configuration to Debug|AnyCPU and that works, but if you switch to the iOS as a startup app and then back to UWP, VS never switches it back to AnyCPU :(.
Not sure if this is actually our extension doing something wrong, but we should be able to figure out a way to make things work better.
Bumping to 15.3 to prompt a re-triage - this is still a confusing onboarding issue.
The fix was to change the configuration platform to "x86" when the UWP is set as the startup project in a context of a Xamarin solution (this is when the solution contains at least one IOS or Android project).
Created attachment 23558 [details]
Logs during verification
I have tested the app on visual studio 2015 Xamarin version : 18.104.22.1689 (9b1a9b2)
It is fixed and working as expected hence marking this as verified.
Build info : https://gist.github.com/raghorteprasad/c92afa139b28e131c4e16379152f7d2e
Screencast : https://www.screencast.com/t/e7l6QVDMi
Please find attached logs.