|
| DAL and BLL as separate class libraries: Naming convention? |
 |
Thu, 3 Apr 2008 00:25:15 +0000 |
If I create an asp.net 2.0 application named, let's say, MyApp, and I create
separate class library projects for the DAL and BLL, how should I name those
projects? Is there some kind of naming convention?
E.g., MyAppDAL and MyAppBLL?
|
| Post Reply
|
| Re: DAL and BLL as separate class libraries: Naming convention? |
 |
Thu, 3 Apr 2008 00:50:48 +0000 |
I usually use the following format for Namespaces :
MyCompany.ApplicationName.BLL (for Business classes)
MyCompany.ApplicationName.DAL(for DAL classes)
OR you can Ignore the Company Name ...
Hope it helps
|
| Post Reply
|
| Re: DAL and BLL as separate class libraries: Naming convention? |
 |
Thu, 3 Apr 2008 00:59:38 +0000 |
I see that. But what I mean is, what do you name the actual class library
project for DAL (and for the BLL)?
|
| Post Reply
|
| Re: DAL and BLL as separate class libraries: Naming convention? |
 |
Thu, 3 Apr 2008 01:02:34 +0000 |
MyAppDAL and MyAppBLL are fine. Names should be clear and concise.
If you were developing a Winforms application you would need a long namespace
but when developing for a Webforms - keep it simple!
|
| Post Reply
|
| Re: DAL and BLL as separate class libraries: Naming convention? |
 |
Thu, 3 Apr 2008 01:29:36 +0000 |
Where do I put the projects?
I have a folder MyApp which is my website folder which contains my aspx pages,
web.config, etc. Do I just create the project folders as sub-folder of this
folder? Or do I keep the class libraries outside of the web folder?
E.g.:
MyApp
- MyAppDAL
- Customer.cs
- MyAppBLL
- Customer.cs
- default.aspx
- web.config
Or do I do this:
MyAppDAL
- Customer.cs
MyAppBLL
- Customer.cs
MyApp - default.aspx
- web.config
|
| Post Reply
|
|
|
|
|
|
|
|
|
|