iis - DCOM problems building a VB6 app in CruiseControl.net -

i can build vb6 application relies upon several dcom settings on build machine, no problem.

however. second time try run same build process, fails, dcom and/or iis have locks on output files i'm trynig rebuild.

currently, if log onto build machine , reset iis (using iisreset or otherwise), releases locks on output files, allowing build complete successfully.

obviously, don't want have log onto build machine , don't want have keep resetting iis - there way around this?

thanks.

i think i've found solution - not pretty, it's 1 way around it.

basically, prior build, calling out small application kill running processes going built during build. once they're killed, component no longer running in memory , no longer holding lock files.

as say, there's cleaner way of doing , keep looking, now, should suffice.