blocks|key|3161368|text|这有一个非常具体的原因，它在项目设置中。当您尝试将.NET控件/窗口添加到WPF2.0类库或项目时，通常会发生这种情况。出现此错误的原因是该项目不知道它正在生成C#控件或窗口，因此尝试将其作为WPF+2.0项目生成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161369|该解决方案涉及编辑.csproj文件。右键单击导致问题的项目，然后选择“卸载项目”。右键单击卸载的工程，选择“编辑.csproj”。.csproj文件将打开，您可以看到该文件。查找以下行：|3161370|<Import+Project=…..|code-block|syntax|javascript|3161371|它接近文件的末尾，您唯一拥有的行可能是|3161372|<Import+Project="$(MSBuildBinPath)\Microsoft.CSharp.targets"+/>|3161373|这将告诉Visual+Studio将项目构建为.NET+2.0项目。我们想要做的是告诉Visual+Studio这实际上是一个WPF项目，所以我们必须添加以下行：|3161374|<Import+Project="$(MSBuildBinPath)\Microsoft.WinFX.targets"+/>|3161375|此行将告诉Visual+Studio将项目构建为WPF项目。现在，您的.csproj文件底部应该如下所示：|3161376|<Import+Project="$(MSBuildBinPath)\Microsoft.CSharp.targets"+/>
<Import+Project="$(MSBuildBinPath)\Microsoft.WinFX.targets"+/>|3161377|保存.csproj文件，在解决方案资源管理器中右键单击它，然后选择“重新加载项目”编译，就这样，一切都完成了！|3161378|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

There's a very specific reason for this, and it's in the project settings. This usually happens whenever you try to add a WPF control/window to a .NET 2.0 class library or project. The reason for this error is that the project does not know it's building a WPF control or window and therefore tries to build it as a C# 2.0 project. 

The solution involves editing the .csproj file. Right click on the project causing the problem and select “Unload Project”. Right click the unloaded project and select “Edit .csproj”. The .csproj file will open and you can see the XML. look for the following line:

<pre><code>&lt;Import Project=…..
</code></pre>

It's near the end of the file, and the only line that you have is probably 

<pre><code>&lt;Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /&gt;
</code></pre>

This tells Visual Studio to build the project as a .NET 2.0 project. What we want to do is to tell Visual Studio that this is actually a WPF project, so we have to add the following line: 

<pre><code>&lt;Import Project="$(MSBuildBinPath)\Microsoft.WinFX.targets" /&gt;
</code></pre>

This line will tell Visual Studio to build the project as a WPF project. Now your .csproj file bottom should look like this: 

<pre><code>&lt;Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /&gt;
&lt;Import Project="$(MSBuildBinPath)\Microsoft.WinFX.targets" /&gt;
</code></pre>

Save the .csproj file, right click it in Solution Explorer and select “Reload Project” compile and that's it, you're all done!

blocks|key|259117|text|我已经遇到过这种情况好几次了，总是忘记是什么导致了这种情况。当我在代码隐藏文件中重命名名称空间，而不是在XAML中重命名时，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|259118|所以，检查一下你是否做过同样的事情。|259119|命名空间和类名称需要匹配，因为它们都是分部类的一部分|offset|length|style|BOLD|259120|namespace+ZZZ
{
++++///+<summary>
++++///+Interaction+logic+for+MainWindow.xaml
++++///+</summary>
++++public+partial+class+MainWindow
++++{
+++++++++//...
++++}
}


<Window+x:Class="ZZZ.MainWindow">|code-block|syntax|javascript|259121|entityMap^0|0|0|0|4|5|1|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@$F|T|G|U|H|I]|$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|X|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

I've encountered this a couple times and keep forgetting what causes it.
I ran into this when I renamed the namespace on my code behind file but not in my XAML.

So check if you've done the same. 

The namespace and class names need to match since they are both part of a partial class

<pre><code>namespace ZZZ
{
 /// &lt;summary&gt;
 /// Interaction logic for MainWindow.xaml
 /// &lt;/summary&gt;
 public partial class MainWindow
 {
 //...
 }
}

&lt;!-- XAML --&gt;
&lt;Window x:Class="ZZZ.MainWindow"&gt;
</code></pre>

blocks|key|3161468|text|.xaml文件的构建操作也必须设置为“页面”，当在项目之间移动xaml文件时，此设置会丢失(至少在VS2010中)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161469|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The Build Action for the .xaml file must also be set to "Page", when moving a xaml file between projects this setting gets lost (in VS 2010 at least).

blocks|key|3161474|text|这发生在我身上，因为Nuget包卸载程序清除了App.xaml中元素的所有属性。这包括x:Class属性，它指定应用程序类名。因此，永远不会生成包含InitializeComponent()方法的分部类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161475|我修复了这个问题，方法是将App.xaml恢复为受源代码控制的副本。|3161476|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This happened to me because a Nuget package uninstaller blew away all the attributes on the &lt;Application&gt; element in App.xaml. This included the x:Class attribute, which specifies the application class name. So the partial class containing the InitializeComponent() method was never generated.

I fixed the problem by reverting App.xaml to the source-controlled copy.

blocks|key|256926|text|我在重命名用户控件时遇到了这个问题。我修复它的方法是注释掉InitializeComponent，验证所有的名称都是正确的(xaml和后面的代码)，构建项目，取消注释InitializeComponent，然后再次构建。听起来这个问题可能有几个原因/解决方案，但这种方式对我来说是可行的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|256927|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I encountered this while renaming a usercontrol. The way I fixed it was to comment out InitializeComponent, verify that all the names were correct (xaml and code behind), build the project, uncomment InitializeComponent, then build again. It sounds like there may be a couple causes/solutions for this issue, but this way did it for me.

blocks|key|256942|text|这为我解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|256943|我注释掉了App.xaml文件中的资源|256944|<Application+x:Class="MyApp.App"+xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
++++xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
++<Application.Resources>
++++
++</Application.Resources>
</Application>|code-block|syntax|javascript|256945|重新添加注释以修复构建错误。|256946|<Application+x:Class="MyApp.App"+xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
++++xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
++<Application.Resources>
++++<ResourceDictionary>
++++++<ResourceDictionary.MergedDictionaries>
++++++++<ResourceDictionary
++++++++++++Source="/PresentationFramework.Aero,+Version=3.0.0.0,+Culture=neutral,+PublicKeyToken=31bf3856ad364e35,+ProcessorArchitecture=MSIL;component/themes/aero.normalcolor.xaml"+/>
++++++</ResourceDictionary.MergedDictionaries>
++++</ResourceDictionary>
++</Application.Resources>
</Application>|256947|再深入一点，我发现{Project}\obj\debug中的app.g.cs文件在我对资源进行注释时只包含以下内容。|256948|///+<summary>
///+InitializeComponent
///+</summary>
[System.Diagnostics.DebuggerNonUserCodeAttribute()]
public+void+InitializeComponent()+{
++++if+(_contentLoaded)+{
++++++++return;
++++}
++++_contentLoaded+=+true;
++++System.Uri+resourceLocater+=+new+System.Uri("/MyApp;component/app.xaml",+System.UriKind.Relative);

++++#line+1+"..\..\..\App.xaml"
++++System.Windows.Application.LoadComponent(this,+resourceLocater);

++++#line+default
++++#line+hidden
}|256949|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

