Hot answers tagged tools
SharePoint Manager is a SharePoint object model explorer. It enables you to browse every site on the local farm and view every property. It also enables you to change the properties (at your own risk). This is a very powerfull tool for developers that like to know what the SharePoint holds of secrets.
SPDisposeCheck - to check for any dispose mistakes that could result in a memory leak. Good to have hooked up to a build target as a post-build step so that the build fails if any problems are found.
WSPBuilder - for an easier, faster and more troublefree way to create new SharePoint solutions/features.
U2U CAML Query Builder - who in the SharePoint world can live without this one! It helps you avoid commoin CAML mistakes.
Can't do any serious development/debugging without Fiddler It's a great tool for examining all HTTP(s) traffic of your apps.
I've found .NET Reflector (now from RedGate) to be an indispensable tool when developing, and with SharePoint in particular. In some cases it has saved me from spinning wheels when it is clearly a "bug" or "feature" in the SP codebase, but it most cases it has just been invaluable from a learning perspective (oh, that's how that works!)
My favorite ULS Viewer: http://ulsviewer.codeplex.com/
Maybe not SharePoint specific, but I don't write code without ReSharper. Countless ways it improves productivity.
PowerShell! I use PowerShell more and more for small POC's where I would normally use console apps. Also for automation PowerShell is a great tool!
It asked for only one product per answer but I will group a couple as they work together. NUnit - for your unit testing. I also use MSTest but find NUnit has less clutter (VS2010 removes this for MSTest) TestDriven.Net - great tool for running the tests and include the open source version of NCover for your coverage needs.
Another one that's not really a tool but nevertheless very handy; in my quick launch bar I always add a Shortcut and a Toolbar to the 12 hive: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12
Check these out The PowerGUI Visual Studio Extension from PowerGUI. Power Tab
Development Main Visual Studio Visual Studio 2012 (SharePoint 2010), currently in Release candidate version Visual Studio 2010 (SharePoint 2010) with service pack 1 Visual Studio 2008 (SharePoint 2007) SharePoint Designer SharePoint Designer 2010 (SharePoint 2010) SharePoint Designer 2007 (SharePoint 2007) Visual Studio extensions CKSDev ...
Sure fiddler is good, but Visual RoundTrip Analyzer (VRTA) gives you a nice graphical illustration and can also help you with advice in solving the problems. It has issues regarding virtual environments though, but a great tool never the less (thanx Spence for introducing it to me:-) download VRTA
For SharePoint 2010 Development: SharePoint 2010 Developer Dashboard Visualizer
The content deployment wizard (http://spdeploymentwizard.codeplex.com/ ): The SharePoint Content Deployment Wizard is a tool for SharePoint 2007 which provides the means to deploy the following content: site collections webs lists folders list items (including files)
I very often use ULS Viewer (more info) from microsoft. Very useful tool to quickly find the cause of an error. I have even created a keyboard shortcut, and when I see an error on page, I copy correlation, run viewer and filter events by correlation. .NET Reflector or free analog IL SPY. Before SharePoint development I used this tools very rarely, but ...
Here's one that's useful when you want to put a Web Part page into edit mode but you don't have the option in the UI: ?toolpaneview=2 I explain it more fully in this post: http://sympmarc.com/2010/10/27/add-web-parts-to-sharepoint-forms-without-sharepoint-designer/
[url]?IsDlg=1 renders the page in dialog mode (no navigation). [url]?mobile=0 renders the desktop page on a mobile device. [ListViewURL]?FilterField1=fieldName&FilterValue1=value filters a list view (can be extended to FilterFieldnn).
SharePoint Skinner for creating CSS styles and themes for your site visually
Microsoft Live Mesh is a great tool to handle all your other tools. I've set up a folder that I have all my tools in and then use Live Mesh to have these tools synchronized into my VM's and other machines. As soon as I add or update a tool, they are all "copied" to my other machines.
DebugView from Sysinternals/now Technet combined with System.Diagnostics.Debug.WriteLine, System.Diagnostics.Debug.Assert etc is very good especially in events or workflows where you cannot do trace.
Only top voted, non community-wiki answers of a minimum length are eligible