Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Studio Error Messages:Visual Basic .Net Compiler Messages  [ 16 result(s) ]
MICROSOFT 
 BC31021  -  Visual Basic compiler is unable to recover from the following error: <error>  MICROSOFT
The Visual Basic compiler is unable to recover from the following error: <error>. Some IDE features have been disabled. An internal error has occurred in the Visual Basic compiler.
Save your work and restart Visual Studio. If the error recurs, reinstall Visual Studio. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC30145  -  Unable to emit assembly: <error message>  MICROSOFT
The Visual Basic compiler calls the Assembly Linker (Al.exe, also known as Alink) to generate an assembly with a manifest, with the linker reporting an error in the emission stage of creating the assembly.
Examine the quoted error message and consult the topic Al.exe Tool Errors and Warnings for further explanation and advice. Try signing the assembly manually, using either the Assembly Linker (Al.exe) or the Strong Name Tool (Sn.exe). If the error persists, gather information about the circumstances and notify Microsoft Product Support Services. To sign the assembly manually Use the Strong Name Tool (Sn.exe) to create a public/private key pair file. This file has a .snk extension. Delete the COM reference that is generating the error from your project. From the Windows Start menu, point to Programs, point to Microsoft Visual Studio 2008, point to Visual Studio Tools, and then click Visual Studio 2008 Command Prompt. Move to the directory where you want to place your assembly wrapper. Type the following code. tlbimp /out: /keyfile: An example of the code you might enter would be the following. tlbimp c:\windows\system32\msi.dll /out:Interop.WindowsInstaller.dll /keyfile:"c:\documents and settings\mykey.snk" Use double quotation marks (") if a path or file contains spaces. In Visual Studio, add a .NET Assembly reference to the file you just created.
Visual Basic .Net Compiler Messages
Comments
 
 BC31024  -  Unable to create a .NET Runtime interface: <error>  MICROSOFT
There was an internal compiler error creating an interface, or a method call on an interface failed.
Save your work and restart Visual Studio. If the error recurs, reinstall Visual Studio. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC31508  -  Cannot find .NET Framework directory: <error>  MICROSOFT
The directory where the .NET Framework assemblies are stored could not be located.
Compile the program again to see if the error recurs. If the error continues, save your work and restart Visual Studio. If the error recurs, reinstall Visual Basic. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC31098  -  Class '' cannot be found  MICROSOFT
Error Message Class '' cannot be found. This condition is usually the result of a mismatched 'Microsoft.VisualBasic.dll'. A defined member could not be located.
Compile the program again to see if the error recurs. If the error recurs, save your work and restart Visual Studio. If the error persists, reinstall Visual Basic. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC31097  -  Member '' cannot be found in class ''  MICROSOFT
Error Message Member '' cannot be found in class ''. This condition is usually the result of a mismatched 'Microsoft.VisualBasic.dll'. A defined member could not be located.
Compile the program again to see if the error recurs. If the error recurs, save your work and restart Visual Studio. If the error persists, reinstall Visual Basic. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC36810  -  Errors occurred while compiling the XML schemas in the project  MICROSOFT
Error Message Errors occurred while compiling the XML schemas in the project. Because of this, XML IntelliSense is not available. There is an error in an XML Schema Definition (XSD) schema included in the project. This error occurs when you add an XSD schema (.xsd) file that conflicts with the existing XSD schema set for the project.
Double-click the warning in the Errors List window. Visual Basic will take you to the location in the XSD file that is the source of the warning. Correct the error in the XSD schema. Ensure that all required XSD schema (.xsd) files are included in the project. You may need to click Show All Files on the Project menu to see your .xsd files in Solution Explorer. Right-click an .xsd file and then click Include In Project to include the file in your project. If you are using the XML to Schema Wizard, this error can occur if you infer schemas more than one time from the same source. In this case, you can remove the existing XSD schema files from the project, add a new XML to Schema item template, and then provide the XML to Schema Wizard with all the applicable XML sources for your project. If no error is identified in your XSD schema, the XML compiler may not have enough information to provide a detailed error message. You may be able to get more detailed error information if you ensure that the XML namespaces for the .xsd files included in your project match the XML namespaces identified for the XML Schema set in Visual Studio. For information about how to specify an XML schema for the Visual Studio XML Schema set, see How to: Select the XML Schema(s) to Use for Validation.
Visual Basic .Net Compiler Messages
Comments
 
 BC30140  -  Error creating assembly manifest: <error message>  MICROSOFT
The Visual Basic compiler calls the Assembly Linker (Al.exe, also known as Alink) to generate an assembly with a manifest. The linker has reported an error in the pre-emission stage of creating the assembly. This can occur if there are problems with the key file or the key container specified. To fully sign an assembly, you must provide a valid key file that contains information about the public and private keys. To delay sign an assembly, you must select the Delay sign only check box and provide a valid key file that contains information about the public key information. The private key is not necessary when an assembly is delay-signed. For more information, see How to: Sign an Assembly (Visual Studio).
Examine the quoted error message and consult the topic Al.exe Tool Errors and Warnings for error AL1019 further explanation and advice If the error persists, gather information about the circumstances and notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC31520  -  Unable to apply security attribute(s) to '': <error>  MICROSOFT
There was an error when applying security attributes. This could be a result of using a security attributes incorrectly or it could indicate a problem with the compiler.
Verify that the syntax and arguments for the attribute. Compile the program again to see if the error reoccurs. If the error continues, save your work and restart Visual Studio. If the error reoccurs, reinstall Visual Basic. If the error persists after reinstallation, notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC30747  -  Internal compiler error  MICROSOFT
An internal error occurred during expression evaluation.
Restart Visual Studio.
Visual Basic .Net Compiler Messages
Comments
 
 

 
Visual Basic .Net Compiler Messages (16)
 
  Prev   1  2  Next