Editing MFC Operator Interface

[developer123]

Hi,

Recently, I've coded an application that uses the TestStand API to open and edit sequence files successfully.

Now, I want to edit the simple operator interface example employing MFC. However, even if the project compiles and executes correctly, I'm not able to edit the UI.

When I try to open the "IDD_TESTEXEC_DIALOG" from Visual Studio, I get the following error popup window:

"19 ActiveX controls could not be instantiated.

Reinstall or register the controls and try again."

I tried opening the resource file with Notepad and searched for the UI control's ID in the register inside HKEY_CLASSES_ROOT/CLSID.
The IDs do not exist in my registry.

Do I need something extra to install? Maybe a Visual Studio addon?

Thanks

[developer123]

I also tried the C# example, and I get the following trying to open the CS form:

And when I try to drag a component from the toolbox to the form:

And when I double click the component in VS:

Does anyone have any clue about the issue?

[angus2022 · Accepted solution]

Hi，bro：

      I don't understand C++and MFC

      However, I know some information about C #. May I ask which version of the Teststand and Visual Studio you are using?

      Do not use the latest Visual Studio to develop with Teststand, such as developing Teststand 2017. You can only use Visual Studio 2017 at most. NI mentioned that the latest versions of Visual Studio (vs2019, vs2022...) have incomplete testing and may have unknown issues.

       You can try using Visual Studio 2015 or 2017 to open the example program for Teststand 2017. If your teststand is an older version, you will also need to use an older version of Visual Studio accordingly. For specific information, you can refer to NI's release instructions for the corresponding version.

[developer123]

LOL. You are very right!

TestStand 2019 's UI API is not compatible with Visual Studio 2022. I installed VS 2017 and dialogs open normally.

It would be nice to add this info: Compatibility TestSTand - Visual Studio to the API documentation😞.

Thanks for the tip Angus