We are enjoying using WiseJ for one of our development projects. Just one thing is causing slight annoyance at the moment and we are not sure if we are missing something obvious.
One of the solutions we build using WiseJ is quite complex, and contains a main project (web site) and several custom WiseJ components built as a few libraries.
We are using an up-to-date copy of VS2017, and quite frequently after debugging the subsequent build will fail due to iisexpress.exe holding onto one or more of the output .DLL files – causing the build to fail.
As a dirty work-around we have added a pre-build script like:
echo Terminate IISExpress …
taskkill /F /IM iisexpress.exe /T 2>nul 1>nul
This brute-force kills the process and ensures that the build always works – it does seem a bit nasty though.
Has anyone else experienced this?
I tried disabling the “Edit and Continue” feature (on the debuggers tab of the main project properties) but this didn’t seem to do anything.
As a better work-around, I’ve taken and modified the code here:
I’ve made a little .exe that closes the tray icon correctly by sending a WM_QUIT to that process and then kills the IISExpress worker process.
This works fine, and I no longer get an accumulation of ‘dead’ IIS tray icons either.
Probably do for now!
Please login first to submit.