This solved it for me. 

I had commented out the resources in the App.xaml file

<pre><code>&lt;Application x:Class="MyApp.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"&gt;
 &lt;Application.Resources&gt;
 &lt;!--&lt;ResourceDictionary&gt;
 &lt;ResourceDictionary.MergedDictionaries&gt;
 &lt;ResourceDictionary
 Source="/PresentationFramework.Aero, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=MSIL;component/themes/aero.normalcolor.xaml" /&gt;
 &lt;/ResourceDictionary.MergedDictionaries&gt;
 &lt;/ResourceDictionary&gt;--&gt;
 &lt;/Application.Resources&gt;
&lt;/Application&gt;
</code></pre>

Commenting thiis back in to fixed the build error. 

<pre><code>&lt;Application x:Class="MyApp.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"&gt;
 &lt;Application.Resources&gt;
 &lt;ResourceDictionary&gt;
 &lt;ResourceDictionary.MergedDictionaries&gt;
 &lt;ResourceDictionary
 Source="/PresentationFramework.Aero, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=MSIL;component/themes/aero.normalcolor.xaml" /&gt;
 &lt;/ResourceDictionary.MergedDictionaries&gt;
 &lt;/ResourceDictionary&gt;
 &lt;/Application.Resources&gt;
&lt;/Application&gt;
</code></pre>

Digging a bit deeper I found that the app.g.cs file in {Project}\obj\debug only contained the following when I left the resource commented in.

<pre><code>/// &lt;summary&gt;
/// InitializeComponent
/// &lt;/summary&gt;
[System.Diagnostics.DebuggerNonUserCodeAttribute()]
public void InitializeComponent() {
 if (_contentLoaded) {
 return;
 }
 _contentLoaded = true;
 System.Uri resourceLocater = new System.Uri("/MyApp;component/app.xaml", System.UriKind.Relative);

 #line 1 "..\..\..\App.xaml"
 System.Windows.Application.LoadComponent(this, resourceLocater);

 #line default
 #line hidden
}
</code></pre>

blocks|key|260980|text|导航到解决方案directory|type|unstyled|depth|inlineStyleRanges|entityRanges|data|260981|Delete++\obj+folder|unordered-list-item|260982|Rebuild+|ordered-list-item|260983|+solution|260984|260985|260986|我在重构过程中遇到了这个错误，我重命名了一些文件/文件夹，需要重新生成前缀的*.g.cs文件。|260987|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|S|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

<ol>
<li>Navigate to the solution directory</li>
<li>Delete the \obj folder</li>
<li>Rebuild the solution</li>
</ol>

I encountered this error during refactoring where I renamed some files/folders and the prexisiting *.g.cs files needed to be re-generated.

blocks|key|260989|text|是啊，很多东西都可以...我会加上这一条。确保App.xaml指向您的命名空间(应用程序文件所在的位置)%2B+.App，例如。x:Class="DX.App“<===确保这是应用程序，而不是主页名称|type|unstyled|depth|inlineStyleRanges|entityRanges|data|260990|希望这对你也有效。|260991|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

yeap, so many things can be... I would add this one...
make sure the App.xaml points to your Namespace (where your app file is) + .App
eg.
x:Class="DX.App" &lt;=== make sure this is App and not the Main Page name

Hope this works for you too.

blocks|key|262320|text|我也有同样的问题，但在我的情况下，这些都没有帮助。在我的情况下，我的每个WPF项目(包括新创建的项目)都会因为这个错误而停止编译。最终，我卸载了所有的.Net框架，然后重新安装它们，一切又开始工作了。我还重新安装了Visual+Studio，但结果没有任何影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|262321|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem, but in my case none of this helped. In my situation every WPF project I had (including newly made projects) stopped compiling with this error. Eventually I uninstalled all the .Net frameworks then reinstalled them and things started working again. I also did a reinstall of Visual Studio, but it turned out that had no affect.

blocks|key|2947736|text|导致此错误的另一个常见原因是，如果您在下面的代码中执行了某些操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947737|2947738|右键单击项目中的文件夹以创建新的UserControl。这将创建一个类和从文件夹的命名空间中的用户控件派生的xaml文件。|ordered-list-item|2947739|然后您决定更改该类的命名空间，因为您实际上只是使用文件夹来组织代码。class属性不会自动更新，因此它将搜索不存在的类。我可以使用更好的错误消息，如“x:类类型无法在命名空间bla.blaa.blaaa."|2947740|中找到”|2947741|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Another common cause of this error is if you did something in this:

<ol>
<li>Right click on folder in project to create new UserControl. This creates a class and xaml file that derives from user control in the namespace of the folder.</li>
<li>Then you decide to change the namespace of the class because you're really just using folders for organization of code. The x:Class attribute will not get automatically updated so it will be searching for a class that doesn't exist. Could probably use a better error message like "x:Class type could not be found in namesace bla.blaa.blaaa."</li>
</ol>

blocks|key|256963|text|我遇到过这种情况(尽管这在很大程度上是我的错，而且是在我复制并粘贴了一些代码之后引起的)；当XAML和代码隐藏之间的名称空间不匹配时，就会出现这种情况|type|unstyled|depth|inlineStyleRanges|entityRanges|data|256964|例如|256965|<UserControl+x:Class="DockPanel.TreeView"+/>|code-block|syntax|javascript|256966|后面的代码是|256967|namespace+NotDockPanel|256968|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I've had this (although it was very much my fault and was caused after I copied and pasted some code in); it can occur when the namespace doesn't match between the XAML and code behind

EG

<pre><code>&lt;UserControl x:Class="DockPanel.TreeView" /&gt;
</code></pre>

and the code behind is 

<pre><code>namespace NotDockPanel
</code></pre>

blocks|key|2947764|text|我也遇到了同样的问题，只是我将我的MainWindow、xaml和cs复制到一个新文件中，然后将它们复制回原来的位置。然后，在尝试编译WPF应用程序后，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947765|我修复此错误的方法是重命名名称空间(来自egNamespace+->+egNamespaceNew+)，并且它再次工作。然后，我将名称空间改回原来的名称空间。|2947766|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem, expect I coped my MainWindow xaml and cs into a new file and then copied them back to their original place. I then got this error after trying to compile the WPF app.

