Geeks With Blogs

News View Robert Porter's profile on LinkedIn

I am a Project Manager and Developer with an emphasis on Enterprise Content Management and Business Process Management systems.

With over 20 years of experience in large and small systems design and implementation. Currently based in the Raleigh NC area.


The views expressed here are my own, and do not necessarily represent the views of my clients and employers.


BlogOfBob Read:Learn:Contribute:Repeat

I have been using VSeWSS 1.3 since it first became available. As of this writing it is still in the CTP release stage. The previous version, 1.2 is still available, but the biggest advantage of the 1.3 release is support for 64 bit OS which was a prime motivator for me. Also 1.3 now supports publishing sites which was not possible with the previous versions.

VSeWss 1.3 March 2009 CTP is available, and is the version I am using for the purposes of this article. A good blog post about the extensions is available on Paul Andrew’s blog here. Another great overview of the extensions in action is a screen cast from Kirk Evans available on Channel9 here. He has also posted follow up screen casts which are listed as related posts on the Channel9 page I linked to.

It’s great to have these resources and the extensions do make life as a developer much easier, however installing them is more difficult than it needs to be. Hence I am documenting the process I went through, twice, as much for my own future benefit as yours!

I have successfully installed the extensions in two different VM environments, one based on 32bit Server 2003 R2, and the other on 64bit Server 2008 Standard.

 

Order is Important

Installing the extensions needs to happen after you have the rest of your environment installed and running. The extensions are designed to be installed in Visual Studio 2008 which itself must be installed on the same physical box with your single server SharePoint installation. The extensions are limited to deploying to the localhost and the direct deploy method will not work over the network to an external farm. (They do support packaging so that you can then copy the deployment package to another farm and deploy your project, solution, feature, or web part there.) But the extensions primary purpose is to support the develop, deploy, test cycle while you are actively developing components.

My installation overview that follows is just a high level overview of the process, their are a number of detailed references available on the web for installing WSS or MOSS, and I don’t want to repeat them here as my focus is on the extensions.

The installation order I followed was:

  1. Install the base OS, get it fully patched.
  2. Install IIS (6.0, 7.0) depending on your OS. A good article on how to configure IIS for SharePoint is here.
  3. Make sure ASP.NET (Application Server Role) is applied.
  4. Enable ASP.NET 2.0 on the Server. Same article as above.
  5. Install either WSS 3.0 or the full Moss 2007 install, select either Basic, or if you choose Advanced, make sure you select Single Server Farm.
  6. Run the Wizard and either configure the basic install or create and configure a farm depending on which installation choice you made.

Test your WSS or MOSS installation, make any post installation configuration changes you want. As you do, note the account that your installation is using to access the content databases. This account needs to be added to the local administrators group.

Once you are satisfied that you have everything correctly working on the WSS and MOSS side, install any patches or hotfixes for WSS and MOSS, re-run the wizard, then check for OS patches again. One caveat to note, if you use SQL Server 2008 Express edition or any other flavor of SQL Server 2008 you must install SQL Server 2008 Service Pack 1 or later if you are running on Server 2008 OS. Its a good idea to do this in any event regardless of which OS you are running. But it is required if you are running on Server 2008.

Now that your WSS or MOSS environment is up and running and patched and happy, you can move on to the development tools.

Development Tools

I installed the following and in the following order:

  1. Installed NotePad++ my favorite free text editor with syntax highlighting etc.
  2. Installed Visual Studio 2008
  3. Installed Service Pack 1 for Visual Studio 2008
  4. Installed the .NET Framework 3.5 SP1
  5. Installed the SharePoint (or WSS) SDK’s

Now validate your Visual Studio install, setup your source control of choice, and in general assure yourself that Visual Studio is fully setup and configured.

The next part was the tricky part. At least for me, go ahead and install the VSeWSS extensions. The installation will create a new Web Site called VSeWSS if all goes well, and it will select the same application pool that Central Administration is running under.

VSeWSS

This site is the service endpoint for the extensions.

The next two steps, for my installations, proved to be crucial. I created a new application pool, I called mine VSeWSS, original huh? apppool

I used the settings shown in the illustration, basically the same settings that the Central Administration app pool was using. The difference is that I made this app pool run under the identity of the account that I was using to access the content databases, and which I had added to the local administrators group as I mentioned above. In IIS 7 you select the application pool and then select Advanced settings from the actions menu on the right.

appidentity

In the Process Model I selected Identify and changed the user to the one I had selected. This means the application pool in essence runs with full administrative access as well as full access to the content database. (Good thing this is a development machine!)

And that was it! At that point I was able to get everything working, and built and deployed my first hello world web part and had all the nice shiny goodness of the extensions up and running!

I did run into a few odd errors as I was retrofitting other development systems and one of the worst to overcome was when I was getting an error indicating that no service was listening at the endpoint. Turned out that the .NET Framework 3.0 and 3.5 was installed on that machine prior to IIS being installed.

To fix that I ran the apsnet_regiis –i and the servicemodelreg –i commands from the appropriate locations in the Framework directories. You may also need to add a mapping between svc files and the aspnet_isapi.dll file in your IIS mappings maintenance area if the first two commands don’t resolve the issue.

Happy SharePoint development! Please feel free to comment if you have questions or issues and I will be happy to try and help.

Cheers,

Robert Porter

Posted on Saturday, February 13, 2010 11:40 AM SharePoint , ASP.NET , Visual Studio , .NET , Programming | Back to top


Comments on this post: Installing Visual Studio 2008 Extensions for SharePoint 2007 v3

# re: Installing Visual Studio 2008 Extensions for SharePoint 2007 v3
Requesting Gravatar...
can we install this package when VS 2008 is in french language ?
Left by boudier on Aug 25, 2010 8:43 AM

# re: Installing Visual Studio 2008 Extensions for SharePoint 2007 v3
Requesting Gravatar...
Hi, had to set this up for a customer who still runs MOSS 2007
thank you for bothering to put this together, it saved me from a lot of trial & error. Everything worked as described.
Left by Daniel Latikaynen on Apr 05, 2012 4:30 AM

Your comment:
 (will show your gravatar)


Copyright © Bob Porter | Powered by: GeeksWithBlogs.net