导致这个错误的另一个常见原因是:

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

我在重命名用户控件时遇到了这个问题。我修复它的方法是注释掉InitializeComponent，验证所有名称都是正确的(xaml和后面的代码)，构建项目，取消InitializeComponent的注释，然后再次构建。听起来这个问题可能有几个原因/解决方案，但这种方法对我来说很管用。

其他选项:

在我使用Xamarin Forms的情况下，在“InitializeComponent”的顶部，在我的App.xaml文件中的当前上下文错误中不存在，我还注意到在输出中，.csproj文件未能构建。奇怪。

除了下面两个ItemGroup条目外，文件本身没有什么特别引人注目的:

  <ItemGroup>
    <EmbeddedResource Remove="App.xaml" />
  </ItemGroup>

  <ItemGroup>
    <ApplicationDefinition Include="App.xaml" />
  </ItemGroup>

我从.csproj文件中删除了这两个文件，执行了清理和重建，错误最终消失了。解决这个问题很痛苦，也许这将帮助其他人避免一些压力。

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!

这和我之前做的顺序不一样。它需要被简化。

这发生在我身上，因为一个Nuget包卸载程序吹走了App.xaml中<Application>元素上的所有属性。这包括x:Class属性，它指定应用程序类名。因此从未生成包含InitializeComponent()方法的分部类。

我通过将App.xaml恢复到源控制副本来解决这个问题。

问题出现时，我没有改变代码，使用最近的VS2019 16.7.5。

只要打开相应的XAML文件就可以解决这个问题。