Why won't my vi run outside of the LV2011 project explorer?

[JG-MACK]

I've created a LV2011 project. The vi's within this project open executables to perform measurement functions. When I open the vi's from within the project explorer window the executables open with no issues. However, with the LV project closed and opening the vi's from "windows explorer" the executables won't launch. It seems like I need to have the LV project explorer window open. However that does not work very well in a manufacturing environment. What is the dependency relationship of running vi's in or out of the LV project? How can I remove this dependence?

[crossrulz]

---

@JGmitter wrote:

However that does not work very well in a manufacturing environment.

---

You shouldn't even have LabVIEW on the floor of a manufacturing environment.  You should be building executables from your LabVIEW code and those should be on the floor.

Can you share any of your code?  Are you getting any errors?

[JG-MACK]

crossrulz,

Good point.  Nice to run executables and I agree.  In a perfecct world thats what would happen.  Do you know what the constraints are for vis in a LV project?  Here is the error:

Error 1172 occurred at Error calling method Class.Initialize, (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
    Inner Exception: System.Runtime.InteropServices.COM Exception:  An error has occurred in the vi. More information may be available in the Windows Event log.
Creating vi)

Possible reason(s):

LabVIEW:  A .NET exception occurred in an external assembly. For information about correcting this error, copy the following exception (in bold), and search the Microsoft Developer Network (MSDN) Web site or the Web for a possible explanation.
System.Runtime.InteropServices.COM Exception in Open apps.vi->Example.vi

[tyk007]

Have you read this?

http://zone.ni.com/reference/en-XX/help/371361J-01/lvconcepts/loading_assemblies/

[Dennis_Knutson]

Why on earth would you spend the money for a development system on each production pc instead of building an exe? Do you actually have that many licenses? I don't think a perfect world is an apt description.

[JG-MACK]

Dennis,

The customer has an enterprise software license agreement.  They tend to do a very long new product introduction.  30% of the design is finalized / tweaked in low volume manufacturing.  Yea, its kind of silly but that’s how they do it.  So I take it you don't know the answers to my questions?

[JG-MACK]

tyk007,

Thanks that was helpful.  I added the root C: directory to the search paths with no luck.  😞  Thanks though.

[tyk007]

---

@JG-MACK wrote:

@tyk007

Thanks that was helpful.  I added the root C: directory to the search paths with no luck.  😞  Thanks though.

---

If you read through that help item then you probably realise that Fusion will start locating your assemblies from the LabVIEW executable path (eg. C:\Program Files\National Instruments\LabVIEW) if you load without a project. Adding search paths to the labVIEW environment will make no difference; LabVIEW is not the one performing the search - the CLR is.

This is why NI strongly recommend a project - this adds your project folder where your lvproj lives to Fusion's search path.

If you don't want to budge from using teh development environment - and don't want to add the .NET assemblies to the LabVIEW folder, then you could add them to the GAC if they are signed. The GAC is always in Fusion's search path.

[JG-MACK]

TYK007,

Thanks for the info.  🙂

"If you don't want to budge from using teh development environment - and don't want to add the .NET assemblies to the LabVIEW folder, then you could add them to the GAC if they are signed. The GAC is always in Fusion's search path."

I need to do some research on fusion and the GAC.  I have not had to use these tools as of yet.  Do you have any good step by step resources?

[tyk007]

---

@JG-MACK wrote:

TYK007,

Thanks for the info.  🙂

"If you don't want to budge from using teh development environment - and don't want to add the .NET assemblies to the LabVIEW folder, then you could add them to the GAC if they are signed. The GAC is always in Fusion's search path."

I need to do some research on fusion and the GAC.  I have not had to use these tools as of yet.  Do you have any good step by step resources?

---

It might be best to check to see if it is a fusion loading problem first. You should be able to error the error messages in Event Viewer. What do you see there?