Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Studio:Visual Basic .Net Compiler Messages  [ 27 result(s) ]
MICROSOFT 
 BC30753  -  Option Strict On disallows implicit conversions from '' to ''; the Visual Basic 6.0 collection type is not compatible with the .NET Framework collection type  MICROSOFT
Option Strict On disallows implicit conversions from '' to ''; the Visual Basic 6.0 collection type is not compatible with the .NET Framework collection type. The collection object that is used in Visual Basic 6.0 differs from the collection object that is used in Visual Studio 2008.
Explicitly convert collection objects by using one of the type conversion keywords. The CType Function and DirectCast keywords throw a run-time exception if the conversion fails. The TryCast keyword returns Nothing (Visual Basic) if the conversion fails.
Visual Basic .Net Compiler Messages
Comments
 
 BC31021  -  Visual Basic compiler is unable to recover from the following error:  MICROSOFT
The Visual Basic compiler is unable to recover from the following 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:  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
 
 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
 
 BC31508  -  Cannot find .NET Framework directory:  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
 
 BC30655  -  Unable to find required file ''  MICROSOFT
A file that is required by Visual Studio is missing or damaged.
Reinstall Visual Studio.
Visual Basic .Net Compiler Messages
Comments
 
 BC30698  -  Unable to write temporary file because temporary path is not available  MICROSOFT
Visual Basic could not determine the path where temporary files are stored.
Restart Visual Studio. If the problem persists, reinstall Visual Studio.
Visual Basic .Net Compiler Messages
Comments
 
 BC31024  -  Unable to create a .NET Runtime interface:  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
 
 BC30140  -  Error creating assembly manifest:  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
 
 

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