The exact text is Runtime Error!
Program c:\Pro...
R6025
-Pure virtual function call
The title of the message box is
Microsoft Visual C++ Runtime Library.
I do not have 05 C++ installed. I've already tried vstor.exe. My registry key
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio \8.0\Setup\VSTO]< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
exists and is pointing to the correct directory C:\Program Files\Microsoft Visual Studio 8\Visual Studio Tools for Office\
I've uninstalled and re-installed. There are no installation errors.
Any other ideas
(XP pro, 2005, 1gig of ram, 40gig HD)
More VSTO install woes
LiFo
hyl
I'm sorry, I'm not sure what more I can tell you to make this clearer. If there is something specific that you aren't understanding, I'd be happy to try to clarify. You might also consider contacting product support for help. I believe you get two free support incidents with the product. See the Microsoft Support Services website for options: http://www.microsoft.com/services/microsoftservices/srv_support.mspx#itpros It sounds like you might benefit from someone working directly with you on this issue.
Sincerely,
Geoff Darst
Microsoft VSTO Tools
MarkBruce
As Misha says, something is fairly messed up on your machine. The error you are seeing is generated by the C++ runtime (not the C++ product). What it is saying is that the code is attempting to call a function that has no implementation. Since we are dealing with shipping code, this likely means that you have an incorrect version of some dll installed. Remember "dll hell" It sounds like you are in it (sorry!).
Probably the simplest way to figure out what is going on is to attach a debugger to the process that is throwing the error (it could be either devenv.exe or excel/word.exe) and put a breakpoint on the _purecall function. _purecall can be found in PureVirt.c (which is part of the crt sources which you should have as part of your VS install). I'm not sure where they get installed to--you may need to search your drive for that file. If you don't have it, go back to your install and make sure you install the crt sources. Anyway, _purecall is the handler for pure virtual function calls, so once you hit it, you can check your stack to see what function the runtime was trying to call. More importantly, the stack will give you the dll that the function resides in. Then check the modules window and find out where the dll is being loaded from. Finally, do a search on your machine for all copies of that dll. Either you will have multiple copies (and the wrong one is being loaded) or you will simply have the wrong version. In the former case, the problem is most likely a path setting that is causing the loader to find the wrong dll. Alternatively, see the help for LoadLibrary in msdn for the complete algorithm that the loader follows to find dlls & from that deduce the cause of your problem. If you've just got one copy of the dll and it is wrong, try renaming it, rebooting, and then reinstalling. You might break some other piece of software if you do that, so you'll just have to beware. This latter scenario is probably much less likely.
Good Luck!
Geoff Darst
Microsoft VSTO Tools
JohnStallo