Need help setting up Solution

[Ray Mitchell]

Hello,

I currently have a .dll assembly and 2 .exe assemblies that both use the
..dll assembly. I currently have the IDE set up as 3 separate projects. I
must always first build the .dll assembly, then the other two. What I'd
like to be able to do is to set it up so that they all work together, that
is whenever I change something in either of the 3 whatever is necessary will
be rebuilt in the correct order automagically. When I tried to do this by
putting everything into one assembly it complained (as expected) that there
were 2 Main entry points.

Thanks,
Ray Mitchell

[Daniel O'Connell]

"Ray Mitchell" <Ra*********@MeanOldTeacher.com> wrote in message
news:ph******************@newsread2.news.pas.earth link.net...

Hello,

I currently have a .dll assembly and 2 .exe assemblies that both use the
.dll assembly. I currently have the IDE set up as 3 separate projects. I
must always first build the .dll assembly, then the other two. What I'd
like to be able to do is to set it up so that they all work together, that
is whenever I change something in either of the 3 whatever is necessary will be rebuilt in the correct order automagically. When I tried to do this by
putting everything into one assembly it complained (as expected) that there were 2 Main entry points.
Use project references (Add Reference, Projects tab) instead of hard
references to the assembly. This will do what you want. Thanks,
Ray Mitchell

[Ray Mitchell]

"Daniel O'Connell" <[e-mail]> wrote in message
news:ej**************@TK2MSFTNGP11.phx.gbl...

"Ray Mitchell" <Ra*********@MeanOldTeacher.com> wrote in message
news:ph******************@newsread2.news.pas.earth link.net...

Hello,

I currently have a .dll assembly and 2 .exe assemblies that both use the
.dll assembly. I currently have the IDE set up as 3 separate projects. I must always first build the .dll assembly, then the other two. What I'd
like to be able to do is to set it up so that they all work together, that is whenever I change something in either of the 3 whatever is necessary

will

be rebuilt in the correct order automagically. When I tried to do this by putting everything into one assembly it complained (as expected) that

there

were 2 Main entry points.

Use project references (Add Reference, Projects tab) instead of hard
references to the assembly. This will do what you want.

Thanks,
Ray Mitchell

I think that's what I've done. I've added a reference to the common .dll
created by the common project to the list of references for each of the
other two projects that use that .dll. A I missing what you're telling me
somehow? Thanks for your help.

[Daniel O'Connell]

"Ray Mitchell" <Ra*********@MeanOldTeacher.com> wrote in message
news:hc*******************@newsread2.news.pas.eart hlink.net...

"Daniel O'Connell" <[e-mail]> wrote in message
news:ej**************@TK2MSFTNGP11.phx.gbl...

"Ray Mitchell" <Ra*********@MeanOldTeacher.com> wrote in message
news:ph******************@newsread2.news.pas.earth link.net...

Hello,

I currently have a .dll assembly and 2 .exe assemblies that both use the .dll assembly. I currently have the IDE set up as 3 separate projects.

I

must always first build the .dll assembly, then the other two. What

I'd like to be able to do is to set it up so that they all work together, that is whenever I change something in either of the 3 whatever is

necessary will

be rebuilt in the correct order automagically. When I tried to do

this by putting everything into one assembly it complained (as expected) that there

were 2 Main entry points.

Use project references (Add Reference, Projects tab) instead of hard
references to the assembly. This will do what you want.

Thanks,
Ray Mitchell

I think that's what I've done. I've added a reference to the common .dll
created by the common project to the list of references for each of the
other two projects that use that .dll. A I missing what you're telling me
somehow? Thanks for your help.

In vs.net, there are four types of references, .assembly file references,
which reference assemblies on disk, COM references that referernce COM
objects via interop assemblies, Web references that reference web services
through similar proxy assemblies, and project references which are linked to
a project, not a given file. By linking to a project in the current
solution, visual studio adds a dependency and automatically builds all
assemblies the assembly you are building is dependent upon, this is the
effect you are after, correct?

To achieve it, when you add the reference, you would use the Projects tab on
the Add Reference dialog, not the .NET tab.