Reload automation server doesn't work for all steps

[FrankJ]

Hi all,

I'm creating ActiveX Servers using Visual Basic 6. In TestStand 3.1 I have steps that call methods from an automation server and I have steps that get properties of an automation server.

When I create a new version of an automation server, I open one of the steps that use the automation server and press "Reload", so that is uses the latest version. TestStand Automatically updates all the rest of the steps that use the same automation server, but for some reason it only updates the steps that call a method and not the steps that Get a property. Why is this?

[Scott_Richardson]

Frank -
When you configure a TestStand step to call an automation server, it stores the specific ID information for the server and the class and method/property that you are calling. If the server is created with MSVB the compatibility mode of the project defines whether MSVB alters this information after each recompile of the project. TestStand tries to find the server, class and method/property after you compile the project each time. If you take a look at the Compatibility Options for Visual Basic section in Chapter 5 of the TestStand 3.x Reference Manual you will find more information on this. The section describes the various compatibility modes Visual Basic projects. In a nut shell, it is recommended to use Project Compatibility while developing code and switch to Binary Compatibility when you release a system. When you switch to Binary Compatibility you should keep it there and only add new methods or classes. You should not change the names or prototypes of existing methods or properties for this breaks binary compatibility. In my previous development, it would have been nice if VB exposed the control of these IDs, but they do not.