User Library Distribution

[kevin.key]

Hey,

I'd like to create a distribution for a library I've created and there are a couple of things I'd like the installer to do, but I'm not sure exactly how:

Add the library to the CVI libraries list

Add User defined tokens

Also, it's a RT DLL I want to share is there a way to make it installable to the RT in max?

---------------------------------

I found this directory:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\National Instruments\CVI\Shared\AutoloadLibraries

that seems like the place I want to add a string to, but is that specific to Win7 x64?

And can I set a Registry Value equal to one of the defined directory's plus another string?

And how does CVI find the header file and lib file associated with the function tree?

---------------------------------

I haven't seemed to locate where User defined tokens are stored.

[Josh_L1]

Hi Kevin,

Thank you for bringing this question to our attention. To answer your first two questions, I think what you need is to generate function trees. I have a tutorial link below for your reference. 

http://zone.ni.com/devzone/cda/tut/p/id/6503

You can permanently add dlls and user defined tokens by first creating the function tree. Once the function panels have been created, you just need to right click on Libraries and choose Customize Library Menu > browse and choose the function tree you just generated. This will add the dlls and user defined tokens into the library list.

In regard to your third question, I'm a little confused. MAX is basically a device/program manager for NI products. Are you trying to port device configurations into MAX? As far as installing a dll to MAX is concerned, that is not possible. However, if you could clarify your question a bit, maybe we can figure out a workaround.

Regards,

Josh L.

[Josh_L1]

Hi Kevin,

I just want to make one correction on my post. I've been informed by our R&D Engineers that you can install RT dll through MAX (not into MAX). Are you trying to automatically install the dlls to the target RT system? A few clarification from you will still be much appreciated.

Regards,

Josh L.

[kevin.key]

I've already created a Function Tree. I know how to add a library and user defined tokens to the CVI environment on my pc. What I would like to do is create a distribution that installs the function tree and user defined tokens to someone elses pc without them having to manually add the function tree and user defined tokens to their CVI environment. I'm also curious if I can add the DLL to someone's list of software to install to an RT using the Add/Remove software dialog in MAX.

[Josh_L1]

Hi Kevin,

I found this article you might find useful. I still need to figure out how to incorporate it into an installer. Regarding your question on adding DLLs to MAX, you cannot add the DLL to the Add/Remove software dialog. However, you can choose File Transfer by right clicking on an instrument under Remote Systems in MAX. This option will allow you to add DLLs to the hardware.

I hope this helps.

Josh L.

[kevin.key]

Right, I know how to add a library to my CVI environment. What I'd like to do is modify someone's CVI environment with an installer.

The goal would be: They run the installer. They open CVI and notice that the Library has been added to their list of Libraries and that User Defined tokens have been added to their list of User defined tokens.

[Josh_L1]

Hi Kevin,

Sorry for the late response. I did a little more digging. You are correct in your original post. In order to install the custom library and DLLs to the target machine, you just need to include the registry key mentioned in your first post. However, I don't think you will need to use the Wow6432Node path. I believe CVI automatically defaults to that path if it's a 64 bit system. 

I hope this helps.

Regards,

Josh L.

[LuisG]

Kevin,

Josh's response is correct but, if you are creating your distibution with CVI's Edit Distribution tool, you need to make sure that you create a 32-bit distribution:

... otherwise, the installer would create the registry in the 64-bit hive, which would not work for you.

Luis

[LuisG]

<remove duplicate post>