VS.NET

[Jon Slaughter]

I'm trying to setup the solution for a medium sized project that uses many
different components(dll's).

What I want is for each "part" to compile to a seperate dll. The way I am
doing this now is creating a different project for each "part" but I was
wondering if there was an easier way? Its kinda messy having a bunch of
projects in the solution with just 2 files in it(the class and then the
designer class). The reason why I want the dll's is so they can be replaced
easily. (they are controls and I'd like the ability to dynamically replace
the dll's)

So is it necessarily to do this or is there another way? I was thinking
about juse using one project temporarily for the controls and then splitting
them up when I needed to to get the dll's generated.

Thanks,
Jon

 

[Daniel]

What i do is have lots of projects for each and then one main solution that
i import all those projects into and work from there.

Easy to manage, you can quickly flick between projects and all in separate
dlls. But really its your preference, no right or wrong way on this.