QTP and Visual Studio Tools for Office (VSTO)...
QTP version: 8.2
QTP .Net add-in version: 8.2, all patches up to 2114 applied.
I am taking a look at building automated scripts for an application which essentially is a plug in to Excel using VSTO. The plug in functionality is seen in the Excel action pane. When I attempt to spy the objects in the action pane, Excel fails altogether and does the same if I attempt to record. I can turn off the .net add in and complete some spying and recording of the app, but objects are recognized only as winobjects, so scripting may be somewhat unreliable.
I am certain the .net add in is working properly as I am able to spy and record on standalone .net apps with not problems, so the problem seems to revolve around an embedded .net app in Excel.
On Mercury discussion forums, I found one posting for an issue similar to this issue, except the .net VSTO plug in was placed in Outlook rather than Excel. Behavior was very much the same, however. Unfortunately, no solutions for that issue were posted.
We should be upgrading to the latest and greatest version of QTP in the near future hopefully, but in the interim it would be great if a solution exists for the version of QTP we are using. Has anyone here completed automation for a similar scenario. Thanks.
Re: QTP and Visual Studio Tools for Office (VSTO)...
One other item to add with regard to this issue. When I spy an object in the action pane containing the .net elements, the Microsoft Excel message appears almost immediately, but if I leave the message on screen and wait for a minute or so, the correct object definition for the .net object I am trying to spy appears. So at some level, the .net addin does seem to work against the .net objects in the action pane, but not without causing an Excel failure.