Exploring the composition of the WSS Service Pack

I have found this article a long time ago. It is very useful and recorded here.

 

As we recently studied a problem with the underlying behavior of SharePoint, we need to take a look at Microsoft. sharepoint. library. DLL. this file is installed in GAC. I didn't try to get this DLL from GAC, and I don't know how to get it.

 

However, I know that the SharePoint service pack contains this file. After extracting the SP, I found it was an installation file. How can I achieve the DLL in the installation file? The method in splitstream here is worth a try.

C: \ Wssv3sp1-kb936988-x86-fullfile-en-us.exe/extract: C: \ wsssp1extract

C: \ Officeserver2007sp1-kb936984-x86-fullfile-en-us.exe/extract: C: \ mosssp1extract

For other options, refer:

 

After decompression, we found that many MSP files. MSP files are Windows Installer patch files. The tool that can open these files is Microsoft Windows Installer (hotfix.exe or update.exe ).

 

How can I decompress the MSP file? There is a tool called msix. Click to download it.

 

Decompress the package and find that all files are such files.

 

The file suffix consists of three parts: Real suffix, serial number, and language number.

 

For example, we rename mssmsg. dll_0001.x86.1033 to mssmsg. dll. After the problem is solved, you have obtained the file in the package.

 

To decompress the MSI file, try the following command line:

Msiexec/a f: \ ZENworks \ zfdagent. MSI/QB targetdir = c: \ zfd701

 

References:

How to Create a 'slipstream' installation for moss with SP1

Http://blogs.msdn.com/martinkearn/archive/2008/01/14/how-to-create-a-slipstream-installation-for-moss-with-sp1.aspx

Howto: Extract files from A. MSI file using the Windows Command Line

Http://thebackroomtech.com/2007/08/23/howto-extract-files-from-a-msi-file-using-the-windows-command-line/

Patch files Extractor

Http://blogs.msdn.com/heaths/archive/2006/04/07/571138.aspx