activex control not registered

[mrbean]

I do plan to deploy a custom OI, after I get the full-featured OI working first. What will I have to do differently?

[Eric M]

Instead of placing a check mark next to the Full-Featured LabWindows/CVI OI in the TestStand Engine Options dialog, you need to include in a project the EXE, UIR and other files you created on which your custom OI depends.

There are step by step instructions for deploying an OI in the TestStand reference manual starting on page 14-10. Do note that step 5 should reference TestExec.exe and not TestStand.exe.

[mrbean]

I had copied the full-featured OI contents to the user folder and that is what I had in my second TestStand project contained in my workspace file. Therefore, I didn't have the full-featured OI checked in the Installer Options tab (within the Engine Options). I did, however, already have Install TestStand Engine checked.

I did see one thing in your response that caught my eye. You said "If you install TestStand on the target machine, you can use a Deployment (Run-time) License to activate TestStand".

1) by "If you install TestStand on the target machine" do you mean the checkmark next to "Install TestStand Engine"

2) to use "Deployment (Run-time) License to activate TestStand", what do I need to do.

[Eric M]

By (1), I mean, instead of selecting to install the TestStand Engine when building your deployment, you could install TestStand on your target machine just like you installed it on your development machine.

Then, for (2), if you have a Deployment (Run-Time) License, you can use the serial number associated with that license instead of activating TestStand using the serial number that is associated with your Development License. Using the Deployment (Run-Time) License would activate the TestStand Base Deployment Engine.

If you are not familiar with the TestStand Base Deployment Engine or the TestStand Debug Deployment Environment, you may want to check out the linked pages.

-Eric