Meeting with Ray Ozzie

Ray Ozzie, our Chief Software Architect ( before him, Bill Gates was our CSA ) has came to our development center and deliver a session( that includes a question and answer round ), it was a dream come true for lot us here.

It was a house-full session, around a few thousand engineers eagerly waiting to hear from him, though I found lot of us has preferred to view this meeting thru our internal web cast. I have been in the venue long before to make sure that I will get a chair at the front row, but to my surprise the whole room was almost filled up.
He has been introduced by our Development Center Manager, Srini Kopulu, after then he has delivered a session which covered about our products, the IT industry, how we are looking at the future etc, but no doubt the best round was the question and answer session, he has answered question relates to simple technology to complex architecture/model/prototype/ideas/problems, but the best question was …
“How( or what are the qualities required ) to become the CSA of Microsoft ? J, and I found this is the only question he took little time to think before answer, cause rest of the questions were all technical.
Overall, I have found him a very simple man, looks so down to earth, and very very techie, no doubt, it will reamin a memorable day for lot of us.

CLR Profiler

Few days back I have written a tool using C# which does quite a few WIN32 native calls, and COM calls, while testing I have started doubting that may be my code has some memory leak.
To find out whether it is really leaking memory, I have taken help of a tool named ‘CLR Profiler’ written by Peter Sollich ( A CLR performance Architect), it’s a great tool in a word, it shows memory allocation( in bytes), allocation pattern, GC details, memory allocated for Large Objects …almost everything about memory management.

I found it very useful tool for checking memory leaks for the .NET apps( including ASP.NET apps/services).
While using this tool only thing to remember is that this tool takes quite a lot of memory for writing logs, and by default it writes the log into WINNT\Temp folder, perhaps the best idea would be setting this folder as non system drive( and which is having huge space ).

This tool is downloadable( with source code) , check out this link … http://www.microsoft.com/downloads/details.aspx?FamilyId=A362781C-3870-43BE-8926-862B40AA0CD0&displaylang=en.