The slipstream version also known as the Microsoft Office SharePoint Server 2007 with SP1 has been released.

If you've attended any of the Windows Server 2008 sessions or been following the instructions across blogs you'll be very pleased.

As well, this release makes fresh installations easier.

Office SharePoint Server 2007 with SP1 (32 bit)
http://www.microsoft.com/downloads/deta … laylang=en

Office SharePoint Server 2007 with SP1 (64 bit)
http://www.microsoft.com/downloads/deta … laylang=en

Note: You'll notice two executables: OfficeServer.exe 295.0 MB and OfficeServerwithSP1.exe 409.2 MB. The OfficeServer.exe is the full RTM version. The OfficeServerwithSp1.exe is the new special slipstreamed version which is RTM plus the SP1 (slipstreamed).

These bits can be used as trial to activate standard or enterprise edition. Note these should not be installed on existing SharePoint Server 2007. The separate stand alone SP1 should be used in cases of existing installations.

Why is it easier?

These downloadable bits contain the full version of SharePoint Server 2007 along with a slipstreamed copy of service pack 1. This means the installation will automatically include Service pack 1 for WSS and MOSS. (Yes, the normal installation of MOSS RTM would require you to install WSS SP1, and then MOSS SP1.

What is the Windows Server 2008 reference?

SharePoint Server 2007 RTM or WSS 3.0 will not install on Windows Server 2008. It requires SP1. Thus these bits simplify and reduce confusion resulting from users trying to install WSS 3.0 or SharePoint Server RTM versions directly on Windows Server 2008. Previously, steps were required to add SP1 to the update folder.

For more information about Windows Server 2008 and SharePoint please refer to the TechNet Resource page dedicated to the topic.

http://technet.microsoft.com/en-us/offi … 35844.aspx

Why not just take down RTM and replace with this one?

We do think that this is what people should use the OfficeServerwithSP1.exe on all new deployments and upgrades, but we wanted to make sure that people who are running RTM and might be rebuilding a web front end or otherwise need the release version should have easy access to it. We apologize for any confusion on this.

SPGlobalAdmin globalAdmin = new SPGlobalAdmin();
SPVirtualServerCollection foundservers = globalAdmin.VirtualServers;
foreach (SPVirtualServer server in foundservers){}

but this code isn't supported anymore, Microsoft proposes another way:

foreach (SPWebApplication webApplication in SPWebService.ContentService.WebApplications){}

Here you go.

When you want to develop software that communicates with a sharepoint server, you can add a reference to your solution called System.Sharepoint. This dll file can be found in the

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI

Select the Microsoft.SharePoint.dll Assembly and add a reference to it. Make sure that
the Copy Local property is set to true (you do not want your application referencing the
actual Assemblies used by the server).

Note:
Because of the fact that SharePoint runs on Windows Server 2003 and is frequently
deployed in a data center environment, applications written to run on SharePoint servers
are almost always administrative in nature. It is a rare case when a user will find reason to
be logged on to the console of a Windows Server 2003 machine to interact with a
SharePoint API application for a nonadministrative purpose.

in other words: you can only use this dll when you are developping on a windows server 2003 where sharepoint is installed.