Yes I did mean the solution.

You nailed what I was talking about, now I understand very well what you are doing.

As far as the speed goes, if I had just one project in the solution things started up pretty quickly. When I added in two more projects it sometimes takes up to 15 - 20 seconds.

I'll keep exlporing this and thanks for your insight, it is much appreciated.





>John,
>
>>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?<
>
>When you speak of "main project", I assume you're talking about the solution?
>
>Our projects are already "in" the solution. We use source control to "share" things (DataAccess, DataSets and BizObjects) between Winform apps and Webform apps. So, say I have a Biz object called PersonnelBiz. I've created the project in my Winform app. Then, in the Webform piece of the app, I find I need a Personnel piece, so in Source Safe, I share the Personnel Biz project with the Webform solution ... which, in effect, creates another copy of the Personnel project under the Webform solution's "structure". But, in Source Safe, there's only one copy of the code.
>
>I don't know if it's a poor way to do it or not, but it works great for us.
>
>Now, there was a discussion here earlier, maybe a coupla weeks ago, about referencing a separate project from two different solutions (which is probably what you're talking about?) but since we don't do it this way, I'm not sure what the speed implications are for compiling. Our app takes a while to compile anyway (when starting from scratch and compiling the whole thing), simply because it's a huge application. However, when you make a small change and hit F5 to recompile and run the app, it should only be recompiling whatever change you made, so because it's not recompiling every class in the entire app, it shouldn't be taking *that* long. I'm not sure what you consider too long.
>
>~~Bonnie
>
>
>
>>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.