Old Forums
Search:
Technical support This forum is closed.
Version 1.x > Technical support > Identifiers are not CLS Compliant View modes: 
User avatar
Member
Member
wtijsma - 1/3/2005 4:12:09 PM
   
Identifiers are not CLS Compliant
Hi,

if you have an identifier with access level higher than private (protected etc), it may not start with an underscore (_), or the Assembly can't use the [assembly : CLSCompliant(true)] attribute.
User avatar
Member
Member
wtijsma - 1/3/2005 4:14:53 PM
   
Re: Identifiers are not CLS Compliant
Also just differing in case isn't enough (and impossible by the way in VB.NET) either, so I would recommend prefixing private and protected variables with an F (or whatever get's you on ;-)

User avatar
Member
Member
wtijsma - 1/3/2005 4:27:07 PM
   
Re: Identifiers are not CLS Compliant
Ah I see in other places you used the 'm'-prefix...

User avatar
Guest
admin - 1/4/2005 11:31:36 AM
   
Re: Identifiers are not CLS Compliant
Hi Wiebe,

you're probably talking about the default.aspx page classes. This issue was originally caused by VS.NET that automatically uses _default class name for the default.aspx page :( We will try to rename the class and if it works, we will fix this in the nearest version so that we do not use the [assembly : CLSCompliant(true)] attribute.

User avatar
Member
Member
wtijsma - 1/4/2005 12:28:30 PM
   
Re: Identifiers are not CLS Compliant
No, there was a _treeProvider property in the ContentProvider class...

User avatar
Member
Member
wtijsma - 1/4/2005 12:29:43 PM
   
Re: Identifiers are not CLS Compliant
Also, with the ASPX pages it doesn't matter, because they don't really have to be CLS Compliant (no other languages are going to inherit from them anyway...), but for the libraries it's pretty important...

User avatar
Guest
admin - 1/4/2005 2:19:26 PM
   
Re: Identifiers are not CLS Compliant
OK, we will try to solve it in version 1.4.

Top