 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / July 2006Current naming convention of abstract classes - BaseFoo vs. FooBase?
This is probably a question for someone at MS, although I haven't found anything in FxCop or definitive in the newsgroups regarding this, but what is the current, if any, naming standard regarding base classes? A lot of the older classes are Base<classname> (i.e BaseValidator), and some newer ones - and these may be particular to ASP.Net 2 - follow the <classname>Base pattern (i.e. ProviderBase). Is there a definitive direction the standards are going on this (very minute) naming convention? > This is probably a question for someone at MS, although I haven't found > anything in FxCop or definitive in the newsgroups regarding this, but what [quoted text clipped - 3 lines] > pattern (i.e. ProviderBase). Is there a definitive direction the standards > are going on this (very minute) naming convention? Someone with <http://www.amazon.com/gp/product/0321246756> might be able to answer this. Or you could always get it yourself :) -- Larry Lard Replies to group please When starting a new topic, please mention which version of VB/C# you are using I bought it, and it has no mention of naming abstract classes. There's about a page dedicated to them, and it's basically about their constructors. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.