Hi Bonnie,

I did want to hear what others are doing in the real world, and what you say makes perfect sense.

If you don't mind two more question about the implementation.

I've done a couple of experiments with creating a separate project for the business object. Then what I did in the solution explorer of VS was add the BO projects to the main project. Then when testing by running the app, F5, it takes a longer period of time to get things running then if everything is just under under one project. With too many projects it could take a while.

Is this a poor way to do this - perhaps compile to a .dll instead and then reference, or is there something that can be set somewhere to speed things up? How do you bring these other projects into your main project?

Thank you,
John


>John,
>
>We typically break up our biz classes (and the projects for these) along business lines and functionality. I write software for fire departments, so I'll have a biz class/project for each of these: Incidents, Personnel, Apparatus, Buildings, Inspections, Training, etc. etc.
>
>The biz objects are designed to be front-end ambivalent ... what I mean by that is that can be used by either a Winform or a Webform on the client-side.
>
>~~Bonnie
>
>
>
>>There are recent discussions involving Business Objects and I wanted to ask a question as I'm relatively new.
>>
>>Should a separate project be created for every business object created? In other words to support re-usability between different projects such as winforms and webforms does it make sense to have the different objects in different projects?
>>
>>To sum it up what is the best practice for creating re-usable business objects.