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 project in Visual Studio
2. Add a reference from the UWP project to the shared project that gets created (this is also an issue, but much more minor - the reference should be there by default)
3. In the Xamarin Forms shared project, MainPage.xaml, change the reference project to UWP (top-left of the code editor window).
# Expected behavior
Intellisense works, and there are no errors.
# Actual behavior
Intellisense does not work, and you get a bunch of blue underlines all over your xaml indicating that each of the controls cannot be found. It works fine for iOS and Android, but not for UWP.
# Test environment (full version information)
VS 2017 15.1 (26403.7) Release. Windows 10 Anniversary edition. Xamarin for Visual Studio 126.96.36.199.
Does Intellisense begin working after the UWP project is built? Because the UWP project uses a project.json file, it doesn't actually reference the Xamarin.Forms assemblies in the solution's local packages directory. They are restored during the first build and until then Intellisense can't resolve the types.
Regarding having to manually reference the shared project, that does sound like an issue with the template so I'm assigning this to the VS team to look into.
No, even after building and running, it still does not work.
The cause of this issue is a duplicate of Bug 57746. We've already talked with the authoring team and it should be fixed in 15.4. Thanks, Adrian
*** This bug has been marked as a duplicate of bug 57746 ***