What I did to fix this error was rename the namespace (from egNamespace -> egNamespaceNew, and it worked again. I then changed the namespace back to the original one.

blocks|key|2947787|text|当我不小心从xaml定义中删除了类引用时，就发生了这种情况：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947788|我已经替换了|2947789|<Window+x:Class="myapp.MainWindow"
++++xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
++++xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">|code-block|syntax|javascript|2947790|下面是第一行：|2947791|<RibbonWindow+
++++xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
++++xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">|2947792|我知道这不是原始问题的答案(因为这是建立在另一台机器上的项目)，但错误消息是相同的，所以也许我可以帮助解决这种情况的人。|2947793|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

this happened with me when I accidentaly deleted the class reference from the xaml definition:

I've replaced the 

<pre><code>&lt;Window x:Class="myapp.MainWindow"
 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"&gt;
</code></pre>

first line with this:

<pre><code>&lt;RibbonWindow 
 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"&gt;
</code></pre>

I know this isn't the answer to the original question (because thats project builds on another machine), but the error message was the same, so maybe I'll help someone with this situation.

blocks|key|259281|text|我遇到了同样的问题，我不得不将我的共享项目转换为可移植的类库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|259282|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue, I had to convert my shared project into a portable class library.

blocks|key|2947856|text|右击项目中的文件夹来创建新的UserControl，这对我来说是个问题。我在文件夹外创建了相同的控件，仅此而已。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947857|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Right click on folder in project to create new UserControl that was the problem for me.
I created the same control out side the folder and that was it.

blocks|key|3161761|text|所以我意识到这是一个古老的问题，但我们也遇到了类似的问题。我们可以使用VS2012构建项目，但不能从命令行使用msbuild。我进入.proj文件，注意到在默认的"ProjectTypeGuids“部分下没有"PropertyGroup”的记录，所以我添加了以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161762|<ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>|code-block|syntax|javascript|3161763|这是WPF的项目GUID。然后我删除并重新添加了UserControl，它就开始工作了。我不确定我是否必须做最后一步，但现在它对我来说是有效的。|3161764|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

So I realize this is an older question, but we were having a similar issue. We were able to build a project using VS2012, but not using msbuild from the command line. I went into the .proj file and noticed it didn't have a record for "ProjectTypeGuids" under the default "PropertyGroup" section, so I added this:

<pre><code>&lt;ProjectTypeGuids&gt;{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}&lt;/ProjectTypeGuids&gt;
</code></pre>

which is the project GUID for WPF. I then deleted and re-added the UserControl and it started working. I'm not sure if I had to do that last step, but it works for me now.

blocks|key|262437|text|我刚刚遇到了这个问题，结果是我的项目存储在我的用户文件夹中，该文件夹存储在网络上，我们遇到了短暂的网络中断。我做了一个构建；它抱怨我的文件在编辑器之外被修改过(他们没有；文件锁刚刚被锁定)，它构建得很好，消除了有关InitializeComponent()方法的错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|262438|顺便说一句，如果你想知道，从网络驱动器开发一些东西是不好的做法。当您试图利用.NET的托管代码时，它会变得特别有问题；根据我的经验，每次构建时它都会崩溃。我忘了把这个丢弃的小项目放到合适的文件夹里，最终为此付出了代价。|262439|entityMap^0|2Z|L|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I just encountered this problem, and it turned out to be that my project is stored in my user folder, which is stored on the network, and we had a momentary network outage. I did a build; it complained that my files had been modified outside the editor (they hadn't; the file locks just got borked), and it built fine, removing the error regarding the <code>InitializeComponent()</code> method.

BTW, in case you're wondering, developing something from a network drive is bad practice. It becomes particularly problematic when you're trying to leverage .NET's managed code; in my experience, it freaks out every time you build. I forgot to put this little throw-away project in the proper folder, and ended up paying the price.

blocks|key|2947926|text|对于那些在网上找到这篇文章的人。如果有编译，请检查Windows.csproj文件。应该有2个条目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2947927|<Page+Include="YourFile.xaml">
++<SubType>Designer</SubType>
++<Generator>MSBuild:Compile</Generator>
</Page>

<Compile+Include="YourFile.xaml.cs">
++<DependentUpon>YourFile.xaml</DependentUpon>
</Compile>|code-block|syntax|javascript|2947928|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For those who find this on the internet. Check the Windows.csproj file if the compilation is there. There should be 2 entries

<pre><code>&lt;Page Include="YourFile.xaml"&gt;
 &lt;SubType&gt;Designer&lt;/SubType&gt;
 &lt;Generator&gt;MSBuild:Compile&lt;/Generator&gt;
&lt;/Page&gt;

&lt;Compile Include="YourFile.xaml.cs"&gt;
 &lt;DependentUpon&gt;YourFile.xaml&lt;/DependentUpon&gt;
&lt;/Compile&gt;
</code></pre>

blocks|key|257044|text|如果名称空间是正确的，则也存在相同的错误，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257045|只需关闭您的应用程序并再次打开它，。|offset|length|style|BOLD|257046|这可能会解决你的问题|257047|entityMap^0|0|0|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

If the Namespaces are correct then also there is a same error, 

Just close your application and open it again.

This may solve your problem

blocks|key|257049|text|另一种可能的解释是，您是在针对x86进行构建。右击您的解决方案并选择“配置管理器”。看看你是不是在构建x86，而不是任何CPU。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257050|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another possible explanation is that you're building against x86. Right-click your Solution and choose Configuration Manager. See if you're building against x86 instead of Any CPU.

blocks|key|3161808|text|对于那些在Debug模式下没有错误，但在Release模式下确实有指定错误(但项目运行正常)的人，这里有一些简单的尝试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161809|3161810|打开与违规xaml.cs文件对应的XAML文件。|ordered-list-item|3161811|进行编辑--任何编辑，如在某个地方添加空间|3161812|保存文件并将其关闭|3161813|3161814|这个方法在VS+2015中适用于我，据其他用户说，2017和2019年也是如此|3161815|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|S|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

For those who have no errors in Debug mode, but do have the specified error in Release mode (and yet the project runs fine), here is something simple to try:

<ol>
<li>Open the XAML file corresponding to the offending xaml.cs file. </li>
<li>Make an edit--any edit, like add a space somewhere</li>
<li>Save the file and close it</li>
</ol>

This method worked for me in VS 2015, and according to other users, also 2017 and 2019

blocks|key|262484|text|经过一些操作后，.cs文件的名称空间可能与.xaml文件中的名称空间不同(在xaml中查找x:Class="namespace.yourType")。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|262485|将它们修复为相同的。|262486|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

After some action the namespace of the .cs file and the one in .xaml file may be different (in xaml look for the x:Class="namespace.yourType").

Fix them to be the same.

blocks|key|259367|text|由于某些原因，在项目之间复制.xaml和它的.cs之后，构建操作有时会发生变化。请确保您的.xaml的构建操作是页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|259368|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Because of some reason after copying .xaml and it's .cs between projects the build action is sometimes changing. Please make sure build action of your .xaml is Page.

blocks|key|3161917|text|在我的例子中，我的项目中有一个引用，这是错误的，但没有报告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161918|我解决了阅读所有参考资料的问题，即使它们是正确的。|3161919|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case there's been a reference inside my project which was wrong but that wasn't reported.

I solved my problem with readding all my references even if they were meant as correct.

blocks|key|262528|text|我发现"Startup+object“是(没有设置)导致这个错误的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|262529|"Startup+object"+(Not+set)|offset|length|262530|entityMap|0|LINK|mutability|MUTABLE|url|http://i.stack.imgur.com/Ncba9.png^0|0|0|Q|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I have discovered that the "Startup object" was (Not set) causing this error for me.

<a href="http://i.stack.imgur.com/Ncba9.png" rel="nofollow">"Startup object" (Not set)</a>

blocks|key|3161960|text|我同意上面的答案，即名称空间必须匹配。但是，在名称空间匹配时，我遇到了类似这样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161961|为了解决这个问题，我简单地将XAML中的名称空间更改为不正确的名称空间，保存后再将其更改回正确的名称空间。瞧！|3161962|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I agree with the answer above that the namespaces have to match. However, I had a problem like this where the namespaces matched.

To fix, I simply changed the namespace in the XAML to an INCORRECT one, saved, then changed it back to the CORRECT one. Voila!

blocks|key|3161993|text|当我创建一个"WPF应用程序项目“，然后将它的构建目标更改为”类库“，以供另一个程序用作外部工具时，就会发生这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161994|我更改了窗口的所有.xaml文件，以便将它们的构建操作设置为“页面”。我没有意识到的是，这个项目还包含"App.xaml“和"App.xaml.cs”。|3161995|"App.xaml“也需要设置为"Page”，或者完全删除(与“App.xaml.cs”一起删除)。我做了前者，然后是后者，因为我意识到这些文件是无用的。|3161996|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This issue happened for me when creating a "WPF Application Project" then changing its build target to "Class Library" to be used as an external tool by another program.

I changed all my .xaml files for my windows so their build action were set to "Page". What I did not realize was that that the project also contained "App.xaml" and "App.xaml.cs". 

"App.xaml" needs to be set to "Page" as well, or deleted altogether (along with "App.xaml.cs"). I did the former, then the latter as I realized the files were useless.

blocks|key|261301|text|当您从另一个项目导入类，或者更改xaml文件的路径，或者更改xaml文件或.cs文件后面的命名空间时，可能会出现此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|261302|One:它的名称空间可能与您的新项目中的名称空间不同|offset|length|style|BOLD|261303|namespace+TrainerB.MVC.Forms
{
+++++public+partial+class+AboutDeveloper+:+ContentPage
+++++{
++++++++++public+AboutDeveloper()
++++++++++{
+++++++++++++++InitializeComponent();
++++++++++}
+++++}
}|code-block|syntax|javascript|261304|正如您所看到的，导入文件中的名称空间以旧项目名称"TrainerB"开头，但新项目可能具有不同的名称，因此只需在.xaml文件和后面的.cs文件中将其更改为正确的新项目名称即可。|261305|2：|261306|将.xaml文件的属性更改为：|261307|生成操作：嵌入式资源|261308|自定义工具：+MSBuild:UpdateDesignTimeXaml|261309|​|261310|📷|atomic|261311|261312|261313|261314|261315|261316|261317|261318|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/531b61561921198a296dfb817cff4026.jpeg|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/3d04f1357a55e1e2fa4aac5f86101cf9.jpeg|2|https://ask.qcloudimg.com/http-save/yehe-900000/5bf14fee1d46c07d57253d9a3bdde6cc.jpeg^0|0|0|4|0|0|O|A|0|0|2|0|0|0|5|0|0|6|0|0|0|1|0|0|0|0|0|1|1|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1P|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1X|8|@$D|1Y|E|1Z|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|20|8|@$D|21|E|22|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|23|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|24|8|@]|9|@$D|25|E|26|1|27]]|A|$]]|$1|11|3|X|5|6|7|28|8|@]|9|@]|A|$]]|$1|12|3|X|5|6|7|29|8|@]|9|@]|A|$]]|$1|13|3|Z|5|10|7|2A|8|@]|9|@$D|2B|E|2C|1|2D]]|A|$]]|$1|14|3|X|5|6|7|2E|8|@]|9|@]|A|$]]|$1|15|3|X|5|6|7|2F|8|@]|9|@]|A|$]]|$1|16|3|Z|5|10|7|2G|8|@]|9|@$D|2H|E|2I|1|2J]]|A|$]]|$1|17|3|X|5|6|7|2K|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F|1G|-4]]|1H|$5|1B|1C|1D|A|$1E|1I|1G|-4]]|1J|$5|1B|1C|1D|A|$1E|1K|1G|-4]]]]

You might get this error when you import a class from another project, or change the path of the xaml file, or the namespace of either the xaml or behind .cs file.

One: It might have a namespace that is not the same as what you have in you new project

<pre><code>namespace TrainerB.MVC.Forms
{
 public partial class AboutDeveloper : ContentPage
 {
 public AboutDeveloper()
 {
 InitializeComponent();
 }
 }
}
</code></pre>

As you can see the name space in the imported file begins with the old project name: "TrainerB", but your new project might have a different name, so just change it to the correct new project name, in both the .xaml file and the behind .cs file.

Two:

change the properties of the .xaml file to:

Build Action: Embedded Resource

Custom Tool: MSBuild:UpdateDesignTimeXaml

<a href="https://i.stack.imgur.com/wz7sh.jpg"><img src="https://i.stack.imgur.com/wz7sh.jpg" alt="Xaml file properties"></a>

<a href="https://i.stack.imgur.com/DT6sJ.jpg"><img src="https://i.stack.imgur.com/DT6sJ.jpg" alt="Xaml Namespace Correcting 01"></a>

<a href="https://i.stack.imgur.com/VEKnQ.jpg"><img src="https://i.stack.imgur.com/VEKnQ.jpg" alt="Xaml Namespace Correcting 02"></a>

blocks|key|3162155|text|这个问题的另一个解决方案是简单地将XAML上的属性->+Build+Action从Embedded+Resource更改为任何其他内容，然后保存，然后将其更改回Embedded+Resource。错误就会消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162156|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another solution to this problem is to simply change the property-> Build Action on the XAML from Embedded Resource to anything else, save, then change it right back to Embedded Resource. The error goes away.

blocks|key|3162178|text|上面的答案对我来说都不起作用。除了重复的那些，我都试过了。然而，出于某种奇怪的原因，这在我的Visual+Studio+2015跨平台项目中起到了作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162179|在解决方案资源管理器中，|3162180|右击导致问题的项目。在弹出菜单中选择:添加-->类Xaml选择跨平台-->+Forms+|ordered-list-item|3162181|。保留漂亮的Page1.cs标准名称并单击添加。|3162182|请注意，由于某种原因，以前的InitializeComponent()-problem是如何消失的。|3162183|删除新创建的Page1.cs，并继续编程，就像Visual+Studio工作得很好一样。|3162184|3162185|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

None of the above answers worked for me. I tried them all except the duplicate ones. However for some weird reason this worked in my cross-platform project in Visual Studio 2015:

<ol>
<li>Right-click the project that is causing the problem in the Solution Explorer. In the pop-up menu choose: Add --> Class</li>
<li>Select cross-platform --> Forms Xaml Page. Keep the pretty Page1.cs standard name and click Add.</li>
<li>Notice how the previous InitializeComponent()-problem just disappeared for some reason.</li>
<li>Delete the newly created Page1.cs and continue programming as if Visual Studio was working just fine.</li>
</ol>

blocks|key|3162212|text|由于这似乎是关于缺少'InitializeComponent‘的问题的主要线索，我将在这里包含我的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162213|我也有这个问题，我已经尝试了我在这里找到的所有东西，以及谷歌可以找到的所有其他论坛，但都没有为我解决这个问题。在尝试了两个小时之后，我终于发现我的设置出了什么问题。|3162214|在我们的项目中，我们使用来自MahApps的Metro组件。给我带来麻烦的视图是继承自MetroWindow的视图，如下所示：|offset|length|3162215|<Controls:MetroWindow+x:Class="ProjectNamespace.MyView"
++++++++++++++++++++++xmlns:Controls="http://metro.mahapps.com/winfx/xaml/controls"
++++++++++++++++++++++...+>|code-block|syntax|javascript|3162216|现在，我将我的静态资源定义为|3162217|<Controls:MetroWindow.Resources>
++++<prop:Resources+x:Key="LocalizedStrings"/>
++++...
</Controls:MetroWindow.Resources>|3162218|在我的所有其他视图中，这就是我在UserControl中定义资源的方式，所以我认为这是可行的。|style|CODE|3162219|然而，Controls:MetroWindow并非如此！在那里，我绝对需要如下的资源定义：|3162220|<Controls:MetroWindow.Resources>
++++<ResourceDictionary>
++++++++<prop:Resources+x:Key="LocalizedStrings"/>
++++++++...
++++</ResourceDictionary>
</Controls:MetroWindow.Resources>|3162221|因此，总而言之，我的问题是缺少<ResourceDictionary>标记。我真的不知道为什么这会产生'InitializeComponent‘错误，奇怪的是，它甚至没有在我的每台机器上产生它，但这就是我修复它的方式。希望这能有所帮助(剩下的0.001%25遇到这个问题的人)。|3162222|entityMap|0|LINK|mutability|MUTABLE|url|http://mahapps.com/^0|0|0|E|7|0|0|0|0|0|G|B|0|3|K|0|0|F|K|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|H|3|I|5|J|7|1E|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1H|8|@$F|1I|G|1J|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1K|8|@$F|1L|G|1M|S|T]]|9|@]|A|$]]|$1|W|3|X|5|J|7|1N|8|@]|9|@]|A|$K|L]]|$1|Y|3|Z|5|6|7|1O|8|@$F|1P|G|1Q|S|T]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

Since this seems to be the go-to thread for the problem regarding missing 'InitializeComponent', I'll include my answer here.

I too was having this issue and I've tried everything I found here and in all other Forums that Google could find, however none resolved the issue for me. After two hours of trying everything, I finally figured out what was wrong with my setup.

In our project, we are using Metro components from <a href="http://mahapps.com/" rel="nofollow noreferrer">MahApps</a>. The view that was giving me trouble was a view inheriting from MetroWindow, like this:

<pre><code>&lt;Controls:MetroWindow x:Class="ProjectNamespace.MyView"
 xmlns:Controls="http://metro.mahapps.com/winfx/xaml/controls"
 ... &gt;
</code></pre>

Now, I have defined my static resources as

<pre><code>&lt;Controls:MetroWindow.Resources&gt;
 &lt;prop:Resources x:Key="LocalizedStrings"/&gt;
 ...
&lt;/Controls:MetroWindow.Resources&gt;
</code></pre>

That's how I've defined Resources in <code>UserControl</code>s in all my other views, so that's what I assumed will work.

That was, however, not the case with <code>Controls:MetroWindow</code>! There I absolutely needed the resource definition as follows:

<pre><code>&lt;Controls:MetroWindow.Resources&gt;
 &lt;ResourceDictionary&gt;
 &lt;prop:Resources x:Key="LocalizedStrings"/&gt;
 ...
 &lt;/ResourceDictionary&gt;
&lt;/Controls:MetroWindow.Resources&gt;
</code></pre>

So my issue, in summary, was a missing <code>&lt;ResourceDictionary&gt;</code> tag. I really don't know why this produced the 'InitializeComponent' error and it weirdly didn't even produce it on every machine of mine, but that's how I fixed it. Hope this helps (the remaining 0.001% of people encountering this issue).

blocks|key|262665|text|我尝试了上面所有的建议。如果你也尝试了，但没有成功，那就选择更简单的方法。创建一个新的page.xaml，然后复制新类的代码，然后删除出现问题的类XAML。不要花更多的时间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|262666|entityMap^0|11|F|1T|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I try all suggestions above. If you try too without success get the more easy way. Create a new page.xaml then copy your code for new class and delete class XAML with problems. Don't spend more time.

blocks|key|3162327|text|卸载整个解决方案，然后再次重新加载。然后重新构建解决方案。这为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162328|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unload the entire solution and then reload it again. Then Rebuild the solution. This resolved the issue for me.

blocks|key|257304|text|如果您使用的是Xamarin表单，并且您移动了一个XAML文件，那么该文件的“构建操作”就会改变。Xamarin+Forms需要"build+action+=+Embedded+Resource“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257305|在Visual+Studio中应用“生成操作”：|257306|Select+the+XAML+file+->+Properties+->+Build+Action+=+Embedded+Resource|offset|length|style|CODE|257307|entityMap^0|0|0|0|1Y|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

If you are using Xamarin Forms and you move a XAML file the "build action" of the file is changed. Xamarin Forms requires "build action = Embedded Resource".

Apply "build action" in Visual Studio:

<code>Select the XAML file -&gt; Properties -&gt; Build Action = Embedded Resource</code>

blocks|key|2948562|text|在这个线程中，最好的方法是使用VS2017+15.5.2加载LabelControlAdvancedSample的XAML，这是this+tutorial+page中的最后一个示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2948563|<Window+x:Class="WpfTutorialSamples.Basic_controls.LabelControlAdvancedSample"
++++xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
++++xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
++++Title="LabelControlAdvancedSample"+Height="180"+Width="250">
<StackPanel+Margin="10">
++++<Label+Target="{Binding+ElementName=txtName}">
++++++++<StackPanel+Orientation="Horizontal">
++++++++++++<Image+Source="http://cdn1.iconfinder.com/data/icons/fatcow/16/bullet_green.png"+/>
++++++++++++<AccessText+Text="_Name:"+/>
++++++++</StackPanel>
++++</Label>
++++<TextBox+Name="txtName"+/>
++++<Label+Target="{Binding+ElementName=txtMail}">
++++++++<StackPanel+Orientation="Horizontal">
++++++++++++<Image+Source="http://cdn1.iconfinder.com/data/icons/fatcow/16/bullet_blue.png"+/>
++++++++++++<AccessText+Text="_Mail:"+/>
++++++++</StackPanel>
++++</Label>
++++<TextBox+Name="txtMail"+/>
</StackPanel>|code-block|syntax|javascript|2948564|​|2948565|将App.xaml+&+App.xaml.cs保留为缺省值后，尝试编译上面的代码会产生链接器错误。|2948566|幸运的是，当鼠标悬停在LabelControlAdvancedSample.xaml.cs中的InitializeComponent()语句上时，有一个链接的文本提示：|2948567|2948568|显示潜在的修复程序。|blockquote|2948569|2948570|2948571|单击它将调用另一个链接的文本：|2948572|2948573|生成方法MainWindow.InitializeComponent。|2948574|2948575|2948576|这样做会产生以下“不做任何事情”的方法：|2948577|++++private+void+InitializeComponent()
++++{
++++++++throw+new+NotImplementedException();
++++}|2948578|必须为要构建的项目定义函数。看起来在WPF中的InitializeComponent实现与VB.Net有所不同。|2948579|xaml编辑：第一行的namespace.class不正确。根据MSDN和@Sean+B的answer的说法，它应该是|style|BOLD|2948580|<Window+x:Class="LabelControlAdvancedSample.MainWindow"|2948581|因此，项目编译时没有错误，并且不需要伪InitializeComponent方法，实际上它会生成更多的错误。去展示VS是有帮助的，即使在极其罕见的用户错误的情况下也是如此。:P|2948582|entityMap|0|LINK|mutability|MUTABLE|url|http://www.wpf-tutorial.com/basic-controls/the-label-control/|1|https://social.msdn.microsoft.com/Forums/vstudio/en-US/5f47ea5d-d0a7-4c62-ac97-8a21a69487ec/initializecomponent-is-it-necessary?forum=vbgeneral|2|https://msdn.microsoft.com/en-au/library/hh830433.aspx?f=255&MSPPError=-2147217396|3|https://stackoverflow.com/a/7730022/2128797^0|1S|I|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|19|6|1|0|7|1G|W|4|2|19|6|3|0|0|0|2G|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|D|3|E|5|F|7|1X|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|20|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|21|8|@]|9|@]|C|$]]|$1|P|3|Q|5|R|7|22|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|23|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|24|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|25|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|26|8|@]|9|@]|C|$]]|$1|X|3|Y|5|R|7|27|8|@]|9|@]|C|$]]|$1|Z|3|-4|5|6|7|28|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|29|8|@]|9|@]|C|$]]|$1|11|3|12|5|6|7|2A|8|@]|9|@]|C|$]]|$1|13|3|14|5|F|7|2B|8|@]|9|@]|C|$G|H]]|$1|15|3|16|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|17|3|18|5|6|7|2G|8|@$A|2H|B|2I|19|1A]]|9|@$A|2J|B|2K|1|2L]|$A|2M|B|2N|1|2O]]|C|$]]|$1|1B|3|1C|5|F|7|2P|8|@]|9|@]|C|$G|H]]|$1|1D|3|1E|5|6|7|2Q|8|@$A|2R|B|2S|19|1A]]|9|@]|C|$]]|$1|1F|3|-4|5|6|7|2T|8|@]|9|@]|C|$]]]|1G|$1H|$5|1I|1J|1K|C|$1L|1M]]|1N|$5|1I|1J|1K|C|$1L|1O]]|1P|$5|1I|1J|1K|C|$1L|1Q]]|1R|$5|1I|1J|1K|C|$1L|1S]]]]

The best shot at an MCVE in this thread is, with VS2017 15.5.2, load up the XAML of LabelControlAdvancedSample, the last example in <a href="http://www.wpf-tutorial.com/basic-controls/the-label-control/" rel="nofollow noreferrer">this tutorial page</a>.

<pre><code>&lt;Window x:Class="WpfTutorialSamples.Basic_controls.LabelControlAdvancedSample"
 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
 xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
 Title="LabelControlAdvancedSample" Height="180" Width="250"&gt;
&lt;StackPanel Margin="10"&gt;
 &lt;Label Target="{Binding ElementName=txtName}"&gt;
 &lt;StackPanel Orientation="Horizontal"&gt;
 &lt;Image Source="http://cdn1.iconfinder.com/data/icons/fatcow/16/bullet_green.png" /&gt;
 &lt;AccessText Text="_Name:" /&gt;
 &lt;/StackPanel&gt;
 &lt;/Label&gt;
 &lt;TextBox Name="txtName" /&gt;
 &lt;Label Target="{Binding ElementName=txtMail}"&gt;
 &lt;StackPanel Orientation="Horizontal"&gt;
 &lt;Image Source="http://cdn1.iconfinder.com/data/icons/fatcow/16/bullet_blue.png" /&gt;
 &lt;AccessText Text="_Mail:" /&gt;
 &lt;/StackPanel&gt;
 &lt;/Label&gt;
 &lt;TextBox Name="txtMail" /&gt;
&lt;/StackPanel&gt;
</code></pre>



Having left the App.xaml &amp; App.xaml.cs at default, attempting to compile the above produces the linker error. 
Fortunately, when hovering over the InitializeComponent() statement in LabelControlAdvancedSample.xaml.cs there is a linked text hint: 

<blockquote>
 Show potential fixes.
</blockquote>

Clicking it invokes another linked text:

<blockquote>
 Generate method MainWindow.InitializeComponent.
</blockquote>

Doing this produces the following "do nothing" method:

<pre><code> private void InitializeComponent()
 {
 throw new NotImplementedException();
 }
</code></pre>

The function must be defined for the project to build. Looks like something differs in the implementation of InitializeComponent in WPF to <a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/5f47ea5d-d0a7-4c62-ac97-8a21a69487ec/initializecomponent-is-it-necessary?forum=vbgeneral" rel="nofollow noreferrer">VB.Net</a>. 
Edit: The namespace.class in the first line of the xaml is not correct. 
According to <a href="https://msdn.microsoft.com/en-au/library/hh830433.aspx?f=255&amp;MSPPError=-2147217396" rel="nofollow noreferrer">MSDN</a> and @Sean B's <a href="https://stackoverflow.com/a/7730022/2128797">answer</a>, it should be 

<pre><code>&lt;Window x:Class="LabelControlAdvancedSample.MainWindow"
</code></pre>

Thus the project compiles without error and the dummy InitializeComponent method is not required, in fact it generates more errors. Goes to show VS can be helpful, even in the extremely rare case of user error. :P

blocks|key|257328|text|我知道这是由于不同的原因而被回答的，但这是一篇很受欢迎的帖子，我在一个类库中遇到了同样的问题。在这种情况下，事实证明这既是我的命名空间中的一个更改(在本文的here中得到了回答)，也是因为编译器无法重新构建定义InitializeComponent()方法的Window.g.i.cs。它不能，因为类库在csproj文件中缺少WPF项目的ProjectTypeGuid值。有关这一点的说明是here和here。我想我会分享，以防其他人遇到同样的问题。在这种情况下，仅仅更改名称空间是不够的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|257329|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/7730022/1688919|1|https://stackoverflow.com/a/3574603/1688919|2|https://stackoverflow.com/a/47224727/1688919^0|26|4|0|5F|4|1|5K|4|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

I know this was answered due to a different cause, but this is a highly hit posting and I had ran into the same issue with a class library. In this case, it turned out to be both a change in my namespace (answered in this post <a href="https://stackoverflow.com/a/7730022/1688919">here</a>) and that the compiler could not rebuild the Window.g.i.cs which defines the InitializeComponent() method. It couldn't because the class library was missing the ProjectTypeGuid value for WPF projects in the csproj file. Instructions for this are <a href="https://stackoverflow.com/a/3574603/1688919">here</a> and <a href="https://stackoverflow.com/a/47224727/1688919">here</a>. I thought I would share in case someone else has run into the same issue. Just changing the namespace isn't enough in this case.

blocks|key|3162455|text|我在VS2017，Xamarin.Forms项目中也遇到了同样的问题。正在阅读此错误链接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162456|https://bugzilla.xamarin.com/show_bug.cgi?id=33181#c53|offset|length|3162457|要解决本例中的问题:右键单击[xaml-file-name].xaml，选择Properties，然后将Build+Action更改为Content，然后返回到Embedded+resource。|style|CODE|3162458|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1I|0|0|E|L|12|A|1G|C|1V|7|28|H|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@$D|W|E|X|H|I]|$D|Y|E|Z|H|I]|$D|10|E|11|H|I]|$D|12|E|13|H|I]|$D|14|E|15|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]]]

I had the same problem in VS2017, Xamarin.Forms project. Reading this bug link:

<a href="https://bugzilla.xamarin.com/show_bug.cgi?id=33181#c53" rel="nofollow noreferrer">https://bugzilla.xamarin.com/show_bug.cgi?id=33181#c53</a>

To solve the problem in this case: Right-click on <code>[xaml-file-name].xaml</code>, choose <code>Properties</code>, then change the <code>Build Action</code> to <code>Content</code> then back to <code>Embedded resource</code>.

blocks|key|257336|text|在我的例子中，程序的实例已经在后台运行。我只是停止正在运行的实例和成功构建的程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257337|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case the instance of program was already running in background. I just stop the running instance and program built successfully.

blocks|key|3162491|text|检查+Designer+文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3162492|我也有同样的问题。在我的例子中，原因是FileName.Designer.cs的namespace与FileName.cs中使用的(正确的)+namespace不匹配。|CODE|3162493|更改FileName.Designer.cs的namespace以匹配FileName.cs的the立即解决了问题。|3162494|entityMap^0|0|2|3|8|C|3|0|14|9|1Z|9|0|N|9|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|H]|$9|W|A|X|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|Y|8|@$9|Z|A|10|B|H]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|L|$]]

