Thanks for the reply Victor. I understand what you are saying about what should be considered when breaking this up into projects as your questions point out.

With that all aside when I originally posted the question I was wondering if there were any benefits or hardships for breaking them up into separate projects, as the VS IDE makes it simple to combine other projects into one, and I thought there might be a good reason Microsoft did that, other than what you mentioned. The response you provided seems to indicate don't do it unless necessary and really think hard about how they will be used in the future, which I have always learned is unpredictable.

Thank you


>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.
>
>There is a few variable that come into play when trying to find an answer to this question...
>
>First question: How developers are in your team? The more developers in your team to more you'll want to break down your project. It's not to say that every business object will need it's own project. I would consider a large team 10 or more developers working on the same exact project.
>
>Second Question: Will the business process be required to be identical on the web as it is in a windows application? This becomes very important in you're gonna make a Windows App and convert it to a Web App where the business rules is required to be identical in both segments. In this case you at least want to create a business project in order to reuse it in both web and windows app.
>
>Third Question: I hope you're using Visual Source Safe or some other kind of source control vault... Well, are you? :) Actually, I don't have a third question but I'm sure someone might have one...