Tackling problems and coding solutions for them is an essential part of the job of a software engineer like myself. The only problem with this is that sometimes work becomes a little boring and repetitive. With some tasks you can even begin to feel a little like a brainless code monkey that knows how to do its job very well, but lacks the stimulation of problems that appeal to the creative capabilities of the brain. Enter the Sudoku! I have always liked logical puzzles as a kid (and adult too) and when I was first introduced to sudoku I was immediately...

Today we finally renewed our Gold Certified status in the Microsoft Partner Program. It was a bigger pain to go through all the steps and complete all requirements than it was last year, but I am very happy that everything is all set again. Now that everything is official we will be able to put the following text on our site:"Microsoft Gold Certified Partners are the elite Microsoft Business Partners who earn the highest customer endorsement. They have the knowledge, skills, and commitment to help implement technology solutions that match your exact business needs." Impressive, huh?:) Don't worry, we won't put it on...

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...