Check the Designer file.

I had this same issue. In my case, the cause was that the <code>namespace</code> for FileName.Designer.cs did not match the (correct) <code>namespace</code> used in FileName.cs.

Changing the <code>namespace</code> of FileName.Designer.cs to match that of FileName.cs solved the problem immediately.

blocks|key|257366|text|对我有帮助的是将.csproj中的第一行改为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257367|<Project+Sdk="Microsoft.NET.Sdk.WindowsDesktop">|code-block|syntax|javascript|257368|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What helped me - is to change first line in .csproj to

<pre><code>&lt;Project Sdk="Microsoft.NET.Sdk.WindowsDesktop"&gt;
</code></pre>

blocks|key|259679|text|其他选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|259680|在我使用Xamarin表单的情况下，除了我的App.xaml文件中的“InitializeComponent”不存在于当前上下文错误之外，我还在输出中注意到.csproj文件构建失败。真奇怪。|259681|除了下面这两个ItemGroup条目之外，文件本身没有什么特别之处：|259682|++<ItemGroup>
++++<EmbeddedResource+Remove="App.xaml"+/>
++</ItemGroup>

++<ItemGroup>
++++<ApplicationDefinition+Include="App.xaml"+/>
++</ItemGroup>|code-block|syntax|javascript|259683|我从.csproj文件中删除了这两个文件，执行了清理和重建，错误最终消失了。如此痛苦地解决这个问题，也许这会帮助别人在未来的道路上避免一些压力。|259684|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Additional option:

