Microsoft®Visual Basic编译器遇到问题，需要关闭。

Error occurred on Visual Studio Team System 2008 Development Edition with Visual SourceSafe 2005.  The error most likely appears while opening solution; checking files into VSS; get latest version while working folder contains a writable copy of a different version of files. The error prevented us from running the application in our development box.  After two days of talking with Microsoft technical support VB.net team and running though many tests, we still had no solution for this problem.  The only useful thing we learned was that this error only occurs for large web applications.  Visual Studio works fine for all other projects but this one.  Since the Microsoft support technician mentioned file reference a couple times, we guessed if a reference was pointing to a file which is not there any longer, some errors will be generated.  We tried to delete everything in the bin folder within the project working folder of VSS.  We got latest version of the solution and rebuilt it.  This large web application compiled and debugged well again.

在Visual Studio Team System 2008开发版和Visual SourceSafe 2005上发生错误。打开解决方案时最有可能出现该错误。 将文件检入VSS； 当工作文件夹包含不同版本文件的可写副本时，获取最新版本。 该错误使我们无法在开发框中运行该应用程序。 与Microsoft技术支持VB.net团队讨论了两天并进行了许多测试之后，我们仍然没有解决该问题的方法。 我们了解到的唯一有用的事情是，此错误仅在大型Web应用程序中发生。 Visual Studio适用于除此项目之外的所有其他项目。 由于Microsoft支持技术人员多次提到文件引用，因此我们猜测如果引用指向的文件不再存在，则会产生一些错误。 我们试图删除VSS项目工作文件夹中bin文件夹中的所有内容。 我们获得了该解决方案的最新版本并进行了重建。 这个大型Web应用程序再次编译和调试良好。

After the effect, we learned that only the .suo (Solution User Options) file needs to be removed and reloaded from VSS because service references and .dll references are stored in the .suo file.  When .suo file crashed, the VBC error occurred.  It seems the .suo file working in a way like stored themes in a profile.  The .suo file is unique to your environment and your machine.  The .suo file is a structured or compound storage.  The file stored in a binary format.  User information is saved into stream.  The name of the stream is the key that will be used to identify the information in the .suo file.  This .suo problem is not the same problem that caused by a bug in the Visual Studio 2005.  That was a Visual Basic 2005 compiler bug in an ASP.net project when debugging application code by using Edit and Continue feature in the IDE.  There is a hot fix for that bug that you can find at: http://support.microsoft.com/kb/915038 

产生效果之后，我们了解到仅需要删除.suo（解决方案用户选项）文件，并从VSS重新加载，因为服务引用和.dll引用存储在.suo文件中。 .suo文件崩溃时，发生VBC错误。 .suo文件的工作方式似乎与配置文件中存储的主题类似。 .suo文件对于您的环境和计算机而言是唯一的。 .suo文件是结构化或复合存储。 该文件以二进制格式存储。 用户信息将保存到流中。 流的名称是将用于标识.suo文件中的信息的密钥。 此.suo问题与由Visual Studio 2005中的错误引起的问题不同。这是使用IDE中的“编辑并继续”功能调试应用程序代码时，ASP.net项目中的Visual Basic 2005编译器错误。 您可以在以下位置找到该错误的热修复程序： http : //support.microsoft.com/kb/915038

翻译自: https://www.experts-exchange.com/articles/2394/Microsoft-Visual-Basic-Compiler-has-encountered-a-problem-and-needs-to-close.html