Do you use Fiddler to inspect the HTTP traffic? You may be faced with the following problem: since we started using the beta of the IE7 browser we started experiencing problems when monitoring the requests sent to http://localhost or http://127.0.0.1 - the requests were not reported by the Fiddler tool. It took us some time to understand what was the exact reason for this until we found the workaround for this issue here: http://www.fiddlertool.com/Fiddler/help/hookup.asp --- quote --- Why don't I see IE7 or System.NET traffic sent to http://localhost or http://127.0.0.1? IE7 and the .NET Framework are hardcoded not to send requests for Localhost through any proxies,...

The June issue of MSDN is out earlier than planned and this gives me freedom to blog about some very important developments in the telerik product offering. If you are an MSDN subscriber and you do not completely disregard the product ads, you might have noticed that "telerik is growing" and our ASP.NET product line will be soon complemented by a set of Windows Forms components and a Reporting tool. If you are interested in getting more information and seeing a preview of the Telerik Reporting and Windows Forms product lines, please stop by booth 819 at TechEd USA to meet with our...

There's a lot of great content so go and check it out at http://sessions.mix06.com/...

So much to blog about and so little time... It has been almost a couple of months since my last blog post and there were quite a few things to comment - new initiatives, interesting updates, participation in events, etc. For some reason I felt guilty for having so much to say and not blogging about it and I was looking for "THE blog post" to get back into the game:)Luckily for me, and for all telerik customers, the dev team came up with some pretty exciting news - with a great sense of pride we are happy to announce the first major third-party component suite...

Am I getting obsessed with memory leaks?  Give me a non-leaking browser and I'll cut it out .Yesterday I was hunting for a hard-to-find memory leak with r.a.d.treeview.  Our component cleans up its DOM element references and DOM event handlers when it is being destroyed.  Control destruction and resource disposal occurs on two occasions:  when the page unloads and when the control is updated by an AJAX call (r.a.d.callback, Atlas, etc -- the mechanism is framework-agnostic).  Now the treeview, being a good citizen, follows the leak prevention pattern of keeping references to DOM elements to a minimum.  Most of the...