In my case with Xamarin Forms, on top of the 'InitializeComponent' does not exist in the current context error in my App.xaml file, I also noticed in the output that the .csproj file was failing to build. Weird.

Nothing in the file itself stood out to me except these two ItemGroup entries:

<pre><code> &lt;ItemGroup&gt;
 &lt;EmbeddedResource Remove="App.xaml" /&gt;
 &lt;/ItemGroup&gt;

 &lt;ItemGroup&gt;
 &lt;ApplicationDefinition Include="App.xaml" /&gt;
 &lt;/ItemGroup&gt;
</code></pre>

I removed both from the .csproj file, performed a clean and rebuild and the error finally disappeared. So painful resolving the issue, maybe this will help someone else avoid a bit of stress down the road.

blocks|key|261471|text|在我的例子中(NET+Core3.1)，我通过在项目文件的ProjectGroup部分给它一个AssemblyName标签来修复它。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|261472|<Project+Sdk="Microsoft.NET.Sdk.WindowsDesktop">
++<PropertyGroup>
++++<TargetFramework>netcoreapp3.1</TargetFramework>
++++<UseWPF>true</UseWPF>
++++<AssemblyName>ProjectNameUsually</AssemblyName>
++</PropertyGroup>
++...
</Project>|code-block|syntax|javascript|261473|这也修复了编译器在代码隐藏中看不到x:Name控件的问题。|261474|entityMap^0|T|C|1B|C|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

