472,119 Members | 1,752 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,119 software developers and data experts.

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...

Nov 16 '05 #1
0 1040

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 | last post: by
1 post views Thread by Michael Russell | last post: by
reply views Thread by thomas.santos | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.