我也有同样的问题，但对我来说，这些都没用。在我的情况下，我拥有的每个WPF项目(包括新创建的项目)都停止编译此错误。最后，我卸载了所有的。net框架，然后重新安装了它们，一切又开始工作了。我还重新安装了Visual Studio，但结果没有影响。

我的方法是关闭解和删除”。解决方案路径下的Vs "文件夹。 (它会让你丢失所有的编辑器状态-打开的文件列表，窗口位置和错误缓存)

它总是有效的。

导航到解决方案目录 删除\obj文件夹 重新构建解决方案

我在重构过程中遇到了这个错误，我重命名了一些文件/文件夹，并且需要重新生成预先存在的*.g.cs文件。

对于那些在调试模式下没有错误，但在发布模式下有指定的错误(但项目运行正常)的人来说，这里有一些简单的尝试:

打开与出现问题的XAML .cs文件对应的XAML文件。 进行编辑——任何编辑，比如在某处添加空格 保存文件并关闭

这种方法在VS 2015中对我有效，根据其他用户的说法，在2017年和2019年也是如此

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!

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

我发现“启动对象”(未设置)为我导致此错误。

“启动对象”(未设置)