Argument type <> is not CLS compliant

[Davaris]

I'm using Wintellect's Power Collections for .NET

 

http://powercollections.codeplex.com/releases/view/6863

 

and am getting warning messages like:

 

Argument type 'Leadwerks.Vector3' is not CLS compliant

 

whenever I declare a Leadwerks type.

 

I found the cause is this line in Wintellect's algorithms file:

 

// Everything should be CLS compliant.
[assembly: CLSCompliant(true)]

 

Does anyone know what the problem is? Is it an issue with Leadwerks itself, or is it the C# wrapper?

[TylerH]

http://www.devarticles.com/c/a/C-Sharp/Making-Your-Code-CLS-Compliant/

 

The Vector classes contain overloaded operators, which are not CLS Compliant.

[Davaris]

From what I have read, you can mark parts of the code to be non compliant. I don't know if it can still be used with these collections though.

 

http://www.devarticles.com/c/a/C-Sharp/Making-Your-Code-CLS-Compliant/

 

 

You can apply the CLSCompliant attribute on an assembly (or a program element) and have the compiler check if your code is CLS (Common Language System) compliant. This means it works properly when consumed by other .NET languages. For example, you can place the following attribute on your .NET AssemblyInfo.cs files:

 

[assembly: CLSCompliant(true)]

 

 

Some of the things the compiler checks:

 

Class and member names cannot differ only by case. For example, you can't have one property named Counter and another named counter. This is important for cross-language compatibility since VB .NET isn't case sensitive.

 

Overloaded class methods cannot differ only by out or ref parameter designations.

 

Publicly exposed members cannot start with an underscore ( _ ).

 

Operators can't be overloaded

 

Unsigned types can't be part of the public interface of a class

 

Unfortunately, although you can apply the CLSCompliant attribute in VB .NET, the VB .NET compiler doesn't check for CLS compliance. In VB.NET 2005, this has apparently been fixed.