namespace conventions

[Flip]

In java, it is recommended using a package naming convention of your domain
name (or something similar). For example com.mycompany.screenscrapper. Is
there a similar type of convention suggested for namespaces in c#/.net?

Thanks.

 

[Nicholas Paldino [.NET/C# MVP]]

Flip,

I don't believe there is a convention for namespace naming, other than
the fact that it should be Pascal named. However, having a company
identifier, then going down based on smaller and smaller categories is not a
bad idea. If you prefix with your company name (I don't think the com part
is necessary, really), then when you create your own Windows.Forms package,
it won't be misconstrued somewhere else.

Hope this helps.

 

[Mythran]

Our namespaces go something like the following:

CompanyName.SolutionType.SolutionName

CompanyName.SolutionType.SolutionName.ProjectName

with the exception of WebControls where the SolutionName of the webcontrol is the
same as the project name (IE: MyCompany.WebControls.DatePicker.DatePicker
wouldn't look so good, so it's ns is just MyCompany.WebControls.DatePicker. The
DatePicker has a sample application which falls under
MyCompany.WebControls.DatePicker.DatePickerSample).

Diff SolutionType types:
Applications
Libraries
WebControls
Controls

Hope this helps...

Mythran

 

[Flip]

WOW! That was fast! :> Thank you both Nicholas and Mythran! Both of your
postings shed some light on conventions/recommendations. I always wondered
about the "com." part if everyone is doing it, uh, why do it? :>

Thanks again! :>

 

[Jay B. Harlow [MVP - Outlook]]

Flip,
In addition to the other comments.

The "Design Guidelines for Class Library Developers"
http://msdn.microsoft.com/library/d...ef/html/cpconNETFrameworkDesignGuidelines.asp
Covers Namespace naming conventions:

http://msdn.microsoft.com/library/d...enref/html/cpconNamespaceNamingGuidelines.asp

Hope this helps
Jay

 

[Flip]

Thank you Jay. I'll take a look at these links over lunch! :>