As I have mentioned earlier (see "To leak, or not to leak…(memory) – Part One") the closures are the most common reason for memory leaks in Internet Explorer.

They are extremely good at forming circular references especially in the context of Host objects. The most common example is event handlers “owned” by a Native object which are attached to a specific event raised by a DOM element and hold a reference to that DOM object kept in the Native object.

Example:
DOMElement.Event ->  NativeObject.EventHandler -> current execution context scope ->
NativeObject. DOMElementRefference -> DOMElement

Very frequently websites and web applications with a rich UI include components which produce...

A few weeks ago a couple of colleagues and I established that our source control system (VSS 6.0d) needs to be updated. There were numerous issues that were plaguing our daily struggle with Source Safe – slow speed, frequent crashes and file corruptions. Naturally we began looking for alternatives of the aging software (version 6.0 was originally released with VStudio 6.0 and was only patched a bit with the release of VS.NET in 2002).

In a nice bit of synchronicity with our efforts, Visual Studio 2005 was just released and introduced a brand new version of Source Safe (it was internally...

As a newbie blogger perhaps I should have started with a brief info on who I am and should have continued with a post extending my best wishes for Xmas and Year 2006. Nonetheless, I thought it's a better idea to post some technical content that might be of use to our community. Perhaps the info will benefit some of you and will let you spend Xmas Eve with your family, rather than sit in the office trying to fix problems for which our team has found solutions.

Ever been shocked with how much your memory usage grows on every refresh...

One of the people on our design team sent us the good news this morning - it's official that Internet Explorer for Mac will no longer be supported and will not be available for download as of December 31st, 2005. You can read the full bulletin at the Mactopia site:
http://www.microsoft.com/mac/products/internetexplorer/internetexplorer.aspx?pid=internetexplorer

I am sure there won't be a lot of tears in the eyes of our development team now that the "villain" will be finally gone.

We will not stop to support Mac IE immediately but we do plan to drop support for the notorious browser at some point in Q1 2006. We do recommend to customers...

My name is Vladimir Milev and I am a software engineer at telerik. I would like to talk about code metrics in my first post on the company blog. The r.a.d.controls suite has come a long way and features a lot of components. This has come at a price though – increasing complexity of the code.

Code complexity is measured in different ways, however, the most commonly acclaimed metric is called “Cyclomatic complexity”. It was introduced by Thomas McCabe in 1976, and it measures the number of linearly-independent paths through a program module. The score is determined by the following...

As you may know, all components from the r.a.d.controls suite render XHTML 1.1 compliant output. We wanted to promote it in a way that all users can click a button in our online examples and see for themselves that everything validates perfectly. W3C provides an online validation service (http://validator.w3.org) so it should not be that hard. Unfortunately ASP.NET 1.x complies with *NO* HTML standard ever approved by W3C. ASP.NET 2.0 was first XHTML 1.1 compliant, but then in the official release Microsoft fell back to XHTML 1.0 transitional which is less restrictive.
I made a couple of Google searches and found other people...

DotNetNuke 4.0 was officially released about a month ago, giving a major revamp to the project, now specifically designed for .NET 2.0 and offering Visual Studio 2005 support. Although there were some inevitable glitches, in my opinion DNN 4.0 is a solid release.

Porting the existing r.a.d.controls for DNN to 4.0 proved to be a straightforward task. Almost all our DNN controls compiled right away after simply replacing the old .NET 1.1 assemblies with the 2.0 ones (e.g. RadEditor.dll -> RadEditor.NET2.dll). The main task was to simplify the new distributions by taking advantage of the new functionality offered by .NET 2.0. All skinobjects and...