Bug 40439 - Error CS0103 The name InitializeComponent does not exist in the current context when x:Class does not match type name
Summary: Error CS0103 The name InitializeComponent does not exist in the current conte...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.1.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-04-15 14:57 UTC by John Miller [MSFT]
Modified: 2016-04-20 15:38 UTC (History)
2 users (show)

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

Sample Project (13.93 KB, application/zip)
2016-04-15 14:57 UTC, John Miller [MSFT]

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 John Miller [MSFT] 2016-04-15 14:57:00 UTC
Created attachment 15736 [details]
Sample Project


   When x:Class does not match the type name, a CS0103 error occurs on build.

**Steps to Reproduce:**

   1. Build the attached sample in XS or VS

**Actual Results:**

   /Users/johnmiller/Projects/Case343731/Case343731/MyPage.xaml.cs(13,13): Error CS0103: The name `InitializeComponent' does not exist in the current context (CS0103) (Case343731)

**Expected Results:**

   A more valuable error message explaining what is actually wrong. 

**Build Date & Platform:**

   XF 2.1
Comment 1 Rui Marinho 2016-04-20 15:38:08 UTC
This is not a Xamarin Forms issue, is related with the compiler.