VS.NET 2003 - F1 help, doesn't display 1st time, but does 2nd time?

[Rob R. Ainscough]

I have an interesting problem that is either a bug or just some local issue
with my PC (probably the later).

If I place my cursor on a word and hit F1 for help, it goes thru a process
(see a message in the lower left corner saying Downloading...) and my hard
disk churns away for a 2-4 seconds and then displays the "can't display this
page" (standard explorer type message when a web site can't be found).

Example

Imports System.Xml
.... place the cursor anywhere in "xml" and hit F1

The even stranger part after I get the "can't display this page" message, if
I close that window and hit F1 again, it works!? Bizarre.

Anyone else have this problem?

Rob.

 

[Charles Law]

Hi Rob

I get exactly the same. Also, when I open MSDN locally, the start-up page
does not always load, presenting me instead with the same error page. I
close it and open again and all is well.

I had always assumed that it was a timeout on the page because it took
longer than expected to find/load, even though the page is held on the local
m/c. I don't know how to fix it, unfortunately, and have just learned to
live with it. It is quite irritating though.

Charles

 

[Rob R. Ainscough]

It is good to know I'm not alone with this problem.

Definitely not a show stopper, just annoying.

I also had my first VS.NET 2003 termination this morning -- I was attempting
to debug a Windows Service (created with VB.NET). I loaded the source
solution and then from the menu selected "Tools | Debug Process..." and
wham, generated an exception in VSW (or something like that) -- VS.NET
shutdown and was back at my desktop with a MS error reporting dialog -- so I
reported the error. Anyway, reloaded VS.NET open my solution did exactly
the same "Tools | Debug Process..." and no problem this time?? I was able
to attach a debug session to my Windows Service.

The similarity being it failed the first time, but worked the second time.

Just curious what OS and what .NET framework version are you using?

I'm running WinXP SP2 and .NET v1.1 SP1 -- ever since I installed the SP1
for .NET v1.1 I've had a slew of strange problems (and not specific to a
single PC) that weren't around before I installed .NET v1.1 SP1 -- such as
wireless devices icons appearing in my systray, then going away (not even on
a wireless network), 3 minute dead zone (unresponsive) after the desktop
loads and a slew of other strange little issues. I suspect that SP1 was a
rushed release to plug up some security holes in the framework.

Any word when .NET framework v2.0 will move out of Beta?

Rob.