Installing the WSS 3.0 SDK on XP/Vista
Phew - it's been a while since I posted. It's not that I've not got nothing to say just that I've been a wee bit distracted but some real nasty problems.
On the good side however MS finally got round to releasing the RTM version of the WSS 3.0 SDK. However in a big case of yaboo-shucks-to-you it's not installable on a XP or Vista PC. Well - not unless you know the (albeit rather easy) magic key.
I know that everything you see, read and hear about MOSS development keeps on screaming that you should develop on a server, for me that's not an answer - in fact IMHO it's just downright wrong.
I've got a good development environment on my laptop. I have various 3rd party tools and VS add-ons that I've installed on it. I've got loads of extra stuff besides. In other words - it's my development environment.
"Guns for show, Knives for a Pro" - Soap : Lock, Stock & Two Smoking Barrels.
OK, so MOSS development's not quite the same as ripping off a brutal London based gang of their hard stolen dosh - however the theory still stands - use the right tool for the right job. Develop on a PC, test on a server. At least that's my personal view.
And all this was working fine for me until today. I'd copied the requisite DLL's from my MOSS Server to my laptop and registered them into the GAC. I could do all my development on my laptop then copy the files over using a simple batch script to the server prior to deployment. My post build script checked to make sure it would only execute the deployment side of things when it was on the server. All was happy in my world.
However today I find out that the newly released RTM version of the WSS 3.0 SDK won't install on my Vista development environment. Fortunately there's a very simple solution </rant>
Simply fire up regedit (or your favorite Registry Editor) an create yourself a new set of keys under HKLM called SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0. Now create a REG_SZ value called SharePoint and set it to equal Installed.
That's it - everything else should then install nicely.

.png)

9 comments:
Thanks man. I agree with you. Development on a server? They nuts or what!
This also works to get VSeWSS (at least the 1.1 CTP) installed on Vista.
I did get the WSS 3.0 installed on my PC, but now I'm getting an error: "No SharePoint Site exists at the specified URL." even though I have inserted the URL for the SharePoint-server I want to deploy to.... I have also tried to write the port i.e :80, and I have tried to conenct with https. Anyone who knows what to do now?
I tried this trick and was ok. But now, I`ve a problem with a sample WebPart project. In project propiertyes, I can`t open the SharePoint solution tab. ¿Is there any fix for this problem?
i am getting the same "No SharePoint Site exists at the specified URL", too. how do you set up your project/debug properties?
Now you can install WSS 3.0 SP1 on Vista.
http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/05/21/how-to-install-windows-sharepoint-services-3-0-sp1-on-vista-x64-x86.aspx
Hi, Has anyone found a fix for:"this product requires windows server 2003 sp1.install this service pack and re-run"
because I am also trying to install WSS 3.0 in XP Environment.
Please Assist
Alex said...
Has anyone got it to work for XP? Seems like it works for Vista but I am still having the same issue.
Getting follwoing error
Setup is unable to proceed due to the following error(s)
This product requires Windows Server 2003 SP1. Install this service pack and re-run setup.
Correct the issue(s) listed above and re-run setup.
Anyone knows how to fix this
Post a Comment