Runtime Assembly Mismatch Issues after Upgrading Measurement Studio

[daringen]

After upgrading to MS8.6.1, I seem to be having several assembly mismatch issues when I try to deploy my web application to the server.  Everything runs fine on my development machine, but when I publish it to the server, it is still looking for NationalInstruments.UI Version 8.6.35.165 instead of 8.6.35.465.  I have deleted the references from my project and re-added them to ensure they have all been updated and searching my solution for '8.6.35.165' yields no results, so I'm not sure where in the binding process it is resolving to the old version.

The error output is as follows:

[Snowman 6008]

Darrington,

What version of Visual Studio are you ussing and are you able to compile and run any of the web shipping examples? C:\Documents and Settings\All Users\Documents\National Instruments\MStudioVS2008\DotNET\Examples\UI\WebForms  

[daringen]

Thanks for your reply.  I am using Visual Studio 2008.  I just attempted to compile and publish the example site to my web server.  The same thing occurs.  I can run the example site just fine in debug mode on my development machine, but when it is published to the server, it produces the same error: "Could not load file or assembly NationalInstruments.UI Version=8.6.35.165" even though the web.config references the updated version 8.6.35.465.  I have also tried deploying my web application via a web setup project with the merge modules instead of xcopy/publish to no avail.

[Snowman 6008]

Daringen,

Can you load up that DLL on the server using a .NET reflector such as http://www.red-gate.com/products/reflector/ ? That should trace any dependencies of the assembly and aslo let you know where they are located. This way you can make sure that you have the correct version of the DLL installed on your server and make sure it can locate all of its dependencies. 

[daringen]

I have resolved the issue.  It seems the application in the root directory of my server still referenced the old assemblies and since they all had the same name as the assemblies used by my new application in the virtual directory, it using the same ones when the binding occured.  Thanks for your assistance.