Cottleston Pie

Fernando Felman’s thoughts on software development

How to install the SharePoint 2007 VS 2005 Extensions on a Workstation

Posted by Fernando Felman on February 11, 2008

SharePoint 2007, or MOSS, is a server product and as such it can only be installed on the Windows Server family platform. I can understand that, it makes sense. What I can’t understand and doesn’t make any sense at all is that I’m not allowed to install the development tools on my new shiny Vista.

The recommendation for MOSS development was always to get a VM to run W2k3 with MOSS and Visual Studio. That’s all fine when you’ve to develop and do cycles of compile-deploy-debug, but what if you want to load an existing web part project with the visual studio installed on your workstation?

If you try to install the Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 Tools (VSeWSS) on a workstation you’d probably fail and get the following error: “This product can only be installed if Windows SharePoint Services 3.0 has been installed first”. So the only thing we’ve to do is to hack the installer into thinking MOSS is installed. How difficult can it be, right?

Before continuing into opening the Regedit tool, be aware that mocking around with the Windows registry is not supported, not recommended and generally considered bad manners.

Now open the regedit and create the following keys and the string value:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]

"Sharepoint"="Installed"

That’s it! You have fooled the installer into running on a workstation. Easy. I also recommend adding the core SharePoint assemblies into the CAG using gacutil. Those assemblies can be found by default in any ShaerPoint machine under the folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI.

If you’re feeling adventurous enough and want to get the full remote debugging experience, try out this excellent Martin Vollmer’s post.

About these ads

