I put [assembly: CLSCompliant(true)] in my executable's
AssemblyInfo.cs file - and suddenly a library project it referenced
stopped compiling:
"... Referenced class ... has base class or interface
'System.Web.Services.Protocols.SoapHttpClientProto col' defined in
an assembly that is not referenced. You must add a reference to
assembly 'System.Web.Services'."
If I comment out the line, or change it to [assembly:
CLSCompliant(false)], the solution compiles again.
What's going on here? The only effect that I expect [assembly:
CLSCompliant(true)] to have on compilation is to catch use of
non-compliant features that aren't explicitly flagged ....
--
www.midnightbeach.com
