Function procedure is marked as
<CLSCompliant(True)> but returns a type that is marked as
<CLSCompliant(False)>, is not marked, or does not qualify because it is a noncompliant type.
For a procedure to be compliant with the Language Independence and Language-Independent Components (CLS), it must use only CLS-compliant types. This applies to the types of the parameters, the return type, and the types of all its local variables.
The following Visual Basic data types are not CLS-compliant:
When you apply the CLSCompliantAttribute to a programming element, you set the attribute's
isCompliant parameter to either
False to indicate compliance or noncompliance. There is no default for this parameter, and you must supply a value.
If you do not apply the CLSCompliantAttribute to an element, it is considered to be noncompliant.
By default, this message is a warning. For information on hiding warnings or treating warnings as errors, see Configuring Warnings in Visual Basic.
Error ID: BC40027
To correct this error
Functionprocedure must return this particular type, remove the CLSCompliantAttribute. The procedure cannot be CLS-compliant.
Functionprocedure must be CLS-compliant, change the return type to the closest CLS-compliant type. For example, in place of
UIntegeryou might be able to use
Integerif you do not need the value range above 2,147,483,647. If you do need the extended range, you can replace
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,
intis often 16 bits in other environments. If you are returning a 16-bit integer to such a component, declare it as
Integerin your managed Visual Basic code.