In my case (NET Core 3.1) I fixed it by giving it an <code>AssemblyName</code> tag in the <code>ProjectGroup</code> section of the project file. e.g.
<pre><code>&lt;Project Sdk=&quot;Microsoft.NET.Sdk.WindowsDesktop&quot;&gt;
 &lt;PropertyGroup&gt;
 &lt;TargetFramework&gt;netcoreapp3.1&lt;/TargetFramework&gt;
 &lt;UseWPF&gt;true&lt;/UseWPF&gt;
 &lt;AssemblyName&gt;ProjectNameUsually&lt;/AssemblyName&gt;
 &lt;/PropertyGroup&gt;
 ...
&lt;/Project&gt;
</code></pre>
This also fixed a problem it was having with the compiler not seeing a control by its x:Name in the code-behind.

blocks|key|3162617|text|在我向解决方案配置管理器添加了一个新的平台'x86‘之后，我也收到了这个错误消息。在它只有“任何CPU”之前。解决方案仍在运行，但在错误窗口中显示了多条此类错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162618|我发现问题是在项目属性中‘输出路径’现在指向"bin\x86\Debug“。这是由Configuration+Manager在添加操作时放入的。'Any+CPU‘平台的输出路径总是"bin“(因为这个测试项目从来不是以发布模式构建的)，所以Configuration+Manager认为它应该自己添加"\x86\Debug”。从错误消息中没有任何迹象表明构建输出可能是原因，我仍然不明白项目怎么会像这样运行。在将新的'x86‘配置中的所有项目设置为"bin“之后，所有的错误都消失了。|3162619|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this error messages too after I added a new platform 'x86' to the Solution Configuration Manager. Before it had only 'Any CPU'. The solution was still running but showed multiple of these error messages in the error window.
I found the problem was that in the project properties the 'Output Path' was now pointing to &quot;bin\x86\Debug&quot;. This was put in by Configuration Manager at the add operation. The output path of the 'Any CPU' platform was always just &quot;bin&quot; (because this test project was never built in release mode), so the Configuration Manager figured it should add the &quot;\x86\Debug&quot; by itself. There was no indication whatsoever from the error messages that the build output could be the cause and I still don't understand how the project could even run like this. After setting it to &quot;bin&quot; for all projects in the new 'x86' configuration all of the errors vanished.

