Inherited Form Compains of CLS non-Compliance

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have now whittled down my parent Form to nothing more than the simplest
Form with no objects on it of any type at all. When I inherit from it, the
subclassed form's Designer.vb file underlines the Partial Class declaration
with the message:

"Capitation form is not CLS-compliand because it is derived from ParentForm,
which is not CLS-compliant"

Why should a garden variety Windows Form - which is what my ParentForm is -
not be CLS-compliant.
TIA
Jav
 
Jav said:
I have now whittled down my parent Form to nothing more than the simplest
Form with no objects on it of any type at all. When I inherit from it,
the
subclassed form's Designer.vb file underlines the Partial Class
declaration
with the message:

"Capitation form is not CLS-compliand because it is derived from
ParentForm,
which is not CLS-compliant"

Why should a garden variety Windows Form - which is what my ParentForm
is -
not be CLS-compliant.
TIA
Jav
Click to expand...

I think that you will find that VB is regarded as inherently non-compliant
by default.
 
Back
Top