33 Responses to “How to install the SharePoint 2007 VS 2005 Extensions on a Workstation”

  1. This is utterly disgusting. Here I am, all ready to open the installer up in Orca and edit the MSI Conditions, but this? This is ridiculously simple!

    Tnanks.

    • Atul Jha said

      A completely agree with Avner,
      I had the whole Orca installed, as i could not install this MSI previously on my machine, and Sharepoint is installed on a 64 bit environment, where i was going to install this…

      Thanks Fernando, this was damn simple…

  2. Majid said

    I am able to find ‘Web Server Extensions’ key but there is no ’12.0′. so should i add the key?

  3. Mjid, you’ve to create all the non-existing keys and the missing string value.
    Enjoy.

  4. Majid said

    Felman, this is what i am asking.. how to create those? i can create the keys but how to create the Folder named ’12′ in ‘Web Server Extensions’?

  5. Majid,
    Create a new text file and rename it to “temp.reg”. Edit that file using notepad and add the following content to it:

    — Start temp.reg —
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]
    “Sharepoint”=”Installed”
    — End temp.reg —

    Save it and exit notepad.
    Double click it and accept the warning message. You’re done.

  6. Majid said

    Thank you very much… its worked!!!!

  7. James said

    You’ve saved me a ton of time here… Thanks for a VERY useful post.

  8. [...] Traduction libre d’un billet de Fernando Felman [...]

  9. Kirk said

    Thank you for the post. Wish I found this when I started to try to install this.

  10. Anders said

    Thanks :-)

  11. Andreas said

    I tried this hack on my Windows XP with Visual Studio 2008 Professional and Sharepoint Services Extension 1.2. I was able to install the extension without any problems, but I can’t see the Sharepoint entries in the “New Project” Dialog in my Visual Studio.

  12. Hey Andreas,
    The only difference I can think of between your environment and mine is that you’re using Visual Studio 2008 whereas I was working on Visual Studio 2005. So I know it’s a long shot, but maybe the SharePoint tools are not compatible with the newer version of Visual Studio?

  13. Andreas said

    I think the extension version 1.2 is especially for Visual Studio 2008.
    I also can see the extension in the “Products List” in the “About Visual Studio Dialog” and it’s possible to open an existing sharepoint project.

    Maybe one of the Updates of Visual Studio is the problem. I will try a reinstallation this weekend.

  14. Andris said

    I can’t see the Sharepoint entries in the “New Project” Dialog in my Visual Studio.

    Andreas,
    Make sure you have choosen correct target framework in the New Project dialog.

    Hope it helps,
    Andris

  15. Andreas said

    Hi Andris,
    i tried every Framework…
    I reinstalled my Visual Studio and the extension today, but the problem is still the same.

    I will keep on trying to get it run.

  16. Andreas said

    Hi,

    I solved the problem…
    The extension was german and my Visual Studio 2008 english.
    Now I installed the english extension and it works.

  17. [...] http://fernandof.wordpress.com/2008/02/11/how-to-install-the-sharepoint-2007-vs-2005-extensions-on-a… [...]

  18. [...] Interesting link on how to setup VSSeWSS on a non Windows Server PC: How to install the SharePoint 2007 VS 2005 Extensions on a Workstation [...]

  19. [...] Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 (VSeWSS) Not recommended. VSeWSS contains nothing to help you deploy features on anything but the machine running VS, does not support x64, and is required to open projects that it creates. So if you create a project today on a 32-bit machine, you will be unable to open it in a year when you’re building on 64-bit. This is bad. The one good feature included is the SharePoint Solution Generator (SPSolGen) which converts lists and sites “Saved as Template” into list and site definitions. [Learn more here] [Registry hack to install VSeWSS to a machine that is not the server] [...]

  20. Dave Horton said

    That helped a lot, and it allowed me to install the VSeWSS for 2008. Then it goes a couple steps more than it used to when I try to create a Sharepoint Sequential Workflow project. Sadly, then it seems to want a local Sharepoint directory for debugging. As my workstation doesn’t have sharepoint installed, it complains at that point and tells me to install Sharepoint. Did I miss something?

  21. This works just great! worth mentioning.. When you create the new String Value in Registry, you name it “Sharepoint”. The value within it is set to “Installed”. Just wanted to be even clearer than the original post, but again; THANK YOU!!!

  22. [...] Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 (VSeWSS) Not recommended. VSeWSS contains nothing to help you deploy features on anything but the machine running VS, does not support x64, and is required to open projects that it creates. So if you create a project today on a 32-bit machine, you will be unable to open it in a year when you’re building on 64-bit. This is bad. The one good feature included is the SharePoint Solution Generator (SPSolGen) which converts lists and sites “Saved as Template” into list and site definitions. [Learn more here] [Registry hack to install VSeWSS to a machine that is not the server] [...]

  23. [...] this article you can read how to install the VS2005 MOSS2007 extensions on a [...]

  24. [...] (aka VSeWSS) on a system without Sharepoint installed. Thanks to a blog post from Fernando Felman (reference), you just need to install this registry [...]

  25. Jay said

    Great! But…
    Imports Microsoft.SharePoint
    cannot be found.

    Will this just mean there will be no intellisense or will it not build?

    • It means you’re missing the core SharePoint assemblies (DLL files)…
      “I also recommend adding the core SharePoint assemblies into the CAG using gacutil. Those assemblies can be found by default in any SharePoint machine under the folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI.”

  26. Cathy said

    Hi,

    I have visual studio 2005 extension for sharepoint sucessfully installed in my Professional XP. But I could not see web part library when I clicked File -> New Project -> Sharepoint in my visual studio 2005.

    Any idea?

    • Hi,
      Unfortunately, nothing pops in mind.

      Apart from the obvious “clear app cache by restrating the app, and if that fails, do a reboot”, nothing pops in mind. But I assume you already did those.

  27. Hans said

    Thanks Fernando!

    You really saved my a lot of hazzle!

    Thanks!!!!!!!!!!!!!!!!!!!!!!!!

  28. [...] http://fernandof.wordpress.com/2008/02/11/how-to-install-the-sharepoint-2007-vs-2005-extensions-on-a… [...]

  29. I want to know if I need to install WSS 3.0 or MOSS 2007. I have set up a virtual machine win winsrv2003 for sharepoint. I am a beginner and want to learn Sharepoint

    • Hi Sujit,
      Welcome to the SharePoint world.

      I would recommend you start your learning on the newest SharePoint version, i.e., SharePoint 2013 (SP2013). The development model for SP2013 is quite different than that of SP2007 or even SP2010.

      However, if you do wish to learn on an old platform as SP2007, then the answer to your question is “yes, you have to setup a SharePoint 2007 VM with Visual Studio” to be able to develop with SharePoint 2007.

      Best of luck,
      Fernando

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
Follow

Get every new post delivered to your Inbox.

%d bloggers like this: