Project/Class Library/DLL with different namespace?

[sameaname]

Hi
We have the below 6 class libraries in our ASP.NET project


1. Application.UI - //Contains all the aspx and UI control, css/ images web.config etc. (assembly name : Project.Application.UI)
2. Controls,UI - //Contains all custom build user controls. (assembly name : Project.Controls.UI)
3. BusinessLogic // Contains all the business logic data/ complex business objects (assembly name : Project.BusinessLogic)
4. DataObjects //Contains objects that represent database fields. (assembly name : Project.DataObjects)
5. DataAccess // SQL data access components (assembly name : Project.DataAccess)
6. Utilities// Contains helper classes with help functions (assembly name : Project.Utilities)

Recently someone decided to move some of Data Objects classes to Business Logic but leave the namespace unchanged. For example in the BusinessLogic library (Project.BusinessLogic) now contains classes with namespaces - Project.DataObjects. Is this a good approach? What are the consequences of this?
Please note: We also have intention to use security code analysis tools (CAT.NET) and csProductBuild for the build process.

Please help.
Regards,
raj

[sameaname]

I have two options to setup ASP.NET web application. Please can anyone tell me which one is better than the other one and why?

Option A

1. Application.UI - //Contains all the aspx and UI control, css/ images web.config etc. (assembly name : Project.Application.UI)
2. Controls,UI - //Contains all custom build user controls. (assembly name : Project.Controls.UI)
3. BusinessLogic // Contains all the business logic data/ complex business objects (assembly name : Project.BusinessLogic)
4. DataObjects //Contains objects that represent database fields using properties. (assembly name : Project.DataObjects)
5. DataAccess // SQL data access components (assembly name : Project.DataAccess)
6. Utilities // Contains helper classes with help functions (assembly name : Project.Utilities)



Option B
1. Application.UI - //Contains all the aspx and UI control, css/ images web.config etc. (assembly name : Project.Application.UI)
2. Controls,UI - //Contains all custom build user controls. (assembly name : Project.Controls.UI)
3. BusinessLogic // Contains all the business logic data/ complex business objects. Also contains objects that represent database fields using properties (assembly name : Project.BusinessLogic)
4. DataAccess // SQL data access components (assembly name : Project.DataAccess)
5. Utilities // Contains helper classes with help functions (assembly name : Project.Utilities)

You see the only difference is the Business Logic. Which one you prefer and why would you recommend it?

Note : All assemblies are contained in a one web server.

[Bassem]

I think there is no change except you have to reference the namespace you use classes from.
example: if N1.A uses N1.B, but B moved to N2, Now you have to reference N2; using N2; then use B.

Another thing are there classes declared to be internal in DataObject namespace, So they have to be in the same assembly to be visible.

That was a thought maybe right maybe wrong.
Regards,

[Frinavale]

Are you having a problem with this or are you just asking us our opinions on your design changes?

As Bassem has stated there is no problem with doing this, you simply change your references to the DLL to access Objects...

What you've done is a matter of style and organization preferences. There is nothing "wrong" with what you've done and it's up to you to decide whether it's good or bad design according to how things fit into your particular application.