Tag: Debug

Don’t debug often

Sometimes it’s better to code the whole module first instead of debugging and testing continuously. Debugging is very time consuming especially for heavy applications like SharePoint’s.

If the deadline is approaching, at least you have a module that has already been thought out, you can mitigate problems later. It’s a better solution that trying to implement the module when deadline approaches.

For big application, debugging is very time consuming and disruptive to your flow.
Write code in big chunks, then debug once in one session to save time.

Ways to debug ASP.NET and Sharepoint webparts

Either run Debug from Visual Studio, which will retract and redeploy the project before deploying and more time consuming

Or, From “Debug”, select “Attach to process…” and attach the debugger to the w3wp.exe processes and start debugging. Make sure to open the browser and browse the site first to start the processes before attaching.

Test emails with SharePoint

use papercut

https://papercut.codeplex.com/

follow the article https://prasadpathak.wordpress.com/2014/10/31/sharepoint-using-papercut-for-testing-the-email-functionality-in-sharepoint/

Make sure the local SMTP server is created and configured and started from IIS 6.0
Disable the Simple Mail Server … service in Services
Set papercut to listen on port 25 local server

Hacking and debugging tools

http://www.asjava.com/tools/fiddler-tutorial-how-to-use-fiddler/

Illuminations and firebug: it’s aware of popular JS frameworks such as Ext.js, Angular, etc.

DBVisualiser: allow you to edit rich text and images in vast amount of databases. http://www.dbvis.com/

RegExr: to test and visualize regex: http://regexr.com/

XPath Visualiser: to test and visualize XPath for XML query: http://xpathvisualizer.codeplex.com/

WinMerge: to compare files to find differences.

Visual Studio Web Essentials plugin: add useful features for JS development such as #region