Hi Lyle,
Thank you for your comment.
I did not "forget" so much as I left the code there for you (or anyone else) to uncomment if you so choose.
I am not able to provide support for TaskGuardian as I am a full time student. I wrote it for myself, then when I saw a lot of people were having this problem and ESRI support staff were unable to reproduce the problem, I decided to share it "as-is". I have reverted my machine to 2.9 for other reasons for the next few months, so I don't actually need TaskGuardian any more.
But it is licensed as Apache 2.0, which means you or anyone can make whatever modifications you like to your own version. The idea of killing the Indexing Server first is a good idea, but it would be yours to implement.
Regarding the creation of an exe, I chose not to do that as exe's posted in public can have malware inserted into them. By posting just the code and the solution, I make it so you can see that there is no malicious code, and so you can create your own exe, which you then have responsibility for. So I recommend you build from Visual Studio, which creates the exe under
%yourDirectory%TaskGuardian\bin\Release\netcoreapp3.1 as TaskGuardian.exe.
You can take that exe and move it wherever you like, and you can even make it be a Windows startup task. That is all as-you-like and as you have permission from your employer. But I can not accept any liability for what others do with this as-is code, and I can't take my student time to support others. It is really ESRI's responsibility to deal with the underlying problem, and I have made TaskGuardian public for other's convenience.
Thank you for understanding my situation.
- Paul