Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > General .NET
|
General .NET For general discussion of MICROSOFT .NET topics that don't fall within any of the other .NET forum subcategories or .NET language forums.  If your question is specific to a language (C# or Visual Basic) or type of application (Windows Forms or ASP.Net) try an applicable forum category. ** PLEASE BE SPECIFIC WITH YOUR QUESTION ** When posting here, provide details regarding the Microsoft .NET language you are using and/or what type of application (Windows/Web Forms, etc) you are working in, if applicable to the question. This will help others answer the question without having to ask.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the General .NET section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 1st, 2007, 11:36 AM
Authorized User
 
Join Date: Jul 2007
Posts: 20
Thanks: 0
Thanked 0 Times in 0 Posts
Default Namespace Naming Conventions For Layerd Applicatio

I am creating a website for an organsation.

I choose the Layered Application Method as Imar did in his very famous article.

But as I have a huge system in which Many departments and there services are present. Then we also have the controls, webpages, etc.

So I need an standard which will help me in this regard.

Any article or comments are welcome for this purpose.

Thanks.

 
Old September 1st, 2007, 01:57 PM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

I follow the Microsoft suggestions which are more of less something like this:

<CompanyName>.<Technology>.<Application>

You can layer in as much as you need to satisfy your needs. For example:

MyCompany.SomeDepartment.SomeApplication.Web
MyCompany.SomeDepartment.SomeApplication.BOL
MyCompany.SomeDepartment.SomeApplication.BLL
MyCompany.SomeDepartment.SomeApplication.DAL

-Peter
 
Old September 1st, 2007, 02:03 PM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Yeah, in my articles I recommend something similar:

<CompanyName>.<ProjectName>.<Layer>

So, following the articles:

Spaanjaars.ContactManager.Web
Spaanjaars.ContactManager.Dal

Since namespaces are nothing more than names that you can make up yourself, you're free to choose whatever you want.

However, don't overdo things. For example, if both the sales department and the marketing department can access your Intranet, you probably can get away with CompanyName.Intranet.Web instead of creating specialized namespaces for each department.

However, it depends on the application you are building. The more specialized classes you have, the more specialized namespaces you may need.

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004





Similar Threads
Thread Thread Starter Forum Replies Last Post
Why TopMost make form at The top of all applicatio imaginator C# 1 March 7th, 2008 03:47 PM
Having problem share the data between 2 Applicatio prashant.borude BOOK: Beginning SharePoint 2007: Building Team Solutions with MOSS 2007 ISBN: 978-0-470-12449-9 0 September 24th, 2007 04:25 AM
Variables in the four naming conventions FJInfante SQL Server 2000 3 May 1st, 2006 01:06 PM
Code Writing Conventions richard.york PHP FAQs 0 April 5th, 2004 08:23 PM
Naming conventions jara VS.NET 2002/2003 3 June 22nd, 2003 04:21 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.