Hi Mike
thanks very much for getting back to me. I won't submit a patch - as my 'fix' is quick and filthy; as I don't really have much clue where to begin and as I am mutex-ing irrespective of target machine (see below).
It is something that I've been pretty sure I'd hit now that MSBuild is more and more ||. Luckily for me you have made the source of these tasks available, so thank you for that. If you do create a task for this, please let me know - I am intrigued to know how it could get fixed.
Neil
I slung this in BaseTask
protected static Mutex IisMutex = new Mutex(false, IisMutexName);
protected const string IisMutexName = "Iis-IisMutex";
protected const int IisMutexTimeout = 5000;
And the InternalExecute() methods of Iis7Application; Iis7AppPool; Iis7Binding; Iis7Website now have:
try
thanks very much for getting back to me. I won't submit a patch - as my 'fix' is quick and filthy; as I don't really have much clue where to begin and as I am mutex-ing irrespective of target machine (see below).
It is something that I've been pretty sure I'd hit now that MSBuild is more and more ||. Luckily for me you have made the source of these tasks available, so thank you for that. If you do create a task for this, please let me know - I am intrigued to know how it could get fixed.
Neil
I slung this in BaseTask
protected static Mutex IisMutex = new Mutex(false, IisMutexName);
protected const string IisMutexName = "Iis-IisMutex";
protected const int IisMutexTimeout = 5000;
And the InternalExecute() methods of Iis7Application; Iis7AppPool; Iis7Binding; Iis7Website now have:
try
{
IisMutex.WaitOne(IisMutexTimeout);
... }
finally
{
IisMutex.ReleaseMutex();
... }