Multi-projects solution

[=?Utf-8?B?QmVu?=]

Hi all,

Can you share with a few examples in which to create multi-project
solutions. I am not sure why that would be necessary. Why would I opt to
use this feature in VS2005?

I know this feature existed back in classic vb like VB6, but I never find
it necessary to use. Can you share some thoughts on this? Thanks.

Ben
--

[Ray Cassick]

For one example most times when you want to remote a class you need to do
this.

I do it all the time when I need to build an application that uses correct
separation of business logic, data, and presentation layers.

"Ben" <Be*@discussions.microsoft.comwrote in message
news:F2**********************************@microsof t.com...

Hi all,

Can you share with a few examples in which to create multi-project
solutions. I am not sure why that would be necessary. Why would I opt
to
use this feature in VS2005?

I know this feature existed back in classic vb like VB6, but I never find
it necessary to use. Can you share some thoughts on this? Thanks.

Ben
--

[hav]

you could have a seperate project for an installer - anything
related. Also different types or different versions....
on another note does anyone know where "WinDiff" went? I have vs2005
Cheers
hav

[rowe_newsgroups]

On Jun 12, 9:31 pm, Ben <[e-mail]:

Hi all,

Can you share with a few examples in which to create multi-project
solutions. I am not sure why that would be necessary. Why would I opt to
use this feature in VS2005?

I know this feature existed back in classic vb like VB6, but I never find
it necessary to use. Can you share some thoughts on this? Thanks.

Ben

--

I use it often for plugin architectures. Having the project for the
main executable, the Interfaces dll, and all the seperate plugin dlls
in one place make for easy changes. It also comes in handy when you
need to cross the language barrier - suppose you have an old C# class
library you wish to update and use with a new VB project? Then it just
makes more since to combine the two into a solution than to update
them in seperate instances of the IDE.

Thanks,

Seth Rowe

[=?Utf-8?B?QmVu?=]

Thanks everyone for sharing your thoughts.

Ben

--

"Ben" wrote:

Hi all,

Can you share with a few examples in which to create multi-project
solutions. I am not sure why that would be necessary. Why would I opt to
use this feature in VS2005?

I know this feature existed back in classic vb like VB6, but I never find
it necessary to use. Can you share some thoughts on this? Thanks.

Ben
--

[sloan]

Unit Testing should go in its own project. Because you won't distribute
that to the customer.

Prez/BAL/DAL are good candidates.

"Ben" <Be*@discussions.microsoft.comwrote in message
news:F2**********************************@microsof t.com...

Hi all,

Can you share with a few examples in which to create multi-project
solutions. I am not sure why that would be necessary. Why would I opt

to

use this feature in VS2005?

I know this feature existed back in classic vb like VB6, but I never find
it necessary to use. Can you share some thoughts on this? Thanks.

Ben
--