﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Henrik commented on Tooling shout out: .NET Memory Profiler</title><description>I couldn't agree more. It is so easy to use, and guides you in the right direction. I have introduced it in many projects, and everyone is amazed.</description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment7</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment7</guid><pubDate>Wed, 26 Dec 2012 14:08:40 GMT</pubDate></item><item><title>Omer Mor commented on Tooling shout out: .NET Memory Profiler</title><description>+1 on that. I had lost count on the number of times it saved our asses.
It's way more professional than the other, even though it has much less glitter.
And it's ability to import and analyze memory dump is genius.</description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment6</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment6</guid><pubDate>Tue, 25 Dec 2012 17:27:53 GMT</pubDate></item><item><title>Paul Shmakov commented on Tooling shout out: .NET Memory Profiler</title><description>I second that. While dotTrace and ANTS profilers look easier and friendlier, only the SciTech tool helped me to figure out really tricky leaks a couple of times. </description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment5</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment5</guid><pubDate>Tue, 25 Dec 2012 15:02:23 GMT</pubDate></item><item><title>Karim Ahmed commented on Tooling shout out: .NET Memory Profiler</title><description>Yeah it is way better than other .Net memory profilers, it provides tools and ways to find out the leaks that are very good. Used it in many scenarios and it never failed me.</description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment4</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment4</guid><pubDate>Tue, 25 Dec 2012 14:42:19 GMT</pubDate></item><item><title>Ken Egozi commented on Tooling shout out: .NET Memory Profiler</title><description>where are the good old days? we'd be printing the whole thing out to a 20 feet of continuous paper through the dot-matrix printer, then using a pen to locate the bug.

you youngsters and your hip tools.

get off my lawn.


srsly - I need to check this one out. Had reasonable experience with ANTS and dotTrace in the past, but this one looks to be less fancy, but digging deeper. I'll give it a try next time I'm in trouble</description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment3</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment3</guid><pubDate>Tue, 25 Dec 2012 10:58:06 GMT</pubDate></item><item><title>joff commented on Tooling shout out: .NET Memory Profiler</title><description>When investigating a memory issue, I have also found that .NET Memory Profiler is superior to tools of some other well known vendors.</description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment2</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment2</guid><pubDate>Tue, 25 Dec 2012 10:42:53 GMT</pubDate></item><item><title>Ben Joyce commented on Tooling shout out: .NET Memory Profiler</title><description>I had a couple of memory leaks in two recent projects,  both related to Lifestyle choices in my Windsor DI configuration, and I used the ANTS Memory Profiler from Redgate to find/resolve it. I will try this tool out and report back on its diagnostics. </description><link>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment1</link><guid>http://ayende.com/160449/tooling-shout-out-net-memory-profiler#comment1</guid><pubDate>Tue, 25 Dec 2012 10:24:57 GMT</pubDate></item></channel></rss>