Er, I'm not certain what C#/.NET/VS have to do w/ this particular issue ? If you check my update to Odd threads::shared behavior within a Win32::Daemon app, you'll see I have managed to get everything working, tho wo/ really understanding why my minor change fixes the problem. Thus far I've gotten 28 threads up and running as a Win32 service, and expect to start testing 50+ on a beefier server in the next few days.

The only remaining area of concern I have is the autorecovery issue, which I already know how to fix (using plain old C/C++ and the new API I linked in my update in the OP), but don't have time at the moment.

Admittedly, MSFT has once again made this process is a PITA, but once I figured it all out, it's not too bad. I spose I should writeup a little Meditation or Cool Uses article on the process.