In TestStand v3.5, the TestStand Deployment tool is erroring with a -17100 error when we try to include files for a Talon Instruments SR192A that also use the ".seq" extension for some of it's data files. The Deployment tool appears to assume that these are sequence files and attempts to read paths and determine dependent files, and generates the -17100 error. Is there a way to tell the Deployment tool that these are not Sequence files and should be treated as any other file type? If not, what would be the recommended workaround to get around this issue?
Any suggestions would be greatly appreciated.
If there's no setting/method to getting around this issue in the Deployment tool, I'll add a Product Feature suggestion that the Deployment tool verify that a .seq file is a TestStand sequence before attempting to read paths and dependent files.
Thanks,
-Jack