Bug 30379 - Initializecomponent does not exist in the current context
Summary: Initializecomponent does not exist in the current context
Status: RESOLVED DUPLICATE of bug 33181
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-05-23 08:43 UTC by Dharmendar
Modified: 2016-04-08 20:05 UTC (History)
6 users (show)

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

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 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.

Related Links:

Description Dharmendar 2015-05-23 08:43:22 UTC
I have updated my Xamarin Studio and Xamarin.Forms to, now when ever creating Xaml Page in portable 
application , i'm getting build error as "Initializecomponent does not exist in the current context"
Comment 1 Stephane Delcroix 2015-05-26 04:25:06 UTC
This is supposed to work, and work fine in our tests. Could you please send a test project so we can see what's wrong in your case ?
Comment 2 Mike Rowley 2015-09-24 12:38:27 UTC
Appears to be a duplicate of Confirmed Bug  https://bugzilla.xamarin.com/show_bug.cgi?id=33181
Comment 3 Samantha Houts [MSFT] 2016-04-08 20:05:14 UTC
Marking as duplicate.

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