Non_CLS compliant variables?

[GB]

Hi,

I just upgraded from VS2003 to VS2005 (VB.NET apps) an I get a number of
warnings "Name "..." is not CLS_Compliant". All the corresponding "faulty"
code is in DataSet1.Designer.vb, wich is automatically generated code
associated to some of my Data Adapters at design time. So I feel I should
not touch this code myself.

In fact, all mentionned names are derived from some of my field names in the
records. There is an underscore added in front of the names. Eg : if my
field name is ABC_01, the Designe.vb code would mention a "_ABC_01" name.

How can I have these warnings fixed? Should I change my field naming
conventions in order to avoid this? Where can I find the "CLS-compliant"
rules?

Thanks in advance.

GB

[GB]

OK. Dont bother. I suppressed the faulty Table in a DataSet, then reinserted
it ans so it regenerated the code, ths time correctly. So the porblem is
solved.

GB

"GB" <fo****@bessis.com> a écrit dans le message de news:
eB***************@TK2MSFTNGP15.phx.gbl...

Hi,

I just upgraded from VS2003 to VS2005 (VB.NET apps) an I get a number of
warnings "Name "..." is not CLS_Compliant". All the corresponding "faulty"
code is in DataSet1.Designer.vb, wich is automatically generated code
associated to some of my Data Adapters at design time. So I feel I should
not touch this code myself.

In fact, all mentionned names are derived from some of my field names in
the records. There is an underscore added in front of the names. Eg : if
my field name is ABC_01, the Designe.vb code would mention a "_ABC_01"
name.

How can I have these warnings fixed? Should I change my field naming
conventions in order to avoid this? Where can I find the "CLS-compliant"
rules?

Thanks in advance.

GB