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.
Creating a Blank Shared App (XAML) project will result in multiple IntelliSense errors upon project creation. All but one of these errors stem from the UWP project. The one that does not, is the "InitializeComponent does not exist in the current context". This is not happening with the Blank PCL App (XAML) though.
1) Create a Blank App (XAML) with the Shared option selected
2) Observe the InitializeComponent error
env info: https://gist.github.com/BenBeckley/3f951496d1a2149e975b28115fd0ffa8
Created attachment 18839 [details]
Would also help to mention that the Xamarin.Forms version is 126.96.36.199
I have also observed this issue with latest C9 build and XAML blank shared project
Microsoft Visual Studio Enterprise 2015
Version 14.0.25420.01 Update 3
Microsoft .NET Framework
Installed Version: Enterprise
Xamarin 188.8.131.528 (46382df)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (cea7c6e)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.4.0.49 (3282166)
Visual Studio extension to enable development for Xamarin.iOS.
The `InitializeComponent` Error was fixed, and should be included in the next build after 220.127.116.113.
In master will be included in the next build after 18.104.22.1682.
As mentioned in Comment 4, the fix will be included in the next build **AFTER** 22.214.171.1242, hence it's expected that 126.96.36.1992 fails as it doesn't include the fix.
Moving the issue back to resolved/fixed.
Please verify with a newer version.
This bug is a duplicate of 45591.
For some reason the patch that fixes it on `master` doesn't work with `cycle9`.
My theory is that the template is fixed, but there is some minor difference on the Reference Assemblies installed by C9 compared with master that makes this error to show up.
I have checked this issue with latest C9 XVS 188.8.131.523 and observed that we are still getting this issue. Here is the screencast for the same: https://www.screencast.com/t/IPpkFsDEBT
As per Comment 13 this Bug is duplicate of Bug 45591 and this is also in Reopened state.
>This bug is a duplicate of 45591.
Hence I am Reopening this issue so that issue can be fixed in C9 also.
I'm closing this as duplicate of 45591 based on comment 14
*** This bug has been marked as a duplicate of bug 45591 ***