>It's the way we have our source control system set up. Another project means more of pain with source control and more documentation.

Oh that's a good one Mike ... letting source control and documentation issues dictate application design. I think this is a first!! <g>

Why can't you just put the Dealerr class in the Common project?

~~Bonnie





>>>>>Another project structure question:
>>>>>
>>>>>I have a Common project which contains my custom classes and collections.
>>>>>
>>>>>I have a Biz project which contains by business helper classes. The Biz project contains a reference to the Common project.
>>>>>
>>>>>I have Order and OrderCollection classes in my Common project which will contain order data. I have another Dealer class that I want to lazy load into my Order class and expose as a property. I will be loading this dealer through my Biz project.
>>>>>
>>>>>I can't add a reference to my Biz project to my Common project because it will create a circular reference. How are other people doing this? In the application I inherited the container classes exist in the Biz layer, and I don't want to do this.
>>>>
>>>>You'll probably need to implement the Dealer class in a third project so that it can be referenced by both the Common and Biz projects.
>>>>
>>>>HTH,
>>>>Viv
>>>
>>>I think I need to rethink my structure. I really don't want to create a new project (I know it shouldn't be that big of a deal in a normal environment, but it is here). I have a few ideas I might try to run with.
>>
>>I'd be interested in other ways of solving this but I'm not aware of any....
>>OOC why would an additional DLL be a problem?
>>Best,
>>Viv
>
>It's the way we have our source control system set up. Another project means more of pain with source control and more documentation.