06-03-2010 06:29 PM
06-04-2010 01:54 AM
hi garya505,
while building the installer,you need to specify the folder in destination view of the installer properties..Since you want to include your wrapper dll ..so first youmust include in the project ,then while building specification for installer..you need to mention the destination for that dll as system folder and build the installer...So once the installer is built and if you install the application,then your dll will be in the system32 folder ..For more info...please go to
http://zone.ni.com/devzone/cda/tut/p/id/3303 ..
Thanks and regards,
srikrishnaNF
06-04-2010 11:32 AM
Thanks that helps. I managed to include the dll in the build and installer, but I had to use 2 separate build specs. Is it possible to do this with 1 build spec and 1 installer?
I can't find where to edit the destination folders. I can create folders under the [PersonalFolder] and [SystemFolder] but I don't know what the purpose of that is. Most of our files will go in our installation directory (not "C:\WINDOWS\Program Files"). I can't see where to set this directory.
Maybe I'll find it in the tutorial you pointed me to, but it's not intuitive.
06-04-2010 12:11 PM
06-04-2010 12:17 PM
06-04-2010 01:33 PM
garya505 wrote:
How do I change the [PersonalFolder] and [SystemFolder]?
Those are Microsoft Installer-defined folders, not Application Builder-defined ones. As far as I know there's no way to change them via the Application Builder. They map based on the operating system.
06-04-2010 01:41 PM
garya505 wrote:Thanks that helps. I managed to include the dll in the build and installer, but I had to use 2 separate build specs. Is it possible to do this with 1 build spec and 1 installer?
I can't find where to edit the destination folders. I can create folders under the [PersonalFolder] and [SystemFolder] but I don't know what the purpose of that is.
There should be no need for this. I have DLLs that go with the project installation, and I don't do anything special. The DLLs are in the project file, and in the build spec for the exe the "Support Directory" is set to the default, which is the "data" folder that resides in the same directory as the .exe file. As for the installer, again, nothing special done.
Most of our files will go in our installation directory (not "C:\WINDOWS\Program Files"). I can't see where to set this directory.
There is no such folder on standard Windows installations.
06-04-2010 02:21 PM
Ok, the dll will go in C:\WINDOWS\System32, but my Source Distribution needs to go in a directory that I specify. How do I do that?
06-04-2010 02:27 PM
During installation on my customer's computer, my dll will go in C:\WINDOWS\System32. However, my source VI files need to go in a directory that I specify.
I meant to say "C:\\Program Files". What I was saying is that my installation will probably not put any files in there. I may or may not have exe files that go in there, I don't know at this point.
I can't believe that LabVIEW will not put a set of files where I want them to go. That's ridiculus.
06-07-2010 11:59 AM
Good morning!
You can set your support files to install in a separate directory than your executable. In the build specifications for your EXE, select the Destinations category and change the path for the Support Directory to C\WINDOWS\System32 as shown below.
Then go the Source File Settings category and set your dll to install in the Support Directory, as shown below.
Let me know if this works!
Take care!