Making DLLs CLS Compliant

Updated June 5, 2006
Iron Speed Designer V4.0 and later

Common Language-specification (CLS) compliance generally refers to the claim that CLS rules and restrictions are being followed. Iron Speed Designer creates applications that are CLS compliant and meet these higher standards.

However, when integrating with other third-party controls such as Crystal Reports or other DLLs, you may receive a compiler error that the DLL is not CLS compliant. To fix this, you need to in effect set Iron Speed Designer’s compilation options to a lower standard so that non-CLS compliant DLLs can be integrated into an Iron Speed Designer application.

You can modify the AssemblyInfo.cs file to indicate that you do not want the C# compiler to check for CLS Compliance. To do that, specify:

[assembly: CLSCompliant(false)]

There may already be a line containing ‘true’ for CLS Compliance; change it to ‘false’.

For more information about CLS, see:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwritingcls-compliantcode.asp

Making DLLs CLS Compliant

See Also