Bug 49389 - InitializeComponent does not exist in current context along with other IntelliSense errors from UWP project
Summary: InitializeComponent does not exist in current context along with other Intell...
Status: RESOLVED DUPLICATE of bug 45591
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: Low normal
Target Milestone: 4.3.0 (C9)
Assignee: Bugzilla
Depends on:
Reported: 2016-12-08 21:40 UTC by Ben Beckley
Modified: 2017-02-13 19:11 UTC (History)
9 users (show)

Is this bug a regression?: ---
Last known good build:

logs (5.18 KB, application/x-zip-compressed)
2016-12-08 21:45 UTC, Ben Beckley

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:

Description Ben Beckley 2016-12-08 21:40:26 UTC
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.

Reproduction Steps:
1) Create a Blank App (XAML) with the Shared option selected
2) Observe the InitializeComponent error

env info: https://gist.github.com/BenBeckley/3f951496d1a2149e975b28115fd0ffa8
Comment 1 Ben Beckley 2016-12-08 21:45:35 UTC
Created attachment 18839 [details]
Comment 2 Ben Beckley 2016-12-08 21:50:28 UTC
Would also help to mention that the Xamarin.Forms version is
Comment 3 Parmendra Kumar 2016-12-23 05:38:07 UTC
I have also observed this issue with latest C9 build and XAML blank shared project

Screencast: https://www.screencast.com/t/dsuj6XtUJb

Microsoft Visual Studio Enterprise 2015
Version 14.0.25420.01 Update 3
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Enterprise
Xamarin (46382df)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android (cea7c6e)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS (3282166)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 4 Jose Gallardo 2016-12-26 20:03:52 UTC
The `InitializeComponent` Error was fixed, and should be included in the next build after
In master will be included in the next build after

Comment 6 Jose Gallardo 2016-12-27 15:54:23 UTC
As mentioned in Comment 4, the fix will be included in the next build **AFTER**, hence it's expected that fails as it doesn't include the fix.

Moving the issue back to resolved/fixed.

Please verify with a newer version.

Comment 13 Jose Gallardo 2017-01-12 12:39:25 UTC
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'll investigate.
Comment 14 Danish Akhtar 2017-02-07 10:52:15 UTC
I have checked this issue with latest C9 XVS 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.
Comment 15 Joaquin Jares 2017-02-13 19:11:48 UTC
I'm closing this as duplicate of 45591 based on comment 14

*** This bug has been marked as a duplicate of bug 45591 ***