Must have tool set for MOSS 2007 development.

views:

245

answers:

+3 Q:

Must have tool set for MOSS 2007 development.

I'm trying to compile a list of Must have tools/extensions for developing MOSS 2007 to build a dev machine. The dev os is Window 2008 R2 64 bit.

MOSS 2007
Visual Studio 2008
Sharepoint Designer
WSS/Office Server SDK
Visual Studio 2008 Extensions for WSS 3.0

Is there any additional required/nice to have tools?

+1 A:

On MOSS 2007 several people I respect use WSPBuilder and swear by it. For hard-core dev work you may find DbgView invaluable. Finally, a solid diff/merge tool like WinMerge often comes in handy. Of course, your mileage may vary.

Jason Weber 2010-03-19 02:32:48

+3 A:

.Net Reflector

Fiddler2

CSS debugging tools like IE developer toolbar, FireBug etc

Paul Lucas 2010-03-19 02:37:02

Reflector and FireBug make up for SharePoint's sparse documentation.

Rich Bennema 2010-03-19 16:12:28

+2 A:

SharePoint Manager is updated for 2010, but the 2007 release is still available. It's a great tool for browsing the innards of a SharePoint site hierarchy.

SPM

Chris Farmer 2010-03-19 02:51:55

This is probably the most important tool to have for SharePoint developer (well, except VS and WSPBuilder or STSDEV or VSeWSS)

Janis Veinbergs 2010-03-19 07:04:52

I think STSDEV was a great tool and grants more fine-grained control over the WSP creation process than the Visual Studio Extensions. I admit that I gave up on the VSeWSS tools early on, so they might be awesome now, but using STSDEV has been a breeze to integrate into the build process. Also, since the source is available, it's easy to fix or extend on a whim!

Chris Farmer 2010-03-19 02:57:03

The VSeWSS CTP 1.3 was a lot better than the previous versions, but still not good enough to make me use them. I haven't checked out STSDEV but there's nothing like the fine-grained control you get from manually doing your manifest.xml and .dff files ;-)

Paul Lucas 2010-03-19 14:42:04

I'll pile on with the STSDEV love. I prefer STSDEV's flexibility over either VSeWSS or WSPBuilder. Although, Visual Studio 2010 will probably replace them all. I haven't tried a 2007 project in VS 2010 yet, but I'm liking what I see for 2010 projects.

Rich Bennema 2010-03-19 16:19:51

I had to do some work with VSeWSS recently. It has improved significantly - from impossible to use to merely painful.

Tom Clarkson 2010-03-22 00:36:17

+7 A:

SharePointDevWiki.com covers this well:

Basic tools: Building a SharePoint Development environment

Then take your pick from this exhaustive list: SharePoint Development tools

My must-have items in my toolbox (some already mentioned) are:

VMWare Player
SharePoint Manager 2007
Powershell
SPWakeUp
NotePad++
SharePoint Inspector
SharePoint Feature Manager
SPDisposeCheck
Application Pool Manager
Beyond Compare 2
STSADM Win
ULS Viewer
Imtech Fields Explorer
Imtech List Generator
Firefox and Firebug
Stramit CamlViewer 2007
CAML Intellisense
U2U CAML Query Builder
Fiddler
Gary Lapointe's Custom STSADM Extensions
Scott Hillier Features on Codeplex
SharePoint Sushi

Brian Meinertz 2010-03-19 03:30:04

Great list! In fact I might just download some of those now!

Paul Lucas 2010-03-19 14:37:33

Of this list, the two absolute must haves in my mind are SPDisposeCheck and U2U CAML Query Builder. Do not deploy a custom DLL to production without first running SPDisposeCheck.

Rich Bennema 2010-03-19 16:09:48

I'd say IronPython is an invaluable tool for experiments with the SharePoint object model and short scripting tasks - of course, unless you already use Powershell.

How to begin - http://blog.glenc.net/2007/08/12/sharepoint-meet-python/

kerray 2010-03-21 20:24:07

Here is another good list for SharePoint 2007 developer tools

desigeek 2010-07-14 18:50:00

ansaurus

tags:

views:

answers:

Must have tool set for MOSS 2007 development.

related questions