problem deploying NI User Interface library

[Penny]

Hi,

Something very strange is going on.  All of a sudden my VS 2008 with MS 2009 projects are not deploying properly.  (They were as of several weeks ago.)  The warnings are:  

 Warning    1    Unable to find module dependency with signature 'Microsoft_VC90_CRT_x86.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC'    C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\SimpleReadWrite\SimpleTestProject\Setup7\Setup7.vdproj 

 Warning    2    Unable to find module dependency with signature 'Microsoft_VC90_ATL_x86.240CE762_0ECF_3EA9_9B88_59EFA15C781A'    C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\SimpleReadWrite\SimpleTestProject\Setup7\Setup7.vdproj 

So I wrote a very simple project that consists of just one button that brings up a MessageBox - nothing more.  It builds, executes, and deploys fine until I include the NI User Interface library, with:

using NationalInstruments.UI;

with the corresponding reference to NationalInstruments.UI .   Then I get the above warnings.

I Googled the knowledge base at http://digital.ni.com/public.nsf/allkb/961CB182B0F3C2EE8625755F0066A47D that suggests Service Pack 1 for VS 2008 for this exact error, so I reinstalled Service Pack 1 to be sure.  It did not seem to change anything.  

The only thing I can think of is that my Windows automatic updates have done something unexpected.  Does anyone have any ideas on this?

Thanks,

Penny

[Anna_K.]

Hello Penny,

Another customer had previously seen this problem and they had to reinstall SP1 and indeed once they had ran a Windows updated they problem returned. Here is a log of their steps. Try reinstalling SP1 and let us know the state of the signatures:

After SP1 re-install (VS90sp1-KB945140-ENU.exe) the files were re-created with these signatures:
Microsoft_VC90_CRT_x86.msm
{D8D85FD0-537C-3A3A-9BEC-7A1B426637EC}
Microsoft_VC90_ATL_x86.msm
{240CE762-0ECF-3EA9-9B88-59EFA15C781A}
The problem:
WARNING: Unable to find module dependency with signature 'Microsoft_VC90_CRT_x86.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC'
WARNING: Unable to find module dependency with signature 'Microsoft_VC90_ATL_x86.240CE762_0ECF_3EA9_9B88_59EFA15C781A'
was solved.

After SP1 update from Windows Update (Security Update for Microsoft Visual Studio 2008 Service Pack 1 (KB971092)) the files were re-created with these signatures:
Microsoft_VC90_CRT_x86.msm
{AA2EBBCC-4E3B-3442-865E-7BB3E9F45F0C}
Microsoft_VC90_ATL_x86.msm
{0901F145-82C9-3BF6-A91B-31F6791950EA}

The problem re-appeared.

I had previously saved a copy of the files with the signatures Visual Studio was looking for. I copied the files into the 'C:\Program Files\Common Files\Merge Modules' directory, over-writing the files with the wrong signatures.
The problem was again solved.

[Anna_K.]

Remember to keep a separate copy with the files with the correct signatures before any updates are run in case the updates over-write the files to a different signature.

Thanks,

Anna K.

[Penny]

Hi Anna,

Thanks for that info.  I checked the signature values of the two files, and they are the updated values (the ones that VS does not want):

{AA2EBBCC-4E3B-3442-865E-7BB3E9F45F0C}
{0901F145-82C9-3BF6-A91B-31F6791950EA}

I reinstalled Visual Studio Service Pack 1 (VS90sp1-KB945140-ENU.exe) and the signatures did not change.  Perhaps it has to be uninstalled first, and then reinstalled?  I am not presently sure how to do that.

I notice that the other customer had to overwrite the two files manually to fix the problem.  Is there any chance I could get copies of those files?  Or, should I try a 'System Restore' to retrieve them?

Thanks,

Penny

[Penny]

Hi Anna,

So I did uninstall VS 2008 SP1 (Add/Remove Programs with 'Show Updates' box checked) and then reinstall it, and it did fix the problem.  The signature values are now correct and the build error is gone.  So thank you for the assistance!

Best regards,

Penny

[Anna_K.]

Hello Penny,

Thats great to hear! One last thing, perhaps save a backup copy of th files just in case.

Have a great day,

Anna K.