Non_CLS compliant variables?

  • Thread starter Thread starter GB
  • Start date Start date
G

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
 
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

CLS compliant names 3
is NOT CLS-Compliant warning in VS2005? 2
Type of member ... is not CLS-compliant 1
Warning Msg: Name '_ClassColumn' is not CLS-compliant. 10
Private Member Variable Naming Convention 4
VS2005: non CLS-compliant classes 4
Not CLS-compliant warning... 3
CLS Compliance 5

Back
Top