blocks|key|3162632|text|当我没有使用最新的VS2019+16.7.5更改代码时，出现了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162633|只需打开相应的XAML文件进行编辑就解决了这个问题。|3162634|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The issue appeared while I did not change the code, using a recent VS2019 16.7.5.
Just opening for edition the corresponding XAML file solved the problem.

blocks|key|257418|text|我在WPF中遇到了类似的问题。我复制了一个用户控件，但忘记在its.xaml.cs文件中为它重命名公共ViewModel属性。但还是不起作用。我最终删除了该项目的obj\debug类型文件夹中的所有文件(我们使用了不同的名称)。并重建了它。它仍然不工作，我退出了Visual+Studio。(在此之前，我可能有两个Visual+Studio实例。)我遇到的问题是，当我已经修复它的时候，它却报告它有这个错误！当我回到Visual+Studio+(在删除了obj中的调试内容之后)，终于没有错误指示器了。然后我重建了项目，现在一切都好了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|257419|这不是我在这里做事情的确切顺序。它需要简化。|257420|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had a problem similar to this in WPF. I had copied a usercontrol but had forgotten to rename the public ViewModel property in its.xaml.cs file for it. But still wasn't working. I eventually deleted all of the files inside the obj\debug type of folder for the project (we had this named differently). And rebuilt it. It still wasn't working, and I exited Visual Studio. (Before this I had at one point two instances of Visual Studio I think maybe.) The problem I had was that it was reporting it had this error when I had already fixed it! When I came back into Visual Studio (after deleting the debug stuff in obj), there finally was no error indicator. Then I rebuilt the project and now all was good!
This is not the exact order that I did things here. It needed to be simplified.

