My solution builds approximately 12 projects and the DLL for each needs to ultimately reside in its own directory for deployment. I'm looking for suggestions as to the best approach for achieving this. One approach I tried is to recursively load all the .dll files into an ItemGroup collection, however, I'm faced with having to:
- filter out unwanted/extraneous .dlls when I attempt to move the .dlls to their folders
- determine the correct folder for each directory dynamically
I don't have the option of creating deployment directories based on file or assembly meta-data because the deployment directory names are pre-existing.
Also, I am compiling a VS2003 solution via a custom task.
Any assistance is greatly appreciated.
RESOLVED --> Question regarding MSBuild copy task
cwatkins-gd
I coded another custom task to arrive at the desired outcome.
In my project file I create an ItemGroup for the files along with the appropriate custom metadata elements. In my task I do the move, deleting any files of the same name which already exist.