Windows 7 Troubles

[G$]

I am having a great deal of trouble getting my C# application to run in Windows 7.  The application runs fine on Windows XP, and it runs fine on Windows 7 if I remove the Measurement Studio controls, i.e.. LEDs, but I can not for the life of me get it to run if they are left in.  I continuously get an error saying "Remote Interface.exe has stopped working.  Windows is checking for a solution to the problem..." and then the window closes in a matter of a few seconds.  I have included all of the .dll files that should be necessary and have spent the entire day searching these forums for anything else that I may be missing.  Any help would be greatly appreciated, as this is port is a major gating factor in my current development.  If any more information is needed, please just let me know.  Thank you so much in advance.

Regards,

Greg

[G$]

After perusing a few more of the posts here, I was led to check my registry system for the entries under National Instruments, only to find that none are being created (there is no National Instruments folder at all).  I am not sure if this is a problem, but it is additional information that I didn't have yesterday.  Also, I am including all the .msm files suggested in the merge module help documentation and have a System Folder and Program Files Folder in the File System structure of my setup project.  Finally, I have installed this using the Setup.exe file, as well as the .msi file, and I have run the Setup.exe file as an administrator, all to no avail.  Again, any help to lead me down the right path would be greatly appreciated as I am really stuck.  Thank you so much.

Greg

[D_Biel]

GMoney,

A few probing questions to get us started.

What version of Measurement Studio are you using? Does your XP machine have any NI software already installed? Do you have a clean XP computer to test the application on? Try making a really basic application that uses just one Measurement Studio control. Does this work in Windows 7?

[G$]

Hi,

I am using Measurement Studio 2010.  I have loaded the software in question, as well as several other pieces of software that I have developed, on a wide variety of Windows XP machines.  Some have had National Instruments software, such as Measurement and Automation Explorer, loaded on them and some have been clean of any National Instruments software at all, it made no difference as to whether or not the application ran smoothly.  

For comparison, I have tried a couple of different pieces of software that I have developed and that I know work on Windows XP, and I can not get anything to run on Windows 7.  Per your reccomendation, I have just tried the simplest of applications (with one standard C# button and one Measurement Studio LED) and have had the same issue as with all other applications, "Windows7TestApp.exe has stopped working.  Windows is checking for a solution to the problem..."  I then took the same exact software, doing nothing but deleting the LED from the window (even leaving the referenced National Instruments .msm modules), and loaded that onto the Windows 7 machine.  Without the LED, the application ran without a problem.

This has caused me such frustration over the last couple of days as I have tried every solution or suggestion that I could come across, all with no change.  Your input would be so greatly appreciated.

Thank you,

Greg

[G$]

Good morning,

I appreciate your time and attention on this matter, but I believe that I have it resolved.  In my search for an answer, I came across another post to these forums that mentioned changing the build platform target of the application to "x86" instead of "Any Computer".  This was mentioned to address another issue, but I figured that I had tried everything else I could think of, so I might as well give this idea a shot as well.  Sure enough, once I changed this setting my application began working just like it did on my XP machines.  The interesting part is that this setting seems to only affect the performance of applications that use Measurement Studio components, and not those without.  If you could make any statement as to why this behavior is present it would be a great help in understanding the inner workings of the software development tools and serve me well as I continue to make the switch to Windows 7 from the old familiar XP.

Thanks again,

Greg

[D_Biel]

Greg,

Are you running Windows 7 64-bit? The x86 setting specifies that the application will only use assemblies for 32-bit environment. This will force the application to run in the WOW on a 64-bit machine. It appears that your build was pulling x86 assemblies instead of MSIL and then trying to run as a 64-bit application. Check out this article on Visual Studio .NET Platform Target Explained. I don't have a good explaination for why that occurred, but if you are curious then you could create a fusion log and post it here.