deployment missing DLL

[JÞB]

OK, I'll ask.  What are we doing wrong in our deployments?

We do use a custom model that leverages xml files for....many things.

Steps to reproduce:

Deploy a Workspace that dependeds on xml for a workspace that contains a Lvproj that does not use DOMuserDefRef.dll (Athough the model does) and all vi's that use xml are broken.  Not the vi's in the workspace lvproj.   The model custom vi's, including those in vi.lib!

Add Dummy.vi to open and close a xml file to the LabVIEW project and the vi.lib vi's are no longer broken... but the model vi's are!  The deployment still fails.

Add the Dummy.vi to the TS Workspace, the Dummy.vi and the model.vis are broken.

Add Step.DummyAction to MainSequence with a call to Dummy.vi (do not report) all is well........

I really would like an explaination of what we could do better.

[Norbert_B]

Jeff,

i don't know if this is connected by any means, but there is some coincidence.

Does it help?

Norbert

[JÞB]

---

@Norbert_B wrote:

Jeff,

i don't know if this is connected by any means, but there is some coincidence.

Does it help?

Norbert

---

Not really, I have a work-around.  So, for right now I good (Meaning it only took 3 man days to deploy what should have work the first time )

Does it help NI to resolve the issue?

"Jinkies! a clue." - Velma Dinkley

[Norbert_B]

---

@Jeff Bohrer wrote:
[...]Does it help NI to resolve the issue?

"Jinkies! a clue." - Velma Dinkley

---

Well, maybe if you describe your workaround 🙂

Is it something like using LV to precreate a source distribution?

thanks,

Norbert

[JÞB]

Add ID10T.vi to the TestStand Workspace. Make sure the workspace sequence calls ID10T.vi

For example in MainSequence:

 Add Step

 Dummy (Action) ID10T.vi on MyProject.

SR is on the way with greater detail

[Norbert_B]

Just another possible way: What happens if you put that XML functionality for your project into a PPL?

Norbert

[JÞB]

---

@Norbert_B wrote:

Just another possible way: What happens if you put that XML functionality for your project into a PPL?

Norbert

---

I really don't know.  Again, our deployment practices here could benefit from some education.  (The environment is almost always "Deploy a 1-off sequence on TestStand Model X to a new hard-drive" ) The developers on site are primarily EEs and aren't really concerned about source distributions or packed libraries they just want to give the production floor a tool to use to test product for a while.