You need to download Debugging Tools for Windows from
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx onto the
machine that will create the dump.

Then run the following command once the process is running slowly:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p <ProcessId> -quiet -o <OutputDir>

for example:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p 2055 -quiet -o C:\Temp

You can find the process id in task manager.

Hope this helps.

Regards,
Matt Garven

Hi TS,

For this issue, I suggest you check if there is any background process
running all night, which costs much memory usage and causes the system slow
done.

Also, does VS.net still takes 20 seconds for the second and following
build? Actually, for Windows system, it will poll a lot of physical pages
from memory to the disk paging file to reduce memory usage for long did not
used application, so after a long time, the VS.net's memory pages are
stored on the paging file, and the first build will cause the system to
retrieve the memory pages from disk paging file again, which will take a
far long time than normal time.

Hope this helps.
==================================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support