Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Studio:Visual Studio Error Messages  [ 232 result(s) ]
MICROSOFT 
  -  Visual Studio has encountered an unexpected error.  MICROSOFT
This error generally occurs when Visual Studio receives data in an unexpected format or receives data from an unexpected source.
Close and then restart Visual Studio.
Visual Studio Error Messages
Comments
 
  -  Microsoft Visual Studio is not responding. If this continues, please shut down and restart your application.  MICROSOFT
Visual Studio Macros has lost connection with the host application.
Shut down the host application and then restart it.
Visual Studio Macros Error Messages
Comments
 
  -  Visual Studio is waiting for an operation to complete. If you regularly encounter this delay during normal usage please report this problem to Microsoft.  MICROSOFT
The server application has not completed the current request. This error might also be caused by antivirus software blocking some devenv.exe processes. Several features in the product use scripts, and these scripts might be blocked by antivirus software. For related information, see "PRB: Visual IDE does not open when started or application cannot start error message" online at http://support.microsoft.com/default.aspx?scid=kb;en-us;306905&Product=vsnet.
Choose Switch To to open the application and investigate the problem. —or— Choose Retry to wait for the server application to finish processing the request. To correct antivirus related errors In your antivirus software, specify that the software should allow scripts that originate from devenv.exe to run. For detailed instructions, see the product documentation for the antivirus software.
Visual Studio Error Messages
Comments
 
  -  Wizard file is missing a required value.  MICROSOFT
The .vsz file for the wizard does not have the correct format. This error occurs when a .vsz file is corrupted or if the file is from a product other than Visual Studio.
Verify that the wizard is a Visual Studio wizard and try again. —or— Re-install Visual Studio to replace the corrupted file.
Visual Studio 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
 
  -  The application requires a .dll for class ID .  MICROSOFT
Visual Studio could not find the DLL for the class that you specified. This is an operating system error.
Re-install Visual Studio or the affected application and try again.
Visual Studio Error Messages
Comments
 
  -  This program requires an application for class ID .  MICROSOFT
Visual Studio could not find the application you are trying to use. This message is an operating system error.
Re-install the affected application and try again. —or— Re-install Visual Studio and try again.
Visual Studio Error Messages
Comments
 
  -  Type library was not found.  MICROSOFT
Visual Studio cannot run without the DTE.olb and vsext.tlb type libraries. This error generally occurs when these two files have been removed or deleted.
Re-install Visual Studio.
Visual Studio Error Messages
Comments
 
  -  Item cannot be added to the Toolbox.  MICROSOFT
This error generally occurs when you attempt to add an item for which the Toolbox cannot display a shortcut icon. Items which the Toolbox can display include: Controls and .NET Framework components installed on your local machine. Note Controls and components for ASP.NET Web forms must have an AspNetHostingPermission.Level Property of "Unlimited" to be displayed in the Toolbox. Selected text dragged or pasted from a Visual Studio editor, such as code snippets. Items which the Toolbox cannot display include: Excel workbook files. .NET Framework assemblies installed on shared network servers. Note: An assembly added from a UNC path is not fully trusted, so it is not granted sufficient permissions to be displayed in the Toolbox.
Use the Customize Toolbox dialog box to add a control or component that is installed on your local machine to the active Toolbox tab. - or - Drag or paste selected text from a Visual Studio editor onto the Toolbox.
Visual Studio Error Messages
Comments
 
  -  Wizard file format is not recognized.  MICROSOFT
The wizard cannot be opened. This error is generally caused by a corrupted wizard file or a wizard that does not match the version number of Visual Studio.
Verify that the wizard file has the same version number as the version of Visual Studio listed as the value of VSWIZARD, such as VSWIZARD 7.0. —or— Re-install Visual Studio to repair the corrupted file.
Visual Studio Error Messages
Comments
 
 

 
Visual Studio Error Messages (127)
Visual Basic .Net Compiler Messages (16)
Visual Studio Macros Error Messages (24)
Visual Studio Project Error Messages (64)
Visual Basic .Net Run-Time Messages (1)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next