blocks|key|3162639|text|我的方法是关闭解决方案并删除解决方案路径下的".vs“文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3162640|(它将使您丢失所有编辑器状态-已打开文件的列表、窗口位置和错误缓存)|offset|length|style|BOLD|3162641|它总是有效的。|3162642|entityMap^0|0|T|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

My way is close solution and delete &quot;.vs&quot; folder under the solution path. 
(it will make you lost all of your editor status - list of opened files, window location, and error cache)
It always work.

blocks|key|262818|text|OK+++++this.InitializeComponent();+

Wrong++this.InitializeComponent;|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|262819|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>OK this.InitializeComponent(); 

Wrong this.InitializeComponent;
</code></pre>

If I create a new project in Visual Studio 2010 SP1 and select "WPF Application" and tries to build the generated application, I get the error

<blockquote>
 The name 'InitializeComponent' does not exist in the current context.
</blockquote>

I got a similar error this morning when I tried to build my current project. Yesterday, I had no problem compiling and running it.

I created a new project and got the error whenever I compiled the project. I have just sent the project to a colleague, and he has just compiled without any errors.

What is wrong?

The name 'InitializeComponent' does not exist in the current context

Visual Studio

编译器

Windows

Xamarin

如果我在Visual Studio2010 SP1中创建一个新项目并选择"WPF Application“并尝试构建生成的应用程序，则会出现以下错误名称'InitializeComponent‘在当前上下文中不存在。今天早上，当我试图构建我当前的项目时，我得到了一个类似的错误。昨天，我编译和运行它没有任何问题。我创建了...

问名称'InitializeComponent‘在当前上下文中不存在
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问名称'InitializeComponent‘在当前上下文中不存在EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问名称'InitializeComponent‘在当前上下文中不存在
EN