467,116 Members | 1,121 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,116 developers. It's quick & easy.

Custom build steps

I am trying to emulate the C# behaviour of copying referenced assemblies
into the build output directory but for normal DLLs. Currently some
components (DLLs) are build and dumped into a shared area with the system
path set to it so that the main application can run. This causes a number of
problems; the main one being that we want to develop / run side by side
versions of our application (branches) concurrently. So I thought that
custom steps would be the way to go with the input being the built component
dll and the output being the target directory / component name. Is this the
correct way to go or is there a better way? There is only one custom build
step for a project and I have mulitple referenced components...

Any help would be appreciated...

Regards
Lee
Nov 16 '05 #1
  • viewed: 955
Share:

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

16 posts views Thread by Bret Pehrson | last post: by
2 posts views Thread by prabhupr@hotmail.com | last post: by
1 post views Thread by Michael Russell | last post: by
15 posts views Thread by rizwanahmed24@gmail.com | last post: by
reply views Thread by thomas.santos@gmail.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.