cls-compliant

When compiling my solution, I get several warnings of the following: warning CS3016: Arrays as attribute arguments is not CLS-compliant No other information on what type is not compliant is given. In my projects I have some attributes that take params array arguments in their constructors, but they are all internal, and that shouldn't affect CLS-compliance. Why is this warning being given, and what type is it being given on? CS3016 . If you have an attribute which takes an array as argument and the project is marked as CLSCompliant you will get this warning. Brent I ran into this today. I had

I am currently reading Albahari 's C# 3.0 in a Nutshell and on pg. 241, whilst talking about Array indexing, he says this: Nonzero-based arrays are not CLS (Common Language Specification)-compliant What does it mean exactly, for nonzero arrays to not be CLS compliant ? And what implications does it have on your code? [Update] Here is a link to the page of the book. The CLS (Common Language Specification) lays the groundwork for a common set of rules for compliance that guarantees that other languages (VB.NET, F#, etc.) can use assemblies that you have built with C#. A nonzero-based array would

What is the CIL , CTS , and CLS in .NET and what is the difference between them? CIL (Common Intermediate Language) is the byte code to which your C# or Visual Basic code is compiled. It's the "machine code" of the .NET execution engine. The CTS (Common Type System) is the representation of types (classes and structures) at the compiled level. Basically, it's saying that all .NET languages will use a common way of representing types (classes and structures). The CLS (Common Language Specification) is a set of constraints on APIs and a complementary set of requirements on languages. If a

Can anyone explain the following behavior? In summary, if you create multiple CLS compliant libraries in Visual Studio 2008 and have them share a common namespace root, a library referencing another library will require references to that library's references even though it doesn't consume them. It's pretty difficult to explain in a single sentence, but here are steps to reproduce the behavior (pay close attention to the namespaces): Create a library called LibraryA and add a a single class to that library: namespace Ploeh { public abstract class Class1InLibraryA { } } Make sure that the

What is the CLSCompliant attribute? You mark classes with the CLSCompliant attribute when you want to make sure it can be used by any other .NET language. These are the basic rules: Unsigned types should not be part of the public interface of the class. What this means is public fields should not have unsigned types like uint or ulong, public methods should not return unsigned types, parameters passed to public function should not have unsigned types. However unsigned types can be part of private members. Unsafe types like pointers should not be used with public members. However they can be

Why do I get the compiler warning Identifier 'Logic.DomainObjectBase._isNew' is not CLS-compliant for the following code? public abstract class DomainObjectBase { protected bool _isNew; } From the Common Language Specification : CLS-compliant language compilers must follow the rules of Annex 7 of Technical Report 15 of the Unicode Standard 3.0, which governs the set of characters that can start and be included in identifiers. This standard is available from the Web site of the Unicode Consortium. If you look this up : That is, the first character of an identifier can be an uppercase letter,