Herb Stahl

@peters will do. Does it work with the stock pdbs or would I still need to call PDB2PDB to convert them to portable? The [icsharpcode ILSpyCMD](https://github.com/icsharpcode/ILSpy/issues/1244) is looking to have...

👍 @peters not only does your version of ILRepack not require that I have to use PDB2PDB, but you have also solved my issue with the debugger not stepping into...

@gluck @peters So this seems to be a legitimate issue where @peters variant of ILRepack is ahead in features. Do we merge it back to this one or move on...

By Contrast, the following will exit immediately when I manage Threads myself. ``` // PocoThreadPlay.cpp : This file contains the 'main' function. Program execution begins and ends there. // #include...

The start of the issues is happening here via ~ThreadPool ``` void PooledThread::release() { const long JOIN_TIMEOUT = 10000; _mutex.lock(); _pTarget = 0; _mutex.unlock(); // In case of a statically...

@aleks-f I am zeroing in on where the issue is. The root of the problem is that PoolThread, enters into a wait as shown here; ``` void PooledThread::run() { _started.set();...

`_targetReady.set()` is getting called, because the thread is running. The PooledThread is alive and well. ``` if (_thread.isRunning()) _targetReady.set(); ``` `if (_thread.isRunning())` evaluates to true. `_thread.tryJoin(JOIN_TIMEOUT)` is acting like you...

More Clues. I changed how ThreadPoolSingletonHolder was being created. Instead of an object on the stack, it is now on the heap, which has to be explicitly deleted, which is...

@aleks-f If what I am finding is what I think it is, than I could make the following assertions; 1. Your approach to the ThreadPool is sound, however app teardown...

As is, anything that uses the default threadpool will have a shutdown problem on the Windows x64 builds I am testing. I have a working example of [TaskManager](https://github.com/ghstahl/poco.windows.visualstudio/tree/master/src/PocoTaskManagerPlay) that properly...