Hi Eric,
It seems that you have your registry of help collections damaged or
something went wrong with the Document Explorer sub-system itself. Try to
launch the Visual Studio Documentation shortcut separately to let it update
the help indexes and see whether it fails. If the failure persists, I think
you will have to contact Microsoft Support as the problem is quite serious.
You can also find and download the Microsoft Help SDK, it has a small
unsupported utility that administers help collections. Try launching this
utility (found AFAIR in the "Unsupported" folder of the Help SDK) and
inspect what collections you have installed and whether they are "healthy"
(unhealthy ones will be shown in red). You can try to remove unhealthy
collections (especially if they are MS.VSCC or MS.VSCC.2003) and then
re-install VS .NET.
--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE
"Eric Sykes" <noneathotmaildotcom> wrote in message
news:um**************@tk2msftngp13.phx.gbl...
After installing VSNet for several reasons I had to restore the system to
before the VSNet installation. I reinstalled VSNet no problem but now when
I open up VSNet a message pops up saying "Help is updating to reflect your
recent changes". Then a send dont send debug dialog appears and whatever
option I choose VSNet shuts down. This is an endless cycle and I cant run
any applications within the environment.
The error details read: An unhandled error has been caught by the VSW
exception filter. Any ideas before I do a major cleanout here.
Cheers
Eric
