Home

SharePoint IT Pro Blog

MSDN Magazine Feed

Thursday, August 21, 2008

WSS 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1 on Win2k3 64bit

I got this to work for me using Orca to edit the MSI using the following:

1. Download Visual Studio 2005 Extensions, Version 1.1 for Windows Server 2003 Enterprise Edition 64-bit
A.
http://www.microsoft.com/downloads/details.aspx?familyid=3E1DCCCD-1CCA-433A-BB4D-97B96BF7AB63&displaylang=en
2. Save the install file: C:\Temp\VSeWSSv11.exe

3. Extract the MSI using this command: C:\Temp\> VSeWSSv11.exe /Extract

4. Output MSI file: C:\Temp\VSeWSSv11.msi

5. Downloaded Windows® Server 2003 SP1 Platform SDK
A. Installed just Orca

6. Edit MSI using Orca
A. In the Tables column
1. Select: InstallExecuteSequence
2. In the right pane, drop these two rows.
a. X64System
b. WSSNotInstalled
3. Select: InstallUISequence
4. In the right pane, drop these two rows.
a. X64System
b. WSSNotInstalled
B. Save MSI

7. Run edited MSI and follow the prompts.

Hope this helps someone else, it sure did for me!

Monday, August 4, 2008

Where is the change log?


Shane today in class was looking for where the SharePoint change log is. I did a quick search and found a decent answer on MSDN with detail on Change Log Freshness...

"The Change Log is a physical table in each content database, and each transaction writes to the log." The Change Log recevied by hitting the lists web service http:///_vti_bin/Lists.asmx GetListItemChanges with
GetListItemChangesSinceToken method of the Lists Web service to get changes starting from a specified point in time."

Found a great WSS 3.0
web service one page quick reference on Look Alive blog which I'm sure came from across the various MSDN pages.

Note: The change log is security trimmed. "The change log returns a list of SPChange objects for changes that happened, for example, to the following object types:

  • Items, files, and folders
  • List metadata
  • Site metadata
  • Security