Hi guys,

I am a long-time user of VisualMicro, exceedingly happy with the product, which has been working perfectly for a long time. You've patched every bug that has ever affected me and resolved every issue I've ever encountered.

Today I'm writing to you seeking to understand more about how Visual Micro interacts with Visual Studio during the build process, so that perhaps I can come up with a way to keep working while a build is going on.

= = =

I have long noticed that when building a C# solution (even a very large one) I can usually continue working with the code while the build is underway. 

However, when building a much smaller C++ solution using Visual Micro, the GUI is slowed to a crawl and it is impossible to work on (or even read through) the code.

It appears that the C# build is happening off the GUI thread or perhaps even out-of-process, while the C++ build is blocking or consuming the GUI thread very heavily.   

Since the actual gcc build appears to be a CLI process that can't really be occuring *on* the VS GUI thread, I'm guessing the culprit might be some kind of frequent polling with insufficient yields,  or perhaps even blocking calls being made to monitor progress.

My projects are large enough that during test-fix, half of my time is now spent waiting for the build to complete.  I'm quite anxious to improve this situation. As an ex-Microsoft guy, I could rebuild some parts of visual studio if I knew what VisualMicro was doing. 

Could you possibly explain how VM interacts with VS during the build, and perhaps offer some thoughts about how / why the VS GUI thread is being blocked or consumed during the build?

As always, thanks so much for everything you do! I would be happy to connect directly if that would be easier.

Best,

-- Craig