11-11-2008 03:59 PM
11-11-2008 04:15 PM - edited 11-11-2008 04:16 PM
11-12-2008 09:11 AM
Hello Steve,
What kind of functionality are you trying to achieve with the shortcut parameters? Does this functionality affect how the VI will be run when clicked on?
Please also reply with the version of LabVIEW you are using and the type of operating systems you will be deploying on.
Regards,
11-12-2008 09:21 AM
11-13-2008 06:05 AM
Hello Steve,
I am afraid I might be interpreting your posts incorrectly. In detail, please describe the process you have in mind to when installing, as well as the desired result on the target machine. In your first post you described using the LabVIEW installer. Does that mean that you are building an application with TestStand and LabVIEW for deployment? Or are describing installing from the original discs? Will the specific shortcut paths lead to files already on the machine, or will they be in the installation procedure?
I will appreciate the details you reply back with, as I do not want to propose a solution that will not work for you.
Regards,
11-13-2008 06:17 AM
11-13-2008 06:34 AM
I took another look and the .tsw teststand workspace does not let me view paths the way that the labview and cvi projects do and dates the way the cvi project does. Is there a way to turn this on for the workspace window? Does labview have a way of turning the dates on? It's useful in CVI to detect and repair missing files. Also, can the teststand workspace do a mass compile like labview can? If I can use the teststand workspace with the same amount of control I'll look into using it's deployment engine for future projects. Thanks.
11-14-2008 04:33 PM
Steve,
I've been monitoring this thread as well, and I am still unclear as to what your overall application is. If this is more of a question about how to use TestStand, then I suggest posting to the TestStand forum. If not, please post back with a broad level overview of the tasks you are looking to accomplish. Thanks, I look forward to hearing your response.
11-15-2008 12:19 AM
Hi Steve,
I don't know if it will help, but you can have the installer copy .bat files to the target - of course .bat files can do almost anything. Shortcuts can point to .bat files and it's also possible to have the installer copy an "internet shortcut" to the target station (Internet shortcuts have the "look and feel" of normal shortcuts.) Attached is a .txt file. Place it anywhere and rename it .url. Once renamed .url, it's harder to edit - I usually open a DOS window and use EDIT.
Note: this example assumes C:\Windows\Notepad.exe is a valid path to notepad.
Cheers!
08-13-2012 08:48 PM
This thread is kind of old. But my question is along the same lines as the first post.
Can you create a shortcut in labview installer that when installed on the desktop it will include arguments in the link?
I want to have the installer place a shortcut to a tftp server app. It requires a path as a argument. I would like the shortcut to run "c:\<apppath>\tftp.exe p /dc:\tftp"
I tried the shortcut.url trick from tdb and that worked for running tftp server. But i tried to figure out how to include the p /dc:\tftp argument with no luck.
Any ideas out there? tricks? hacks? I'm headed to idea exchange to post my labview shortcut parameters idea.
-Corey