- COM Interop registration failed MICROSOFT There is a failure in the registration of an assembly that exposes functionality to COM clients. The build process will fail if this error occurs. Assemblies can expose objects to COM clients. The project system provides a property to register exposed classes for COM interop, as well as to generate and register a type library so that these classes are usable from scripting languages as well as Visual Basic 6. See the Build property page in the Configuration Properties folder to access the Register for COM Interop property. Some possible reasons for failure include: Inability to generate a type library for the assembly. This could be a disk space problem or a file locking issue where the type library is locked either by VisualStudio or some other process. Also, type libraries for referenced assemblies may not be registered properly on your system. Inability to register the generated type library. This could be a permissions problem in the registry. Inability to register classes in the assembly. This could be a permissions problem in the registry. Create some free disk space on your computer. If there is a file-locking issue, restart VisualStudio. Make sure that you are logged on as an Administrator or as a member of a group that has permission to access the registry. VisualStudioProjectErrorMessagesComments

- Cannot copy multifile assembly component 'component_filename' to file 'destination_filename'. MICROSOFT The specified component was not copied to the bin directory. Some assemblies consist of multiple files. This diagnostic is displayed whenever a file that is part of a multifile assembly cannot be copied to the run directory. There could be several reasons for failure. For example, running out of disk space or reaching the MAX_PATH limit for path lengths. Also, a process, perhaps VisualStudio, might be holding onto the component that cannot be copied. Check for adequate free disk space. Try moving the project to a folder whose path length is less than the path length of the current project folder. Change the output directory to a folder with a smaller absolute path length. This is applicable for client (non-Web) projects only. Restart VisualStudio. VisualStudioProjectErrorMessagesComments

- Licenses processor error/warning: MICROSOFT An error or warning message is displayed if a tool returns an error or a warning while processing a .licx file. As part of the build process, the project system transforms the Licenses.licx file (if present) into a binary file understood by the .NET Framework license manager. This transformation is done using in-process tools. The most likely cause of such an error or warning is a bad .licx file. A .licx file can become corrupt if the file has been edited outside of VisualStudio or within VisualStudio using a text editor. These files are normally managed by the Windows Forms and Web Forms Designers. Fix the format of the .licx file. An error means that the binary file has not been generated, and that the build process will fail. Warnings are for informational purposes only. VisualStudioProjectErrorMessagesComments

- Resources processor error/warning: MICROSOFT An error or warning message is displayed if a tool returns an error or a warning while processing a .resx file. As part of the build process, the project system transforms each .resx file into a binary file understood by the .NET Framework resource manager. This transformation is done using in-process tools. The most likely cause of such an error or warning is a bad .resx file. A .resx file can become corrupt if the file has been edited outside of VisualStudio or within VisualStudio using a text editor. These files are normally managed by the Windows Forms and Web Forms Designers. Fix the format of the .resx file. An error means that the binary file has not been generated, and that the build process will fail. Warnings are for informational purposes only. VisualStudioProjectErrorMessagesComments

- A failure occurred while attempting to start the compilation MICROSOFT An unknown error has been encountered while issuing the Start Build request to the Visual Basic or Visual C# compiler. Restart VisualStudio. This error will cause the build process to fail. VisualStudioProjectErrorMessagesComments

- has lost the link to . Your work will be exported to when you quit the application. MICROSOFT The host application has stopped responding or been shut down. VisualStudio Macros needs the host application to function correctly. Click OK to export all unsaved project items to the current directory and close VisualStudio Macros. Restart VisualStudio. VisualStudio Macros ErrorMessagesComments

- The project file '' cannot be updated MICROSOFT You are attempting to open a project created in an earlier version of VisualStudio 2005. The project must be updated to the current format, but it cannot be updated because either the specified project file (.vbproj) is marked as read-only or the file is under source control and is currently locked by another user. In Windows Explorer, locate the specified project file. On the File menu, choose Properties. In the Properties dialog box, uncheck the Read-only attribute. If the file is under source code control and is locked by another user, wait until the file is available and check it out locally. VisualStudioProjectErrorMessagesComments

- The project file is missing the 'section' section MICROSOFT The .vbproj or .csproj file is corrupt. One of the following sections is missing: Build Files VisualStudio VisualBasic or CSHARP If the VisualStudio, VisualBasic, or CSHARP section is missing, the project will not load. If the Build or Files section is missing, the project file will load as follows: If Build is missing, all build settings and configuration information will be lost. If Files is missing, the project will have no files in it. Recreate your project. VisualStudioProjectErrorMessagesComments

- Could not determine whether 'assembly' is a multifile assembly. The assembly manifest may be corrupt. MICROSOFT The project system was unable to read an assembly referenced by your project such that the project system is unable to determine which files were referenced by the assembly. Reinstall VisualStudio (if the assembly came with VisualStudio or the .NET Framework). - or - Reinstall the appropriate third-party control. This error will not prevent the project from building. However, a run-time error is possible. VisualStudioProjectErrorMessagesComments