>Hi Viv
>
>After reading your post, I realized that I was making things more complicated than they needed to be (I have a way of doing that) by putting the same dataset in more than one namespace.
>I put them all in the common namespace, removed them from all the others and now any method in the common namespace or in any project that references the common namespace can see them.
>
>Much, much simpler and cleaner now and no duplicated code needed.
>
>Thanks for the help.

You're welcome. I used to get into a real pickle with this in my early .net days. With an n-tier app it still pays to think carefully about which classes need to be 'common' to *all* assemblies - they should be kept to a minimum (enums etc.) so that the 'lower level' assemblies don't become cluttered with access to classes that they don't need to know about.

BTW it *is* possible for two assemblies to reference each other. The problem lies primarily with the VS build order so, in practice, it is still a real pain to support this scenario.

Best,
Viv