locked
Redistributing MSXML4 RRS feed

  • Question

  • Hi,

    I have written an application which is redistributed via an MSI. I merge in the MSXML4 merge modules.

    I have discovered that if I add a manifest assembly reference as follows:

    /manifestdependency:type='win32' name='Microsoft.MSXML2' version='4.20.9818.0' processorArchitecture='x86' publicKeyToken='6bd6b9abf345378f' language='*'

    My app doesn't work. I think that this is because these DLLs already exist in the C:\WINDOWS\SYSTEM32 directory and it is not installing them into C:\Windows\WinSxS. Shouldn't the merge module detect this and install into  both places?

     

    Thanks

    Mark

    Thursday, March 2, 2006 6:55 PM

Answers

  • Thank you for the result files.  I received it. 

    I checked the setup log file, and WinSxS directory from the result.  From setup perspective, all indicated that the installation succeeded and files are installed correctly.
     
    The publicKeyToken for MSXML4SP2 is:
     
    publicKeyToken="666b9d6e4ce23dcb"
     
    According to your email, the manifest linkage used the following publicKeyToken that is different.
     
    /manifestdependency:type='win32' name='Microsoft.MSXML2' version='4.20.9818.0' processorArchitecture='x86' publicKeyToken='6bd6b9abf345378f' language='*'
     
    I think that's the problem.  Please try to use the same publickeyToken from MSXML4SP2, and see if that resolves this issue.
     
    Thanks.
     
    Yuhong
    Tuesday, May 9, 2006 5:00 PM

All replies

  • MSXML4 is released with two merge modules:

    msxml4sys32.msm

    msxml4sxs32.msm

    The former one is to install msxml4 into system32 directory, the later one is to install msxml4 into WinSxS directory.  If you want both to be installed, you need to merge both modules.

    Thanks.

    Yuhong

    Monday, March 27, 2006 6:07 PM
  • I am merging both - but on the target machine it doesn't seem to install to the WinSxS directory (I am using Wise for Windows Installer)
    Monday, March 27, 2006 6:10 PM
  • We need to investigate why the files were not installed to WinSxS.   To investigate it, I need to have the following materials.  Is it possible to get them?

    A). Windows Installer log file from your installation of msi. 

    To get it, you run the installation command as "msiexec /i <your.msi> /l*v c:\msi.log".  The file "C:\msi.log" will be the log file.  You can change it to any location or file name.

    B) The result of WinSxS directories.

    To get it, you can do:

    1). Go to the directory %WINDIR%\WinSxS

    2). Run the command "dir /s /b /a-d > C:\result.txt".

    3). Attach the result file "result.txt" or just add the result in the email.

    Thanks.

    Yuhong

    Monday, April 3, 2006 6:56 PM
  • I've emailed you the requested files...
    Wednesday, April 5, 2006 11:18 AM
  • Sorry for delay.

    It happened that yuhongli didn't receive files and wasn't checking post on this thread either.

    Send them against, please, and cc to me.

    (yuhongli@..., sdub@...)

    I can't guarantee that we would be able resolve the issue but will try hard.

    Sorry, again.

    Friday, May 5, 2006 6:52 AM
  • Re-emailed....

     

    Thanks for your help.

     

     

    Saturday, May 6, 2006 5:47 AM
  • Thank you for the result files.  I received it. 

    I checked the setup log file, and WinSxS directory from the result.  From setup perspective, all indicated that the installation succeeded and files are installed correctly.
     
    The publicKeyToken for MSXML4SP2 is:
     
    publicKeyToken="666b9d6e4ce23dcb"
     
    According to your email, the manifest linkage used the following publicKeyToken that is different.
     
    /manifestdependency:type='win32' name='Microsoft.MSXML2' version='4.20.9818.0' processorArchitecture='x86' publicKeyToken='6bd6b9abf345378f' language='*'
     
    I think that's the problem.  Please try to use the same publickeyToken from MSXML4SP2, and see if that resolves this issue.
     
    Thanks.
     
    Yuhong
    Tuesday, May 9, 2006 5:00 PM
  • I marked Yohong’s post as an "Answer". As usual fill free to clean this mark out if you don't satisfy with the answer and need more help with original problem.
    Tuesday, May 9, 2006 6:48 PM
  • Thanks for your help - I think it would be beneficial to people if the keys were explicitly documented - I had to deduce mine by looking in the directories.

     

    I have solved this by upgrading to MSXML6 (for other reasons) which does not seem to need any of this anyway.

    Thursday, May 18, 2006 6:37 PM