I recently performed a Windows Update on 2 XP SP2 machines. Since then I have
2 VS .NET 2003 IDE problems that are driving me crazy. The first is that I
can no longer use the C# Class Wizard. From Class View if I select Add->Add
Class.., the wizard appears followed by an error dialog about a script error:
A Runtime Error has occurrred.
Do you wish to Debug?
Line 499
Error: Object doesn't support this property or method
If I select Yes to debug the offending line seems to be
ClassNamespace.Clear() in the function PopulateNamespaces() in default.htm. I
am dead in the water here. Can no longer use C# Class Wizard because of this.
Things worked just fine before the recent set of Windows Updates. Anyone know
how to fix this?
A 2nd problem that started at the same time is that I lost the Language
Filter capability in VS Help. I have my filter set for C# but if I use help
for a class or method, I am always getting help for all languages. Again,
this worked before my recent Windows Updates.
Pete Moss - 15 Feb 2006 16:38 GMT
It has been many weeks since I originally posted this problem, but recent
events have tied together all sorts of weird behavior and I found the problem
and a solution. Other weird behavior I had noticed is that it seems that
ActiveX controls are not being loaded into pages. This seems to be true even
when executing content in the My Computer zone. I also noticed that I could
not go to the Windows Update site. It tries to load an ActiveX control but I
see nothing and I see no Internet Explorer Information Bar. And I noticed
that the tdr.ocx control was not loading either. I noticed that the
default.htm script also tries to load an ActiveX control so this must have
been failing -- a point I failed to notice when I wrote the first post.
After all sorts of queries, I came across a post in this very newsgroup that
had the answer
http://support.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.windows
update&mid=60112b55-a428-4fd6-ba70-342d2ee2640d&sloc=en-us&sloc=en-us
which led to the following KB article describing my problem:
http://support.microsoft.com/kb/909889
It turns out that installing an IE security update 896688 (MS05-052) breaks
all of the above functionality. It can be repaired by re-creating a Registry
key included in the OLEfix.reg script referenced in the above articles. As
soon as I ran that reg patch, everything started working again.
Problem solved.