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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.