[Dave_Novak]

I have a somewhat strange problem with VBP 6.1 that only reproduces itself on our Build machine. When VBP finishes and exits the build, its process still hangs around in memory for about 10 seconds.

Here's how I reproduced the problem:
...* Start the VBP GUI
...* Open up Windows Task Manager and navigate to the VBP process in the “Processes” tab
...* Close the VBP GUI
...* VBP process will stay in-memory for another 10 seconds, even though it drops off the “Applications” tab immediately.

Again, this only happens on one machine (unfortunately our build machine), which is a Windows 2003 R2 SP1 box. Another Windows 2003 R2 SP1 box we have, however, works just fine.

Why is this important? We have a .NET web service that launches the VBP command-line process, monitors status, and waits for the task to signal completion. There is even a part of the service that runs a quick VBP build script that normally should take about 2 seconds, but because of this delay, it takes 12 seconds on the build machine. This is making our Web build far more painful than it should be.

Is there some setting that is causing this? Any ideas? Any possible workarounds? All other processes on the system seem to be behaving "normally".