tags:

views:

17

answers:

0

Hello all,

I have a build running through TFS. The build process was 'customised' by overloading the 'BeforeDropBuild' target, where create an installer, remvoe all original build output and leave only our installers there. We also run some unit tests through the build. The problem is that during 'BeforeDropBuild' target, the deletion of some of the original buidl output, the unit test dlls, fails because the dlls are kept open by mstest (found this runnign handle.exe at the start of the 'BeforeDropBuild' target).

Now, am I doing something wrong? Is the a better way to approach this?

Thanks, florin