O
Oenone
I am currently in the process of upgrading my VB.NET applications and DLLs
from VS2003 to VS2005. Everything seems to be going fine, but I've had a
couple of warnings that I don't understand.
In one of my DLLs I define a MustInherit base class with various properties
and methods. In another DLL I inherit from that class to create a custom
derived class. I am getting the following warning in the IDE:
'DerivedClass' is not CLS-compliant because it derives from 'BaseClass',
which is not CLS-compliant.
No warnings are displayed at all for BaseClass. How can I determine what
exactly is it about BaseClass that stops it from being CLS-compliant?
For reference, I have Option strict On for the base class, and within its My
Project settings, I have all of the Compile Conditions set to either Error
or Warn except for "Use of variable prior to assignment" and
"Function/Operator without return value". Could it be one of these that is
causing the non-CLS-compliance issues to occur?
Many thanks,
from VS2003 to VS2005. Everything seems to be going fine, but I've had a
couple of warnings that I don't understand.
In one of my DLLs I define a MustInherit base class with various properties
and methods. In another DLL I inherit from that class to create a custom
derived class. I am getting the following warning in the IDE:
'DerivedClass' is not CLS-compliant because it derives from 'BaseClass',
which is not CLS-compliant.
No warnings are displayed at all for BaseClass. How can I determine what
exactly is it about BaseClass that stops it from being CLS-compliant?
For reference, I have Option strict On for the base class, and within its My
Project settings, I have all of the Compile Conditions set to either Error
or Warn except for "Use of variable prior to assignment" and
"Function/Operator without return value". Could it be one of these that is
causing the non-CLS-compliance issues to occur?
Many thanks,