Does .NET Framework 3.5 SP1 require restart?

Question

Hi All,

We have a production machine and are trying to slowly introduce some 3.0 and up features on our web application. 3.5 is installed but I would like to upgrade to SP1, I would just like to know if it requires a restart of the machine in the end so I can schedule some down time.

Thanks!

EDIT: so it did require the restart, thanks guys for the answer...but the hosting company didn't give us the rights to do so...LOL

Answer 1

He he. I installed it on about 4 machines...two required a restart, two did not. The configuration was similar between them, so there was no obvious way to determine why some needed a restart and others didn't. The best theory I have currently is that the ones which needed restarts tended to be the ones which were more active (they were all running ASP.Net sites), so it is possible that the framework bits had not yet been loaded by IIS for the ones which did not need a restart.

To be safe, plan on restarting and schedule the update accordingly.

Answer 2

I have a similar situation as ckramer posted. Half my machines needed reboot, others didnt.

Answer 3

Mine did not. But I do anyway. Clear the bits.

Answer 4

I ran the update on a Windows XP machine yesterday and it did not require a restart.

Answer 5

3.5 SP1 updates 3.0 to SP2 and 2.0 (which contains the CLR) to SP2. If the CLR is loaded in any process the DLLs will not be writable, and a reboot will be required.

Answer 6

every machine that I have touched with SP1 for .Net 3.5 has required a reboot. It totally trashed my Team Foundation Server box.