NationalInstruments.UI Version 8.5 Widget vs. the GAC

[EWTech]

I'm trying to deploy an application that includes a NI scatterGraph function using ClickOnce deployment on a closed network. This is the way test software is delivered to clients in our lab and I've used this successfully in the past...until I tried Measurment Studio. The spacific message is:

"Unable to install or run the application. The application requires that assembly NationalInstruments.UI Version 8.5.20.220 be installed in the Global Assembly Cache (GAC) first.

The Measurment Studio help describes this but does not attempt to indicate a fix - making it worthless. I've done a web and NI site search on dealing with this and hours on this issue without success. I have a few options. I can continue to mess with this or use ZedGraph to do the same thing. I have code that works on my deevelopment box but can not be deployed and I'd like to make that available if it becomes needed without giving up my development PC but I'm told that this is needed soon.

The "manual" that came with Measurment studio indicated that there was one set of assemblies for Visual Studio 2005 and one for Visual Studio 2008. The version was 8.0.1 for VS2005 and 8.5 for VS2008. I'm starting to consider the possibility that the installer installed the wrong stuff on the development machine. Is this possible.

Bob

[EWTech · Accepted solution]

I was able to get this to work. The application has to have the NI widgets used deployed to the target folder in the Programs Files folder. This is OK if there is a single program using the NI stuff. In Visual Studio 2005 the Project Properties window determines what bits are deployed with the executable and what is not. For future versions of Measurment Studio a common location in the Programs Files folder might be a good idea in cases where more than one Measurement Studio program is deployed on a given system. I think of this as a "Driver" model where applications just check the license file in the target directory and the  look for the NI assemblies somewhere else. That way removeing one from the system doesn't break something else being used on the target machine.