Must Have SharePoint dev tools?

I am sure that you also use Visual Studio, but beside from this I have a couple of additional tools that I would include in my toolbox: WSPBuilder (for building SharePoint solutions - couldn't live without it) SharePoint Designer DebugView IE Developer Toolbar.

Another great tool for SP developers: SharePoint Manager 2007 It is a SharePoint object model explorer which exposes pretty much everything.

STSDEV in my view is good tool for creating solutions, like WSPBuilder and better than VSeWSSv12.

WSPBuilder for automated builds. WSS SDK for quick offline WSS documentation, samples, white papers, etc. MOSS SDK for quick offline MOSS documentation, samples, white papers, etc.SharePoint Solution Installer for easy deployment of WSP packages Imtech Fields Explorer for auto generating content type-based Page Layouts and features. SharePoint Dispose Checker Tool for checking for potentially undisposed webs/sites.

Get SharePoint to Validate to make those ugly HTML-table based web part zones into XHTML. YACAMLQT for us who can't be bother with how to nest CAML into valid statements. SPSReport for generating reports of the farm when an error is hard to track down.

SmartPart for hosting web user controls inside web parts without a line of code. Typemock Isolator for writing Unit Tests in SharePoint Fiddler for tracking what's going on between client and server IIS Diagnostics Toolkit for easily enabling SSL (and other stuff).

My best tools are: SPCamlViewer CAML Query Builder Sharepoint Variation Editor.

Should check out the list of tools on the SharePointDevWiki. Com page 'Other Development Tools'.

If you are doing anything with Search, then I can recommend our SearchCoder toolset: SearchCoder.

In addition to being a great persisted object browser, MAPILab Spy for Microsoft SharePoint is a fantastic tool learning the SharePoint object model and how types interrelate. Many of the one-off command line applications that are needed to read, set, or observe object instances can be avoided with this tool. MAPILab Spy does run $69, so something like SharePoint Manager 2007 (mentioned above in both Kasper's question and Tudor Olariu's reply) gets you some of the same functionality for much less (that is, for free!) For me, though, it's been worth the money for the tool in the development work I've done ... and no, I'm not a spokesperson (paid or otherwise) -- just a satisfied user :-).

SPTraceView hooked up with DebugView is an excellent combo for production debugging. Since most of the interesting stuff is going on in the database behind the scenes, Sql Profiler is a must if you want to know what stored procedure is being called etc.

SPVisualDev from CodePlex is another excellent tool to try out.

I've found that SP-Lint+ has helped me a number of times when I've mis-typed a value in a configuration file. See link text.

I'm using sharegate to replicate my Dev/QA/Prod environment share-gate.com.

Notepad++ For handling encoded XML, linearizing XML, etc. Very handy when SharePoint designer gets on the way.

Sharepoint 2010 Diagnostic Log Compression this tool is life saver for big files in verbose mode for troubleshooting.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.