Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Visual Studio 2008 SharePoint Extensions

  Asked By: Melanie    Date: Oct 10    Category: Sharepoint    Views: 1273

Need some help understanding what I need to develop SharePoint webpage parts
using VS 2008. I'm a little rusty on my VB.Net and am in learning/training mode.
I did a little research and found that I should be able to create a new solution
and find SharePoint in my options... NO... I don't have those options. I then
found Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions,
Version 1.2 download, tried to download it, and need at least 2003 Server. I
have XP professional.

What am I missing? Do I really have to have 2003 Server to install
this. I can't imagine developers required to have server.

Any direction is greatly appreciated. Usually my company would send us to
training. Unfortunately traveling and training is not occurring right now for



3 Answers Found

Answer #1    Answered By: Rebecca Lewis     Answered On: Oct 10

I hear in 2010 this is fixed. But, really the best way to develop is to develop
under the OS you will deploy to. I would setup a VM running Server and install
Visual Studio there for your local development etc. I use VirtualBox to host my
VMs. In fact, I just finished configuring a new VM running Server 2008 with the
newest BETA VS2010. I just need the SharePoint BETA now.

Good luck. Yea.... I killed myself trying the different odd fixes for this that
are out there. It's not worth the trouble going that route.

Answer #2    Answered By: Emily Clark     Answered On: Oct 10

Sound terrible doesn't it? There are all kinds of tools you can install that
make your local machine behave correctly to build/debug/deploy SharePoint
solutions but we just did it the easy way. We have a virtualized server
environment for development and then we push the generated solution packages to
the server folk who run the STSADM commands to install/deploy/activate them on
our UNTI/SYS/PROD environments. All of our dev is done on 'servers' in this
manner. The best case scenario (when budgets get better) is to give EACH DEV
their own environment and install each with the same basic DEV image (VS2008,
MOSS2007 SDK, WSS3.0 SDK, WSPBuilder, etc.) That way, if we asplode our
environments we could just get them regenerated by the server folk. This way we
could do IIS Resets, destroy our builds and reboot our boxes at will without
ruining other's environments. Right now we have to check who else is on the box
and get their permission to IIS Reset, etc... Not too bad yet, considering we
only have 4 SP DEVs.

BTW, down with Visual Basic! Up with Visual C# !! SharePoint-land is C#-centric.

Also, take time to learn about the different deployment solutions out there.
WSPBuilder (my fav) really helps but there is STSDEV and the VSeWSS (v1.3 CTP is
better than v1.2, IMHO) that make the SharePoint end-game much more pleasant.

Answer #3    Answered By: Alycia Everett     Answered On: Oct 10

Two new things in VS2010

SmartParts are incorporated the infrastructure and VS
VS is now sharepoint  aware and will build solution files, manifests, etc
PS: it requires 64bit windows now

For the time being, I run a VM win2k3 with moss 2007 on it with vs2008. it's the
best option for right now. I purposely don't use any of the visual  studio
templates for sharepoint cause i've found it just creates more pain that it's
worth. I usually start off with just a class library project and build the rest
from scratch.

Didn't find what you were looking for? Find more on Visual Studio 2008 SharePoint Extensions Or get search suggestion and latest updates.