Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Studio Project Error Messages  [ 83 result(s) ]
MICROSOFT 
  -  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 Visual Studio or within Visual Studio 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.
Visual Studio Project Error Messages
Comments
 
  -  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 Visual Studio or within Visual Studio 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.
Visual Studio Project Error Messages
Comments
 
  -  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 Visual Studio 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 Visual Studio. Make sure that you are logged on as an Administrator or as a member of a group that has permission to access the registry.
Visual Studio Project Error Messages
Comments
 
  -  Error: the dependency 'file' in project 'project' cannot be copied to the run directory because it would conflict with dependency 'file'  MICROSOFT
There is a conflict between references; more than one distinct dependency with the same file name being copied to the bin directory for the application to run. The run directory cannot resolve the conflict because none of the dependencies are primary references. This error will cause the build to fail. Double-clicking this Task List item will take you to the references node of the project in which the conflict is occurring.
Make one of the assemblies a direct reference of your project. A possible downside to this approach is that the assembly you choose is not guaranteed to work with assemblies that require some other version of the referenced assembly. - or - Make sure that both copies of the assembly are strong-named and in the global assembly cache. This eliminates the need to copy the assemblies to the bin directory.
Visual Studio Project Error Messages
Comments
 
  -  Warning: the dependency 'file' in project 'project' cannot be copied to the run directory because it would overwrite the reference 'file.'  MICROSOFT
There is a conflict between dependencies; more than one distinct assembly files with the same name should be copied to the bin directory for the application to run. The run directory is able to resolve the conflict since one of the dependencies is a primary reference. Double-clicking this Task List item will take you to the primary reference node that is conflicting. This warning occurs when you have a dependency conflict but have worked around it by adding one of the conflicting dependencies as a reference. Or you may have had a version 1 reference, and then added a second reference which itself references the version 2 of the first reference. That is, this error occurs because the projects in your solution have references to each other, but the references were created as file references (using the Browse button in the Add Reference dialog box), rather than project to project references (using the Project tab on the Add Reference dialog box). The advantage of a project to project reference is that it creates a dependency between the projects in the build system so that the dependent project will be built if it has changed since the last time the referencing project was built. A file reference does not create a build dependency so it is possible to build the referencing project without building the dependent project, and so a reference can become obsolete; a project can reference a previously built version of the project. This can result in several versions of
Copy one (or zero) assembly files to the bin directory, which can be done by putting the assembly files into the global assembly cache. The global assembly cache resolves file name conflicts. No local copies of the assembly file will be made because the common language runtime knows how to find assemblies in the global assembly cache. For more information, see Working with Assemblies and the Global Assembly Cache and Error: the dependency 'file' in project 'project' cannot be copied to the run directory because it would conflict with dependency 'file'.
Visual Studio Project Error Messages
Comments
 
  -  Error on line . Expected 'expected' but found 'found'  MICROSOFT
This is a general XML parsing error when reading the project file. This error can occur for project files (.vbproj/.csproj) as well as per-user settings files (.vbproj.user/.csproj.user). More information will be provided by the project system in the parameters expected and found. This error is most likely caused by editing the project (or user) file by hand.
Edit the project file again and restore it to a satisfactory condition. Depending on the severity of the error, you may not be able to open the project.
Visual Studio Project Error Messages
Comments
 
  -  An error has been encountered that prevents reference 'reference' from loading.  MICROSOFT
A fatal error has been encountered when removing a reference from the project file. The causes for this error are identified in , and could be: Malformed GUID for a reference. This is applicable for COM references only. Bad wrapper tool. Currently, the wrapper tool property can be one of tlbimp, aximp, or primary. This is applicable for COM references only. Bad project reference string. This is applicable for project-to-project references only.
Add the reference to the project to resolve this error. Any reference for which this diagnostic is displayed will not be loaded into the project.
Visual Studio Project Error Messages
Comments
 
  -  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.
Visual Studio Project Error Messages
Comments
 
  -  The project file '' cannot be updated  MICROSOFT
You are attempting to open a project created in an earlier version of Visual Studio 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.
Visual Studio Project Error Messages
Comments
 
  -  The project file is missing the 'subsection' sub-section of the 'section' section  MICROSOFT
The SubSection (subsection) is Include and section (section) is Files. This error is most likely caused by editing the project file by hand.
Work in Show All Files mode (by clicking that button in the Solution Explorer toolbar) and include relevant files. If you get this error, the project will open, but no files will be added to the project.
Visual Studio Project Error Messages
Comments
 
 

 
Visual Basic .Net Compiler Messages (3)
Visual Studio Macros Error Messages (7)
Visual Studio Project Error Messages (64)
Visual Studio Error Messages (9)
 
  Prev   1  2  3  4  5  6  7  8  9  Next