Debugging LabWindows/CVI version 2.0

[mark.tudor]

Ah sorry misread it.  I do have CVI on the PC.  I am building the project that creates the dll in CVI, but when I go to Run > Debug seqEdit.exe is when I get the error.

[Dennis_Knutson]

Now I'm not sure what you are trying to debug. While this method will allow you to start up TestStand, you don't have to do that to debug the dll. You can debug the dll in CVI itself. When I start the sequence editor from CVI, I only do that when I need to debug some code that uses TestStand methods and properties and needs the engine running.

I have another question. If you don't have TestStand 2.0, how are you creating a test sequence for it that uses the dll? Or is this a dll a replacement for a test step that already exists?

And, I just remembered that when you install a new version of TestStand, you also get a version selector so that you can switch between different engines. I know this works with the different development systems installed since at one time, I had 2.0, 3.0. and 4.0 on the same pc but I have no idea if it will work if one of the engines is just the runtime.  If you try this, make a backup first.

[mark.tudor]

The dll existed before I got here.  I am the one who gets to come back and look it over to find out why it isn't working correctly.  This is my first project using TestStand / CVI so I am trying to learn on the fly.  I am installing TestStand 4.1.1 onto the PC now.  I've got a backup so hopefully things will turn out ok.

[mark.tudor]

Looks like I am on the right track.  Having them both on the same machine and using the version selector has got me up and running for the time being.  Thanks for the help Dennis.