Thursday, July 05, 2012
You know the score, you install or update something within the .NET framework and that friendly mscorsvw.exe kicks off recompiling assemblies for you (a good thing) and takes up nearly all your CPU.
But when you have an occasionally used machine, it might be nice if it did not do it for each of 10-20 patches for the framework. And not in turn for each one. It’s bloody annoying, especially when that machine has been turned on especially for an unplanned piece of work.
Is there a good reason it cannot be run once, after the last patch is applied? Or is that just too sensible…
(added later)Yes I know you can park the jobs, or run them later, or drop the priority. But the whole point of the patching is to be done under the covers, and just done seamlessly and easily. Not to intrude so much!