Hi there,

I got the following stupid problem:

Whenever I start a program from VS (professional 2003), no matter if
with or w/o debugging, a message box pops up saying "No such interface
supported." My diagnosis is that I probably messed up the registry, so
that some debugger components aren't found.

I tried to fix the problem by doing a reinstall/repair installation
- didn't help. I then wanted to uninstall/reinstall VS, but I cannot
uninstall - "Setup is unable to determine a valid ordering for the
installation."

Does anyone have advice here? The next step I am thinking about is
to reinstall my system - but I would be happy if I could prevent this
by simply putting a few missing entries into the registry. Any help is
appreciated!

Regards

For your Debug/Run problem you might want to try to register oleaut32.dll
- see if that fixes that problem...
regsvr32 %SystemRoot%\system32\oleaut32.dll

For your uninstall - I am trying to find a solution. Will try to get back
to you on this later today.

Sorry to say...what I have found is you will have to manually uninstall
this product once you have ran into this problem. Not sure what caused
your problem however...

Follow these directions to uninstall manually
http://support.microsoft.com/default.aspx?scid=kb;en-us;824642

thanks

Robert S (MSFT Visual Basic QA)
--------------------------------------------------------------------
This reply is provided AS IS, without warranty (express or implied).

Hi,

Do you know of any solution for fixing intellisense?

Thanks

Francisco


[quoted text, click to view]

Do not have any experience with brokent intellisense.

But...please check to make sure it is enabled by:
Choose Options from the Tools menu.
Choose the Text Editor tab in the Options dialog box.
In the Statement Completion Options area, turn on features that you want if
they are not already...

Hopefully somehow the feature got turned off...

Also make sure that you are not having compile errors somewhere in your
code. Additionally if you are using late binding intellisense will not
work for those instances...All of these could impact intellisense
functionality.

hope this helps.

Robert S (MSFT Visual Basic QA)
--------------------------------------------------------------------
This reply is provided AS IS, without warranty (express or implied).