My program does not install properly in Windows 7. The National Instruments files do not install.

[Pete@ITC]

Hello,

I have tried installation as an administrator and that did not work.  The National Instruments directory under Programs does not appear and the registry under HKEY_LOCAL_MACHINE>>SOFTWARE>>National Instruments does not show up either.

Also my LED's don't appear on the form, which may be a minor point or may be significant.

Thank you.

Pete M

[D_Biel]

Are you getting any errors during installation? What leads you to believe it is not installed properly? Note that the installation on Windows 7 may looks slightly different from Windows XP, because of the differing file structure. Is this occurring with NI software? Is this a Measurement Studio deployment or the Measurement Studio development environment? What LEDs are you referring to? Is that part of your application you are installing?

Edit: Also what version of Measurement Studio are you using? If this is a deployment, what operating system did you develop on? Are your development and target system 64-bit or 32-bit?

[bnils]

There is a thread about invisible LEDs, see http://forums.ni.com/t5/Measurement-Studio-for-NET/Blank-LED-Indicator-On-Windows-7/td-p/1135185

It may be the same problem!?

Best regards, Björn Nilsson

[Pete@ITC]

I am trying to install software on a netbook.  I am using the netbook because of its small size for a product we are developing.

The operating system is Windows 7 Starter on a 32 bit machine.  There are no errors for the install when I run as administrator (right click on setup.exe of program).  The program starts and works fine until it runs into a module that uses a National Instruments sub routine.  When I comment out the NI section and reinstall, it works in that module.  This is a Measurement Studio Deployment compiled under Visual Basic 2008 Standard Edition.

I followed the thread on the LED that was in the second reply to my question. These are NI LEDs from the toolbox. When I check the registry for the National Instruments sub folder, it does not show up where it is supposed to be according to the link.  (It does show up there on XP machines where the program does work.)  There is no folder under c:\program files for National Instruments either. 

As far as the statement about merge modules in that link, I think I have all of the NI .dll's that appear under my program's properties - publish folder.  I found that I had to override the publish status from "prerequisite(auto)" to "include" to get the program to install properly on XP and Vista machines.  I tried that on Windows 7 Starter but no success.

[D_Biel]

Make sure you are included the merge modules for all the references. The list in the publish is not necessarily what is going to be deployed. You can find what merge modules you need by looking in the help documentation at navigate to NI Measurement Studio Help>>Deploying Applications>>Merge Modules and Deployment Files>>.NET Merge Modules. Follow all the steps listed there to include your merge modules.

[Pete@ITC]

Thank you.

I tried that but it still did not work.  There are still no registry entries for National Instruments on the target machine after the install.  There are some but not all of the merge modules.

I was able to try another netbook, this one with XP as the operating system, and that did not work either.  It did work without this change on two other regular notebooks and a pc using Vista Professional

Pete@ITC

[D_Biel]

I was able to reproduce the behavior you were experiencing with your Windows 7 Deployment. I am going to be filing a bug report so that our R&D group can investigate this further. In the meantime, there are two workarounds.

1. Running setup.exe as administrator will give the installer the permissions necessary to add the registry keys that will link the MESA.dll.

2. You can edit the .vdproj file that is built with the installer. Search for the line "RequiresElevation" = "11:FALSE" and change the value to "11:TRUE". This will make the installer ask for administrative priviledges to run. You can read more about this under the Application Elevation topic here.

Thank you for your patience and feedback. Please let me know if you have any questions.

[Pete@ITC]

Thank you.

I have already tried workaround number 1 several times and that does not work.

For workaround number 2, I assume you mean .vbproj not .vdproj.  I could not find the entry for "requireselevation".  Could that be because I am publishing the program from a Windows XP based machine?

Pete@ITC

[D_Biel]

Pete,

I did actually mean .vdproj. This is a file in your setup project, not your application project. When you build a deployment with Visual Studio you must create and add a setup project to your solution. This is where you will find the vdproj. It may be in a different directory than your application.

[Pete@ITC]

Thank you.

Your latest reply may be a useful clue.  I publish from the "Properties" window of my application.  Taking this route, a file with the extension .vdproj is not generated.  I have over 50 programs that were published in this way, but only one generated a .vdproj file and I can't figure out why it is the exception.  There is both a "Publish" directory and a "My Installer" directory for that application and it was an intermediate version of the solution. Prior and later versions do not show a "My Application" folder.

Pete@ITC