Debugging applications can be very difficult. Using the standard debugging tools in Visual Studio is like having tunnel vision; you can see one leaf on a tree but not the entire forest. If you find yourself wishing for a better way to debug applications, look no further. Download Mole for Visual Studio for free and a new world of relevant information will be available to you.
Visit the Mole home page on Karl Shifflett’s blog here.
Read the CodeProject article about Mole here.
Watch the tutorial videos that show how to use Mole here.
Listen to the Polymorphic Podcast episode about Mole here.
Also, if you like Mole, you should check out Crack.NET.
The creation of Mole for Visual Studio was a collaborative effort between three .NET programming fanatics; jokingly referred to as Team Mole. Here is a quick review of Team Mole:
Karl Shifflett (a.k.a. The Molenator)

Karl was the captain of this crazy adventure. He was cranking out new features while integrating code that Andrew and I sent him via e-mail. Karl came up with tons of great ideas and just implemented them on the spot. He invented the amazing “Max-O-Drilling” data drilling feature, which makes Mole so powerful. Karl kept the torch burning and kept improving Mole day after day, week after week.
Andrew Smith (a.k.a. The Sniper)

Andrew joined the Mole project shortly after v1 was released. He earned the title “The Sniper” because of his mind-blowing ability to kill the really nasty bugs and then disappear into the thickets until needed again. A large amount of Mole’s editing capabilities was implemented by The Sniper. He contributed an endless stream of great suggestions, feature requests, bug fixes, and encouragement. Due to some of Andrew’s sage advice, Mole is about twice as fast as it would have been otherwise.
Josh Smith (a.k.a. Rock Star)

I built the original visualizer which got this whole initiative underway, Woodstock for WPF. Shortly after I released Woodstock, Karl mentioned that he was using it as a prototype for his own visualizer, Mole, so we joined forces to make Mole. Back then our visualizers only targeted WPF applications, but eventually we made it work for any type of .NET application.
I helped write the core Mole application, researched how to use the visualizer technology efficiently, designed the recursive algorithms for working with large hierarchical data structures, researched and built the logical tree functionality (for WPF apps only), and did endless testing, tweaking, and prodding to make Mole lightning fast. I’m not sure why, but I’ve been dubbed “Rock Star.” Oh well, I can think of worse nicknames!
Enjoy Mole and have a great day!


December 16, 2007 at 9:19 am
Wow!
Mole returns from a voyage deep within the manage heap.
Using his razor sharp claws, he digs through all the unwated mega bytes of HEX data in the CPU’s on die cache and returns with the answer before the carbon based life form, known to the world as “the user” can blink their eye.
Bring on Molemania!
December 16, 2007 at 11:08 am
Mole is the BEST!!!!!
December 16, 2007 at 11:09 am
Marlon,
Glad you like Mole and thank you for the encouragement.
Karl
December 16, 2007 at 11:10 am
Yeah, thanks Marlon!
December 21, 2007 at 3:53 pm
Josh,
Great job with http://www.moleproject.com
You are The Man,
Karl
January 3, 2008 at 2:09 pm
i can haz mole?
January 28, 2008 at 1:02 pm
I have tried both the VS 2005 and VS 2008 versions of the Mole and every time I try to bring up the visualizer I get a “Function evaluation timed out” error.
January 28, 2008 at 1:09 pm
Mark,
Please send support e-mails to moleproject@yahoo.com
Thanks,
Josh
January 30, 2008 at 6:43 am
The XML fragment really hits the chuckle spot! – Well done!
February 1, 2008 at 4:50 pm
I downloaded Mole for VS 2008 and was running it against Family SHow WPF app and but a breakpoint in for the menu creation method and was using Mole to view the menu item and typed “Clip” into the filter and then clicked on the hyperlink “CLip” and the whole thing forze up….
February 1, 2008 at 4:53 pm
Hey Frozen Mole,
Every once in a while someone reports this problem. Some people just cannot open a browser from a debugger visualizer. We can’t reproduce this on our computers and have no way of debugging it (assuming it is even “debuggable” at all). All I can say is, do not click on the property names!
Sorry, I wish I had a better answer for you.
Josh
March 13, 2008 at 6:33 pm
[...] Mole for Visual Studio « Josh Smith on WPF …Debugging applications can be very difficult. Using the standard debugging tools in Visual Studio is like having tunnel vision; you can see one leaf on a tree but not the entire forest. If you find yourself wishing for a better way to debug application (tags: dev dotnet debugging tools free) [...]
April 8, 2008 at 12:20 am
PDF manual really sucks. All screenshots look very ugly. Do not use JPEG, use PNG – it works much better for screenshots.
Links in the TOC lead to the web-site, rather than to sections in the file itself.
April 26, 2008 at 5:59 am
I need your opinions in my project..Please can you reach me from my email address? I am sure that it does not take time for you.
August 16, 2008 at 2:32 pm
Mole is the tool i had in mind, when i discovered it from the sourceProject website all my headaches about debugging went away.
You have improved my debugging , i just wanted to know if the source code is available, to learn from this amazing tool.
August 16, 2008 at 3:46 pm
xisket,
Karl hosts the source code on his blog:
http://karlshifflett.wordpress.com/mole-for-visual-studio/
josh
August 28, 2008 at 7:33 am
Mole seems to dislike VS2008 SP1. I’ve head other problems with that service pack, so I’m not sure if this is Mole’s fault or SP1’s.
I really liked it when it worked, but all I get now is a “Bummer …” message in the best case, or just an exception in the worst case.
September 8, 2008 at 1:22 pm
Hi:
I updated my installation of Mole for Visual Studio 2008 SP1 and now my Visual Studio shortcut keys, like F5 for Debug, don’t work. And I can’t seem to set them in the Keyboard Customize dialog either.
Any ideas?
Thanks,
Denny Huber
September 8, 2008 at 1:23 pm
Denny,
That’s weird. I’m sure it has absolutely nothing to do with Mole, though.
Josh
September 9, 2008 at 8:17 am
Ooops. It appears that my function keys are gone for ALL my apps.
Sorry for jumping the gun.
Denny Huber
October 30, 2008 at 7:16 pm
OMG… Any developer can drill with this tool like a pro in seconds. Really great tool. You guys are awesome.
November 4, 2008 at 7:15 am
[...] WPF Anwendunggen sind ja derzeit nur recht umständlich zu debuggen. Inzwischen gibt’s ein Zusatztool namens Mole: Mole for WPF [...]
November 14, 2008 at 4:18 pm
nice……..(^___*)