Use of Build Specifications for TestStand deployment Target

Hi everyone,
I currently use NI Internet Toolkit in one of my VI to build a code module for TestStand.
The matter is that de deployment target doesn't have the NI Internet Toolkit.
So I would like to build the VI in such a way the deployment target wouldn't need the Toolkit to use the VI.
Does anyone knows a way to that ?
Thanks to all...
Solved!
Go to Solution.

I got some matter with my outputs types (string array):
 - It generates an error while creating the dll with .NET interop.
 - Couldn't manage with share library .dll cause of array bounds couldn't be specified (array of array of char).
Thus I just change my data type to be of simple types, and it working quite well...
Thanks to Mr Dennis Knutson !

Similar Messages

  • Using LabVIEW Packed Library within TestStand Deployment Tool

    I am wondering what could be the interest of generating Packed Library within the TestStand Deployment Tool since the sequences using these VIs will not be able to find the dependant VIs included into the build Packed Library on the deployment target.
    Any experience using Packed Library within TestStand Deployment Tool ?
    Jean-Louis SCHRICKE
    ├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
    ├ CTD - Certified TestStand Developer (2004 & 2007)
    └ CLD - Certified LabVIEW Developer (2003 & 2005)

    Jiggawax,
    Sorry for the confusion,
    My question concerns the developement of Custom Step Types.
    For example, within a project or as an independant product.
    The best practices is to avoid using main module when developing CST in order to preserve evolutivity (main module calling paramters are copied within CST instances and could need prototype updating). I prefer using PostStep (as NI does for its own CST).
    Thus, when creating the CST palette, I have to configure the EditStep and the PostStep and define each VI call.
    If I want to distribute these VIs through a .lvlibp, then I need to build a .lvlibp very early and use it within my CST palette.
    This .lvlibp will be used on deployed benches and may not contain VI diagrams and debug options (best performance).
    But during the development of my CSTs, if I need to debug the VIs called when using CST whitin a sequence, and if I don't want to change the called VIs defined in my CST palette, then I need to regenerate this .lvlibp with debug option (different from the deployment .lvlibp) in order to allow debug.
    May be it could be interesting that the TestStand deployment tool take into account SubSteps when selecting the Packed Library option. This tool is able to modify sequences, it could be able to change also palette configuration file.
    This will allow to have only two levels :
     > Source and Debug (VIs)
     > Deployment (.lvlibp)
    instead of three :
     > Source (VIs)
     > Debug (.lvlibp with debug option)
     > Deployment (.lvlibp)
    Jean-Louis SCHRICKE
    ├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
    ├ CTD - Certified TestStand Developer (2004 & 2007)
    └ CLD - Certified LabVIEW Developer (2003 & 2005)

  • Is LabVIEW application builder needed for TS deployment?

    Does the LabVIEW application builder need to be installed for TS deployment of a project containing LabVIEW VI's?

    LabVIEW Application Builder is only necessary if you are deploying LabVIEW files, even then you can use the flag "Include without Processing Item or Dependencies" in all your LabVIEW files to create an image and optionally an installer without requiring LabVIEW (or app builder) at all; however, using this flag is not recommended becuase if you use it you would have to include all the files and their dependencies in your deployment manually (either by including the root directory of your test system or by adding all the files to your workspace) and you would have to make sure that they are not broken and can be called from the run-time engines you are including in your installer. 

  • Would you use Flash Builder Beta2 for production project?

    i am currently developing a project in Flash Builder beta2 with flex 4 sdk with the new spark components.
    But as i can see not all mx components have a spark equivalent and in my bin-debug folder there are
    spark_4.0.0.10485.swf 431,927  bytes
    rpc_4.0.0.10485.swf 206,435  bytes
    framework_4.0.0.10485.swf 1,018,863  bytes
    without taking in mind my main application file sizes.
    An i am wondering will my project that use a mix of mx and spark components will have to load the hole frameworks?

    i've got the same pb... any ideas ?

  • Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile

    When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the cRIO application is built? I searched through the help and in these forums, but I don't see criteria for selecting one over the others; maybe I missed it.

    Hello Chris,
    Apologies in advance for a long reply.  
    The reference method won't change the functionality of your rtexe.exe.  They all end up dropping a bitstream, based on a bitfile, onto the cRIO's FPGA.
    To a degree, the method used to reference the FPGA code is a matter of taste, but there are situations where one method is better suited than the others.
    Reference by VI:
    Setting the configuration options to open reference by VI is helpful during development when you are making changes to an FPGA VI often and building/testing using the same spec.  When this option is used, a bitfile is selected based on the default build specification for the project.  A project may have only one default build specification.  You can make any build the default by checking the option under the Source Files category in the build properties.  The default build is indicated in the project explorer by the green box around the builds icon.  
    Reference by Bitfile:
    This option references a bitfile directly.  Through the configuration window, you can select one specific bitfile to open a reference to (this is not dynamic and does not change unless you physically go make a change to that path).  If you're using this method, it helps to give your bitfiles more meaningful names than the ones that are automatically generated by LabVIEW.  When you run subsequent compilations off of the same build specification and do not change the bitfile nname or path in the build configuration, the old bitfile is overwritten and replaced with the new one.  When you are using this option, it is critical that you keep up with which bitfile is the one you want to be using.  There is an option now that will help alleviate any problems referencing by bitfile through the Open FPGA VI Reference function.  There is a new VI called Open Dynamic Bitfile Reference.  It is typically used when you want to chose a specific bitfile to load depending on something in your host code (a configuration option etc) - but it allows you to dynamically reference a bitfile on the block diagram by path.
    Referency by Build Specification:
    This option is good for when you want to always use a bitfile that is associated with/compiled with the same build configuration.  Say you have two options for top level FPGA VIs in your project (each with its own build spec).  Both of these VIs have the same interface (read/write controls, DMA) but they run different algorithms or something.  This is nice because you can easily switch your host application between them by picking the build spec associated with the FPGA VI you want to use.  In this type of sutation, referencing by VI is no good because you can only have on default build spec.
    cheers.
    Matthew H.
    Applications Engineer
    National Instruments

  • Use Flash Builder to Develop Adobe AIR Apps for Android | Flash Platform in Action | Adobe TV

    Former Adobe Technical Evangelist Ted Patrick uses Flash Builder to develop and deploy an Adobe AIR application to his Android-powered smartphone.
    http://adobe.ly/wif9U5

    autoplay can cause a tremendous amount of problems for site visitors. is it possible that adobe might turn off autoplay?

  • Build Specification does not include all files for my VI.

    Hi!
    As a part of a semester project i have build a VI to control a filtration unit. The VI is working fine on my computer, but I graduate next month and I have to deliver the files on to a person on the university. The problem is that even though i use the "Build Specification" function (i use LabView 2011 Professional Development System), files are still missing when the program is started on the new computer. A warning in the project file indicates that files are missing or removed to a different location. A file named pid.lib is not found, and it seems like the path to each file is the same as on my computer, but the build specification doesn't change that to fit the new computer.
    I am a LabView newbe, and I have searced this forum and help files to try to solve this by my self, but now my time is becoming limited. Can anyone help me with this?
    Henrik jepsen
    Masterstudent Chemical Enginnering
    Denmark
    Solved!
    Go to Solution.

    Hi Henrik
    You can see what versions of LabVIEW and which Toolkits is installed in Measurement and Automation Explorer (MAX). If you Open MAX, and Select "My System" --> "Software in the left menu, then you can see all software installed.
    If you click on the LabVIEW installation. In this case LabVIEW 2011, you can see all toolkits installed.
    When you run a LabVIEW project / application on another PC, LabVIEW will use a defined priority of where to load the files from. This is specified in Tools --> Options --> Path --> VI Search Path.
    So LabVIEW will frist try to find the VI/VI library in the folder of your project and if the VI is not located there it will look for it as a build function in the vilib, userlib or instrlib folders of LabVIEW. These folders contains VI's and VI libraries installed with LabVIEW.
    In this case, as mentioned above you properly don't have the same toolkits installed on both machines. Therefore the PID.lib is not found in the vilib folder as it should be, and thereby you get the error. You can confirm this by reviewing the installed modules as mentioned above.
    Best Regards
    Anders Rohde
    Applications Engineer
    National Instruments Denmark

  • Query for recurring reports using Query Builder in Business objects

    1. How to count webi Recurring reports using query builder in business objects? (Need Query for this)
    2. How to count Crystal Recurring reports using query builder in business objects? (Need Query for this)
    I am able to get summerized recurring reports using Query Builder.
    For Example we have 343 reports which are under recurring (This includes both Webi Reports and Crystal Reports).
    we need to get individually how many webi reports are under Recurring and Crystal reports are under Recurring.

    1. How to count webi Recurring reports using query builder in business objects? (Need Query for this)
    2. How to count Crystal Recurring reports using query builder in business objects? (Need Query for this)
    I am able to get summerized recurring reports using Query Builder.
    For Example we have 343 reports which are under recurring (This includes both Webi Reports and Crystal Reports).
    we need to get individually how many webi reports are under Recurring and Crystal reports are under Recurring.

  • TestStand Deployment problems on Windows 2K3 x64

    Greeings:
    I'm hoping someone out there can advise me.
    I recently tried building a TS application to deploy on a server running WIndows Server 2003 x64, and I have run into a few difficulties.  On my development system, (32-bit WInXP pro) I built a TS Deployment installer.  I transfered it to the destination machine.  Installation failed ... it said that numerous files were missing from different CAB files.  I tried again ...  the second time I had better luck ... the installation seemed to take.  Using the License Manager, I activated my installation using my development license (my deployment license hasn't arrived yet).  I tried launching my application, and I get an exception that seems to indicate the ActiveX dlls aren't registered:
    Unhandled Exception: System.Runtime.InteropServices.COMException (0x80040154): C
    lass not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
       at System.Windows.Forms.UnsafeNativeMethods.CoCreateI​nstance(Guid& clsid, Obj
    ect punkOuter, Int32 context, Guid& iid)
    I tried registering these manually using
    regsvr32 "D:\Program Files\National Instruments\TestStand 4.1\API\DotNet\Assemblies\CurrentVersion\NationalI​nstruments.TestStand.Interop.UI.AxControls.dll"
    but it complains that this DLL has no DllRegisterServer entry point.  (Is it the wrong DLL to register?)
     I tried uninstalling my deployment and installing the full teststand ... and SeqEdit seems to run properly.  (It must have registered the required DLLs, no?)  My app, on the other hand, still does not run. I am trying to install Visual Studio to see if I can rebuild the application on this system with better results.
    Have I missed an important step?
    Thanks!
    Tom MacLean
    Solved!
    Go to Solution.

    LabCat,
    That's correct.  If you have the build set as Any Platform, when you install that on a 64-bit machine, the project will try to load the 64-bit versions of those assemblies, which don't exist.  You have to make sure your project is building specifically for x86 so it will run properly on a 64-bit machine.  I believe TestStand 4.2 or 4.2.1 ships with OIs that have this set as the default setting in the .NET OI source code, but your earlier version may not have had that corrected.
    Eric B.
    National Instruments

  • Assessing Command 'Analyze Source Files' via Command Line when running TestSTand Deployment Utility

    Our Software Configuration Manager is running the TestStand Command Line Deployment Build Tool (Ref: https://decibel.ni.com/content/docs/DOC-38947).
            When he builds the application,  the code will not be at the same location it was in development. 
    If you are Manually running the TestStand Deployment Utility, This is not a problem because everything is relative in the workspace.   Simply go to the Distributed Files Tab (of TestSTand Deployment Utility) and hit the, "Analyze Source Files" button.  This finds the required files and apparently creates an updated hard path to be used during the build (probably in the *.tsd).
    PROBLEM:  We auto-run the Command Line Deployment Build Tool (Command Line), and we do not have access to the, 'Analyze Source Files' command.
                As a result, our build consist of many warnings and the output is missing many files (the location of the files have not been updated).
    If we could access the 'Analyze Source Files' Command via command line, that would fix the issue. 
    FYI:  We use an automatic builder called Quick Build as our builder.
    Attachments:
    TestSTand Deployment Utility-Distributed Files Tab.PNG ‏76 KB

    Unfortunately it looks like Analyze Source Files does not have a command equivalent for the command line based on this article and attached PDF:
    https://decibel.ni.com/content/docs/DOC-38947
    That may be a good post for the TestStand Idea Exchange for consideration in future versions of TestStand.
    Michael K.

  • What is the significance of the Assembly Deployment Target and Feature Scope?

    Hello,
    We have created a project as Farm Solution (not sandbox).
    Under project properties we can see an option for Assembly Deployment Target : GAC or WebApplication.
    I know that GAC will deploy the dll to windows\assemblies and WebApplication will deploy to website/bin folder.
    Now, we add a feature to the project; in here we can see a dropdown for scope with options as: Farm; Web; Site; WebApplication. I know that depending upon what option is chosen; the feature can then be activated by going to the respective manage features
    option via SharePoint front end UI.
    Can you tell me what is the significance of the Assembly Deployment Target and Feature Scope?

    >>Can you tell me what is the significance of the Assembly Deployment Target and Feature Scope?
    Feature scope can be decided based on the type of artifacts you will be building
    Check the below link for what type of artifacts can be build at different levels of scopes
    http://msdn.microsoft.com/en-us/library/ms454835(v=office.14).aspx
     wrt to Assembly Deployment Target depends on what type of components you are deploying through your solution which will be specified in manifest.xml. There are advantages
    if you deploy the components to web application rather GAC like all Apppools will not get recycled, avoiding IIS reset etc. But if you have 3rd party dlls and feature receivers which need to deployed along with the solution then its advisable to deploy to
    GAC
    http://trentacular.com/2009/06/sharepoint-differences-between-global-and-web-application-targeted-solution-deployment/
    https://www.captechconsulting.com/blog/james-brocato/sharepoint-without-the-gac
    Hope this helps.
    My Blog- http://www.sharepoint-journey.com|
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

  • Exporting build specifications to other project

    Hai all,
    I have created the build specification for developing a exe in my project.  There are too many destination directories am creating in the project and its a lengthy process too.  Is there a way to export the build specifications (of a exe) to another project and reuse the specification there.
    I am using LabVIEW 8.5 Professional development system.
    Previous versions of LabVIEW has *.bld file that can be called while creating new exe's is there any such option in 8.5
    With regards,
    JK
    With regards,
    JK
    (Certified LabVIEW Developer)
    Give Kudos for Good Answers, and Mark it a solution if your problem is solved.

    Hi JK,
    you can open your project file with a normal editor. It is a xml file. There is an item with name = build specification. If you copy this part to another project, then it shall be possible to use it there.
    Hope it helps.
    Mike

  • Build specifications gone

    LV 8.5 on XP Pro
    I have a project with the build specifications for an executable.  The problem is that the startup VI's that are designated in the properties keep coming up missing.  The ICON is still in the project, but when I go into the "source files" they do not seem to save.  The problem is intermittent.  I have tried entering the properties, saving and then closing and reopening LV and had no problems but then the next time I go to do a build I receive error "You did not specify any Startup VI's." 
    Also the installer properties continually are corrupted and I have to re-create the installer.
    Any suggestions?
    ~gold 

    Hey Gold,
    Thank you for contacting National Instruments.  I'm not exactly sure if I understand your problem, so I do want to clarify what you have going on.
    If I understand you correctly, you have a project with VI, documentation, etc, to create an exe as well as an installer.  All files appear in the project explorer, and there does not appear to be any problems with the files there.  When you go to build an exe, you select your startup VIs, and move them into the Startup VI's section of the build page.  When you go to click build, you get an error that you have not selected any startup VI's.  Is this correct? Are there any details you would like to add to that?
    Also, can you please explain what you mean when you say the installer seems to be corrupted?  Can you give any error messages, or a better description of what is going on?
    Thanks,
    Kevin H
    National Instruments
    WSN/Wireless DAQ Product Support Engineer

  • [svn] 3158: -integrate AIR build 20080905ap for windows and mac

    Revision: 3158
    Author: [email protected]
    Date: 2008-09-09 12:16:23 -0700 (Tue, 09 Sep 2008)
    Log Message:
    -integrate AIR build 20080905ap for windows and mac
    -update air-config.xml to target Player 10: bug: https://bugs.adobe.com/jira/browse/SDK-16417
    -fix air-config.xml; modified the external library-path: bug: https://bugs.adobe.com/jira/browse/SDK-16732
    -fix build.xml so the web installers are included in the sdk package, no bug
    -update frameworks/projects/airframework/build.xml for AIR to target player 10
    -updaet build_framework.xml for AIR to target player 10
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-16417
    http://bugs.adobe.com/jira/browse/SDK-16732
    Modified Paths:
    flex/sdk/trunk/build.xml
    flex/sdk/trunk/frameworks/air-config.xml
    flex/sdk/trunk/frameworks/build_framework.xml
    flex/sdk/trunk/frameworks/projects/airframework/build.xml
    flex/sdk/trunk/in/air/air_version.txt
    flex/sdk/trunk/in/air/mac/AIR Integration Kit.tbz2
    flex/sdk/trunk/in/air/win/AIR Integration Kit.zip

    This is from a tester describing what happens on a Mac:
    No the program does not launch properly on the Mac
    What happens is this.
    I open my applications folder
    I open the App Folder and see another folder labeled Program V2.1
    I open that folder and see the Program blue icon which click to launch
    The folder disappears and the blue Program icon appears in my dock along side other applications looking ready for launching.
    This is where the problem starts
    If I click on the blue Program icon which is in my dock along side all of my other application icons they all drop off the screen. like the screen resolution changed suddenly or something,
    The menu along the top of the screen also moves off the screen . in the same manner
    so my desktop which usually has a visible dock at the bottom and a menu bar on the top now doesn't show either of those elements.
    I do have a couple of document icons on my desktop , you know text files or what ever they never move
    If I now click my mouse anywhere on the screen all of the icons return including the blue Program icon still sitting in by dock, if I click it again same sequence of actions.
    I deleted and reinstalled the latest version of Adobe Air and got the same result
    I also want to mention
    The top menu on the mac tells me what application is active, you know "finder" "Open office" "Firefox" what ever is program is running and active shows there
    Program has never show up as being active in the top menu so I'm guessing never fully launched

  • Deploy user for automatic deployment on development system

    Hi everybody,
    I am not sure what user to configure in the "Runtime Systems" tab of my track configurations.
    We use AS Javas of the Version 7.1 EHP1 as runtime systems. Thus we use the deploy controller for deploying. So far we just have used the personal user of whoever created the track as deploy user. Is this the recommended way? Or should we better use some technical user for automatic deployment? If yes, which permissions should this user have?
    Thanks in advance for your help!
    Tobias

    Hi Satya
    Thanks for the quick answer. Do you happen to know if a separate technical user for CMS deployment ist the "standard"/best practice?
    Best regards,
    Tobias

Maybe you are looking for