Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Visual Basic .Net Compiler Messages  [ 1000 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
 
 BC30830  -  'Line' statements are no longer supported (Visual Basic Compiler Error)  MICROSOFT
Line statements are no longer supported. File I/O functionality is available as Microsoft.VisualBasic.FileSystem.LineInput and graphics functionality is available as System.Drawing.Graphics.DrawLine.
If performing file access, use Microsoft.VisualBasic.FileSystem.LineInput. If performing graphics, use System.Drawing.Graphics.Drawline.
Visual Basic .Net Compiler Messages
Comments
 
  Use a variable of a type recognized by Visual Basic. -or- If you encounter this error whil -  Variable uses an Automation type not supported in Visual Basic  MICROSOFT
You tried to use a variable defined in a type library or object library that has a data type not supported by Visual Basic.
Visual Basic .Net Compiler Messages
Comments
 
 BC30766  -  '' is not declared (Smart Device/Visual Basic Compiler Error)  MICROSOFT
is not declared. File I/O functionality is normally available in the Microsoft.VisualBasic namespace, but the targeted version of the .NET Compact Framework does not support it.
Perform file operations with functions defined in the System.IO namespace.
Visual Basic .Net Compiler Messages
Comments
 
 BC30011  -  Internal compiler error: code generator received malformed input  MICROSOFT
The Visual Basic compiler cannot successfully interpret one of its internally written files.
Compile the program again to see if the error recurs. If the error recurs, reinstall the Visual Basic compiler. If the error persists after reinstallation, gather information about the circumstances and notify Microsoft Product Support Services.
Visual Basic .Net Compiler Messages
Comments
 
 BC30815  -  '' is not declared (Visual Basic Error)  MICROSOFT
Error Message '' is not declared. File I/O functionality is available in the Microsoft.VisualBasic namespace.
Use the file I/O functions defined in My.Computer.FileSystem, the System.IO namespace, Visual Basic run-time functions, or the Microsoft.VisualBasic.FileSystem object.
Visual Basic .Net Compiler Messages
Comments
 
 BC40025  -  Type of member '' is not CLS-compliant  MICROSOFT
The data type specified for this member is not part of the Common Language Specification (CLS). This is not an error within your component, because the .NET Framework and Visual Basic support this data type. However, another component written in strictly CLS-compliant code might not support this data type. Such a component might not be able to interact successfully with your component. The following Visual Basic data types are not CLS-compliant: SByte Data Type (Visual Basic) UInteger Data Type ULong Data Type (Visual Basic) UShort Data Type (Visual Basic) By default, this message is a warning. For more information on hiding warnings or treating warnings as errors, see Configuring Warnings in Visual Basic.
If your component interfaces only with other .NET Framework components, or does not interface with any other components, you do not need to change anything. If you are interfacing with a component not written for the .NET Framework, you might be able to determine, either through reflection or from documentation, whether it supports this data type. If it does, you do not need to change anything. If you are interfacing with a component that does not support this data type, you must replace it with the closest CLS-compliant type. For example, in place of UInteger you might be able to use Integer if you do not need the value range above 2,147,483,647. If you do need the extended range, you can replace UInteger with Long. If you are interfacing with Automation or COM objects, keep in mind that some types have different data widths than in the .NET Framework. For example, uint is often 16 bits in other environments. If you are passing a 16-bit argument to such a component, declare it as UShort instead of UInteger in your managed Visual Basic code.
Visual Basic .Net Compiler Messages
Comments
 
 BC40032  -  Underlying type of Enum is not CLS-compliant  MICROSOFT
The data type specified for this enumeration is not part of the Common Language Specification (CLS). This is not an error within your component, because the .NET Framework and Visual Basic support this data type. However, another component written in strictly CLS-compliant code might not support this data type. Such a component might not be able to interact successfully with your component. The following Visual Basic data types are not CLS-compliant: SByte Data Type (Visual Basic) UInteger Data Type ULong Data Type (Visual Basic) UShort Data Type (Visual Basic) By default, this message is a warning. For more information on hiding warnings or treating warnings as errors, see Configuring Warnings in Visual Basic.
If your component interfaces only with other .NET Framework components, or does not interface with any other components, you do not need to change anything. If you are interfacing with a component not written for the .NET Framework, you might be able to determine, either through reflection or from documentation, whether it supports this data type. If it does, you do not need to change anything. If you are interfacing with a component that does not support this data type, you must replace it with the closest CLS-compliant type. For example, in place of UInteger you might be able to use Integer if you do not need the value range above 2,147,483,647. If you do need the extended range, you can replace UInteger with Long. If you are interfacing with Automation or COM objects, keep in mind that some types have different data widths than in the .NET Framework. For example, uint is often 16 bits in other environments. If you are passing a 16-bit argument to such a component, declare it as UShort instead of UInteger in your managed Visual Basic code.
Visual Basic .Net Compiler Messages
Comments
 
 BC32087  -  Overload resolution failed because no accessible '' accepts this number of type arguments  MICROSOFT
A call to an overloaded generic procedure cannot be resolved because the compiler cannot access any overloaded version with the appropriate number of type parameters. When you call a generic procedure, you must supply one type argument for each type parameter. Alternatively, you can supply no type arguments at all and let the compiler attempt to do type inference. For more information, see "Type Inference" in Generic Procedures in Visual Basic.
Ensure that the version you intend to call is accessible by the calling code. See Access Levels in Visual Basic. Add or remove type arguments from your calling code so that the type argument list matches the type parameter list of the version you intend to call. -or- Remove all type arguments from your calling code and let the compiler attempt to do type inference. Be aware that type inference can fail if there are conflicts or ambiguities.
Visual Basic .Net Compiler Messages
Comments
 
 

 
Visual Basic .Net Compiler Messages (1000)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next