Remote WebPart Development with Visual Studio 2008 for MOSS 2007


Today the Visual Studio Extensions for WSS are not supported with VS 2008. So the official way to develop Sharepoint Projects like WebParts is that you still have to use Visual Studio 2005 for that purpose. You can install VS 2005 ans VS2008 on the same machine, but why do I have keep the older version of Visual Studio just for Sharepoint Development.Therefore I tried to apply the same procedure described in my previous post for Visual Studio 2005 to my installation of Visual Studio 2008. The only thing that must be changed is the *.reg file which now should look like this:


Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\CLSID\{041d4811-6ee8-4c3a-8981-ac53f22cf9cc}]
@="Microsoft.SharePoint.Tools.SdtProject"
"Class"="Microsoft.SharePoint.Tools.SdtProject"
"CodeBase"="C:\\Program Files\\Microsoft SharePoint Developer Tools\\package\\SPDevTools.dll"
"InprocServer32"="C:\\Windows\\system32\\mscoree.dll"
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\CLSID\{c81fbc80-1a9b-4d76-81e4-bf729a27f9ac}]
@="Microsoft.SharePoint.Tools.Forms.DeployPropertyPage"
"Class"="Microsoft.SharePoint.Tools.Forms.DeployPropertyPage"
"CodeBase"="C:\\Program Files\\Microsoft SharePoint Developer Tools\\package\\SPDevTools.dll"
"InprocServer32"="C:\\Windows\\system32\\mscoree.dll"
"ThreadingModel"="Both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{bc426e8f-098f-47de-ad66-d11676c41c66}]
@="Microsoft.SharePoint.Tools.SdtPackage, SPDevTools, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
"ID"=dword:00000064
"Class"="Microsoft.SharePoint.Tools.SdtPackage"
"CodeBase"="C:\\Program Files\\Microsoft SharePoint Developer Tools\\package\\SPDevTools.dll"
"CompanyName"="Microsoft"
"InprocServer32"="C:\\Windows\\system32\\mscoree.dll"
"MinEdition"="Standard"
"ProductName"="SharePoint Developer Tools"
"ProductVersion"="12.0000.0000.0000"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{bc426e8f-098f-47de-ad66-d11676c41c66}\SatelliteDll]
"DllName"="SPDevTools.dll"
"Path"="C:\\Program Files\\Microsoft SharePoint Developer Tools\\package"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Projects\{9e5d3e2d-e4e2-418e-8d80-2f0da9a94f9a}]
"DisplayName"=""
@="SdtProjectFactory"
"DefaultProjectExtension"="csproj"
"DisplayProjectFileExtensions"="SharePoint Project Files (*.csproj);*.csproj"
"Package"="{bc426e8f-098f-47de-ad66-d11676c41c66}"
"PossibleProjectExtensions"="csproj"

#[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\NewProjectTemplates\TemplateDirs\{bc426e8f-098f-47de-ad66-d11676c41c66}]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\NewProjectTemplates\TemplateDirs\{bc426e8f-098f-47de-ad66-d11676c41c66}\/1]
@=""
"SortPriority"=dword:00000064
"TemplatesDir"="C:\\Program Files\\Microsoft SharePoint Developer Tools\\package"


 


 !! Absolutely no warranties, use at your own risk !!





That’s it! Hope this procedure is helpful to others, who want to develop Web Parts for MOSS 2007 now with Visual Studio 2008.

Comments (6)
  1. jaumedejuan says:

    Thanks a lot, just as extraordinarily helpful as with your previous post on VS 2005.

  2. Das Erstellen von Workflows mit dem ' alten ' Visual Studio 2005 war keine leichte Sache und

  3. hm_kamae says:

    Hello, MS released visual studio extensions 1.2 . I tried to modify the registry , but no success.. can you help?

  4. Vollmix says:

    Sorry, but not this time. Maybe I will play with the new bits the next two weeks. If I get it working I will post the news on my Blog

    Regards

    Martin

  5. pavenc says:

    Martin,

    This looks great, thanks.  I was a bit overeager, however, and followed your previous tutorial first, even though I have VS 2k8 SP1.  I changed the path in the registry hive myself (from 8 to 9) and got the error that the project type was unsupported.

    I rolled back my registry changes, and re-imported what you have above, and I’m still getting the same error.  Any thoughts?

Comments are closed.

Skip to main content