The RTM SDKs have been released:

WSS 3.0 : http://msdn2.microsoft.com/en-us/library/ms441339.aspx

MOSS 2007 : http://msdn2.microsoft.com/en-us/library/ms550992.aspx

WSS Downloads:

Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 Language Pack

Windows SharePoint Services 3.0 (x64)

Windows SharePoint Services 3.0 Language Pack (x64)

Visual Studio 2005 extensions for Windows SharePoint Services 3.0

MOSS and WSS RTM Installation Guides:

MOSS single server:
 http://technet2.microsoft.com/Office/en-us/library/bd99c3a9-0333-4c1c-9793-a145769e48e61033.mspx

MOSS server farm:
http://technet2.microsoft.com/Office/en-us/library/776589ed-aba4-47eb-8c4d-86905ac11a511033.mspx

WSS single server:
http://technet2.microsoft.com/Office/en-us/library/6181fe5b-90ca-40cf-aade-abd59cf3c9071033.mspx

WSS server farm:
http://technet2.microsoft.com/Office/en-us/library/fb6951ab-36fc-40c4-b2bb-9ab719ac7f691033.mspx

Planning for Capacity Boundaries, Estimating Performance & Capacity Requirements, Additional Factors, and Tools

WSS: http://technet2.microsoft.com/WindowsServer/en/library/0e13e879-0156-4e9f-b6d5-abddcf326d211033.mspx?mfr=true

MOSS: http://technet2.microsoft.com/Office/en-us/library/eb2493e8-e498-462a-ab5d-1b779529dc471033.mspx?mfr=true

Ok, so i fired up the stand alone sharepoint solution generator that comes along with Visual Studio Extensions for Windows Sharepoint Services 3.0 and selected site definition and pressed next and an unhandled exception is thrown.

It seems that the  Sharepoint Solution Generator expects a Sharepoint site as the default web application on the machine. e.g. http://localhost:80

Ok, so quick work around is to create a WSS app on the default web application.

Microsoft has released the Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 which includes some nifty Visual Studio project templates for Web Parts, site definitions, and list definitions

There's also a very useful stand-alone utility program, the SharePoint Solution Generator which builds a VS2005 solution for a WSS site or list definition.

Visual Studio Extensions for Sharepoint Services were announced at DevCon 2006 back in March. A demo was done at the time based on Alpha code. It was supposed to :

• Set of Project Item Templates (e.g. Web Part, Site Def, List Definition, Feature Definiton, Event Handler, Workflow Activity)
• Adds a "Sharepoint" Project Type to VS 2005
• Add required xml schemas.
• Export a site to a site defintion (Now this would be really cool!)

 
Does anyone know when we are likely to see a Beta release?

Microsoft have released a beta of their new virus scanning product for MOSS and WSS v3

Download here

To enable intellisense when you are authoring WSS v3 / MOSS 2007 XML files within visual studio 2005 do the following:

Intellisense should now work!

Stramit has rewritten his CAML viewer for MOSS 2007. Download from http://www.codeplex.com/Project/FileDownload.aspx?ProjectName=SPCamlViewer&DownloadId=2350
 

A couple of good installation resources for MOSS 2007 / WSS Betat 2 TR:

·         Amanda Murphy: MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots) and WSS 3.0 Beta 2 to B2TR Patching Procedure (with screenshots)

·         Steve Smith (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (with screenshots)

·         Dustin Miller (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (screencast)

·         Joris Poelmans (SharePoint MVP): WSS 3.0 B2+B2TR Slipstream Clean Installation Procedure (with screenshots)

I came across this interesting post (copied below). A utility to generate WSSv3 features from existing sites. This would be a very helpful utility if it works. Finger's crossed I can  get hold of a copy.

I don't know how you usually develop customizations for your customers, but I usually have some concepts and ideas from the theoretic folk. Now I setup a VirtualPC and start to play around with the stuff from the concepts, until I am satisfied. This usually includes a lot of creating/deleting/renaming fields/lists/templates etc etc.

Now the big question is, if I am satisfied, how to get this stuff out of the VirtualPC and ready for deployment ?!

Yeah sure, you could either extract all the templates and import in the target system, but how about the fields/columns on site-level?
Sure, go ahead and recreate them, or even better model them in XML *gnarr*

Since I didn't find a tool out there to speed up this process, I wrote a small utillity: FeatureCreator

As you might have guessed, you can select all the stuff you can package into a feature, and create a feature-xml from it. Almost ready for deployment (Just create the manifest, and package it. Maybe I will add even this later)

Expect the first version to be available for download on next Monday, unless someone points me to another way to create the features!
And also stay tuned for its big brother: SolutionCreator !

 Comments welcome!