Are the latest IE and .NET updates breaking the Visual Studio .NET 2003
environment in a bad way? A colleague of mine had the same problem after
installing the updates as I am now having (badly enough, this machine I work
on had automatic updates on and they were installed before I got to it). The
local debugging fails and I can't pull up a local ASP.NET website on my
external browser. My colleague had to basically redo his machine and
reinstall IIS, IE and .NET to get it going again. Anyone else having this
problem? If so, is there an easier fix available then spending two days
rebuilding the machine?
|
Linear Mode
