cls-compliant

I was wondering which edge cases exist that could make Common Language Specification compliance acceptable. Even when not intending to be accessed from other languages, I think that the tenets asserted by the CLSCompliantAttribute are good best practices. Do you have encountered / know of cases where YAGNI outweighs the best practices? Jason Short "[sic] What use is there for being CLS compliant?" Medium trust , ClickOnce , running from a shared network drive, guest profiles in a domain setting, etc. There are lots of security situations where your code cannot run if you break the CLS

I am currently testing out Ndepend, and it gives me a warning that assemblies should be marked as CLSCompliant. Our project is all C#, so it is not really needed. What I am wondering is: are there any negative effects of marking a dll as clscompliant or should I just disable the warning? Note I am not asking what CLSCompliant means that is covered here: What is the 'CLSCompliant' attribute in .NET? This is one of those subtle cases... CLS compliance is probably of most importance to library authors, who can't control who the caller is. In your case, you state "our project is all C#", in which

This new feature is really convenient. Lately I read the document of the "Microsoft All-In-One Code Framework", and it mentions that "Optional Parameters" is not CLS-Compliant. So I tested it by using "Optional Parameters" in a public API, and turned on FxCop, then I compiled and FxCop did not complain about anything. At the mean while, FxCop did report a warning when I add an API that has uint as its return type. So now I am confused, is "Optional Parameters" CLS-Compliant or not? And what's the best way to find out whether a new language feature is CLS-Compliant or not? Optional arguments

This really baffles me. I've tried removing the readonly, changing names.. What am I doing wrong here? public abstract class CatalogBase<T> where T : class { protected readonly String DataPath; protected readonly XmlSerializer Serializer; private readonly XmlSerializerNamespaces _namespaces; protected CatalogBase(String dataPath) { DataPath = dataPath; Serializer = new XmlSerializer(typeof (T)); _namespaces = new XmlSerializerNamespaces(); _namespaces.Add(String.Empty, String.Empty); } public virtual void Write(T obj) { var streamWriter = new StreamWriter(DataPath); Serializer.Serialize