«

I have read the MS docs on namespacing but I am still a little unclear.

Should I use:

Acme.Web.OrderFullfillment
Acme.OrderFullfillment.Data

OR

Acme.OrderFullfillment.Web
Acme.OrderFullfillment.Data

The latter seems right but are dependencies across sibling namespace okay??

KC

I agree that the latter seems right...and I believe that cross-sibling
depedency is ok.

Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/


"KC" <> wrote in message
news:...
> I have read the MS docs on namespacing but I am still a little unclear.
>
> Should I use:
>
> Acme.Web.OrderFullfillment
> Acme.OrderFullfillment.Data
>
> OR
>
> Acme.OrderFullfillment.Web
> Acme.OrderFullfillment.Data
>
> The latter seems right but are dependencies across sibling namespace
okay??
>
> KC
>
>

Overall, the later is best, if you are aiming for:

CompanyName.Appliction.Division.Subdivision

I am not sure I agree with .web in an app, as you are simply dealing with a
UI type, but it is a valid way of organization, if separating out UIs is one
means of dividing out your application.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"KC" wrote:

> I have read the MS docs on namespacing but I am still a little unclear.
>
> Should I use:
>
> Acme.Web.OrderFullfillment
> Acme.OrderFullfillment.Data
>
> OR
>
> Acme.OrderFullfillment.Web
> Acme.OrderFullfillment.Data
>
> The latter seems right but are dependencies across sibling namespace okay??
>
> KC
>
>
>