How to stop updating DLLs?

[Brett Romero]

Say I have four projects - one is an EXE and three are DLLs. The EXE
references all three DLLs. If I update one of the DLLs and compile,
next time I run my EXE project, it will get the latest version of the
changed DLL and use it. How do I keep the EXE project from getting the
latest version of a DLL? I'd like it to use the version in its bin
folder (b/c copy local is true).

Thanks,
Brett

[David Browne]

"Brett Romero" <ac*****@cygen.com> wrote in message
news:11*********************@g47g2000cwa.googlegro ups.com...

Say I have four projects - one is an EXE and three are DLLs. The EXE
references all three DLLs. If I update one of the DLLs and compile,
next time I run my EXE project, it will get the latest version of the
changed DLL and use it. How do I keep the EXE project from getting the
latest version of a DLL? I'd like it to use the version in its bin
folder (b/c copy local is true).

Create a \lib folder as a sibling to your exe's .bin folder. Deploy the
..DLL's there and use a binary reference instad of a project reference. Then
the EXE, when built, will copy the version in the \lib folder instead of the
latest version.

David

[Brett Romero]

What do you mean by a binary reference? I don't reference any projects
now. Just the direct DLL. Is that what you are referring to?

Thanks,
Brett

[David Browne]

"Brett Romero" <ac*****@cygen.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

What do you mean by a binary reference? I don't reference any projects
now. Just the direct DLL. Is that what you are referring to?

Yes, by binary reference, I mean a direct reference to an assembly.

David

[Benny Raymond]

Brett Romero wrote:

Say I have four projects - one is an EXE and three are DLLs. The EXE
references all three DLLs. If I update one of the DLLs and compile,
next time I run my EXE project, it will get the latest version of the
changed DLL and use it. How do I keep the EXE project from getting the
latest version of a DLL? I'd like it to use the version in its bin
folder (b/c copy local is true).

Thanks,
Brett

Change your build so that the dlls don't build. Then when you want a
specific dll updated just go into properties again and check which one
you want to build.

You can also set up different builds like a "Debug (no dlls)" - just
copy the debug build and remove the check next to the three dll projects.

--
Benny Raymond
http://bloatedcowsoftware.com

[Brett Romero]

Thanks about the different builds. I didn't know of those. That's
basically build profiles?

Is there a way to create a build, save it, and give it to your co
worker that is using the same project? Then he builds for only the
items you have selected but doesn't have to worry about creating the
build setup or forgetting to.

Thanks,
Brett

[Brett Romero]

These options for DLLs don't exists. They only exists for projects.

Brett

[Benny Raymond]

Brett Romero wrote:

These options for DLLs don't exists. They only exists for projects.

Brett

Ahh... I thought you were building the dlls as seperate projects within
a larger solution. That's how I handle all of my dlls.

--
Benny Raymond
http://bloatedcowsoftware.com

[Brett Romero]

If you don't have the particular project or want a DLL reference, the
only options to to copy local true/false, which doesn't really seem to
do anything.

Brett