Visual Studio 2010 freezes when post-build events run

Why does Visual Studio 2010 freeze when it runs events after the build? It seems that he makes them on the gui line. Because of this, now I place all the instructions in the .cmd file, so I can at least see the output in real time, and not after the build is complete. Should it work this way, or am I doing something wrong?

UPD: If I put notepad.exe in post-build events, then Visual Studio will stop responding to any user input (and after a while the message "Visual Studio is busy" will appear) until I close the notebook. The question is how to make VS responsive (so that I can at least click the "output" tab) while notepad is working.

+4
source share
1 answer

Postbuild events must work for successful compilation. Value, even if the event is some kind of mechanism that is not related to the project that you invested in, if it fails, your compilation will fail. For example, when creating Media Center applications, the standard process is to include a DLL, which, according to the SDK, is located on your system, but actually left Vista, so if you leave the post build event, you can not even compile your code.

0
source

All Articles