"Name does not exist" error when switching target platform from AnyCPU to x86

I am creating a WPF project for VS2013 community. I wanted to use CefSharp

in a project, but it can't work in AnyCPU

build config , so I changed it to x86

. After that MainWindow.xaml.cs started throwing The name 'InitializeComponent' does not exist in the current context

and 25 more errors stating that none of my XAML control names were found. When I go to x64

, it's the same. When I return to AnyCPU

, the project compiles and works fine.

So what else do I need to change in the config to make it work?

EDIT: I finally decided to ditch CefSharp and returned the AnyCPU option all over the place. Now VS is giving me the same errors only when building for Release. I have reverted to the latest stable version of the project in Git, but the errors persist. I looked at the Debug / Release settings in Configuration manager

and Project properties

, but everything seems fine. Is there somewhere else to look for Release settings?

+3
c # visual-studio-2013 wpf target-platform


source to share


No one has answered this question yet

See similar questions:

2
Can't find XAML element names in code behind Release

or similar:

1252
Try to speed up my code?
352
The name "InitializeComponent" does not exist in the current context
108
Name does not exist in namespace error in XAML
37
name <...> does not exist in the clr-namespace <...>
23
WPF: name does not exist in namespace
7
Why is the default platform framework for WPF apps in Visual Studio x86 and not AnyCPU?
1
Target framework VS2005 .NET 2.0 and C # and x86
0
"Specified Solution Configuration" Debug | AnyCPU is "invalid" when building a solution with Microsoft.Build
0
CefSharp WPF for x64 platform cannot be referenced in another wpf project
0
InitializeComponent does not exist in the current context when creating an x86 WPF app



All Articles
Loading...
X
Show
Funny
Dev
Pics