Using a process model and configuration NOT in the standard directory

[CoastalLabVIEWER]

Sorry, I should have been a bit more detailed.

---

@~jiggawax~ wrote:

---

If it is linked through the station model then you need to also include your station options configuration file in your deployment along with the process model and all of its dependencies called out there.

This is mostly the part I'm asking about.  At work we recieved both the source code and a prebuilt .exe of it all.  I've mostly only dealt with LabVIEW and TS at the development environment level and am a bit weak on the build process.

We'd like to change the "Test Sequence Passed" banner to something else and I know it's either mod modelsupport2.dll or mod the point in DoPostUUT where it is called.  When the .exe is built does it pull in SequentialModel into the exe as a compiled piece of code or can I mod SequentialModel by itself and not have to re-build the .exe

[~jiggawax~]

---

@CoastalLabVIEWER wrote:

We'd like to change the "Test Sequence Passed" banner to something else and I know it's either mod modelsupport2.dll or mod the point in DoPostUUT where it is called.  When the .exe is built does it pull in SequentialModel into the exe as a compiled piece of code or can I mod SequentialModel by itself and not have to re-build the .exe

---

Override the PostUUT callback in your client file and you can do whatever you'd like without having to re-distribute or have a customized process model.