Multiple Projects in one Solution

[Samuel L Matzen]

Hi,

I am trying to develop with multiple projects in a single solution. The
many of these projects create .dlls that are used by other projects. When I
reference a .dll I reference it in the bin directory of the project creating
it.

The problem I am having is that Visual Studio keeps throwing a whole bunch
of error messages indicateing it can't overrite other version of dlls and
that one object can't be converted to another object which are exactly the
same.

Has anyone got multiple dependent project development to work in a single
solution?

Is there some basic issue I am missing here?

Thanks in advance for any advice,

Sam Matzen

[Tom Shelton]

On 2003-11-29, Samuel L Matzen <sm*****@slm.com> wrote:

Hi,

I am trying to develop with multiple projects in a single solution. The
many of these projects create .dlls that are used by other projects. When I
reference a .dll I reference it in the bin directory of the project creating
it.

The problem I am having is that Visual Studio keeps throwing a whole bunch
of error messages indicateing it can't overrite other version of dlls and
that one object can't be converted to another object which are exactly the
same.

Has anyone got multiple dependent project development to work in a single
solution?

Is there some basic issue I am missing here?

Thanks in advance for any advice,

Sam Matzen

Yes - I do it all the time. Don't reference the .dlls. Reference the
projects. When you go to the add reference dialog box, select the tab
marked project.

--
Tom Shelton
MVP [Visual Basic]

[Samuel L Matzen]

Tom,

Thanks. That was right on. Now all of my problem went away.

Keep up the good work. And, thanks for the quick response on Saturday
Night.

-Sam Matzen
"Tom Shelton" <to*@mtogden.com> wrote in message
news:eM**************@TK2MSFTNGP10.phx.gbl...

On 2003-11-29, Samuel L Matzen <sm*****@slm.com> wrote:

Hi,

I am trying to develop with multiple projects in a single solution. The
many of these projects create .dlls that are used by other projects. When I reference a .dll I reference it in the bin directory of the project creating it.

The problem I am having is that Visual Studio keeps throwing a whole bunch of error messages indicateing it can't overrite other version of dlls and that one object can't be converted to another object which are exactly the same.

Has anyone got multiple dependent project development to work in a single solution?

Is there some basic issue I am missing here?

Thanks in advance for any advice,

Sam Matzen

Yes - I do it all the time. Don't reference the .dlls. Reference the
projects. When you go to the add reference dialog box, select the tab
marked project.

--
Tom Shelton
MVP [Visual Basic]