March 23, 2010 Design Patterns, IDE 4 comments

I have a story about the doctor who had a very good and fast car – Mercedes. On the way to work he is often stuck in traffic congestion and this makes him mad and late so as an impact his patients suffer. And he has a dream that his car became Ambulance and all cars make the way to him. Only one issue with this: Ambulance should beep and his car has no such ability so your task is to decorate Mersedes so when it goes it beeps.
How can you accomplish this?


So here we have Car class:

class Car {
    protected String BrandName;

    public void Go(){
        System.out.println(“I’m “+BrandName+” and I’m on my way…”);

and the Mersedes implementation:

MercedesCar extends
Car {
MercedesCar() {
        BrandName = “Mercedes”;

The Decorator pattern is used to add some functionality to your objects. In our example we want to add beeping to the concrete implementation of Car, but also we can add other functionality. So in order to save contract of Car class and have base class for all features we create the CarDecorator class like below:

CarDecorator extends
Car decoratedCar;

CarDecorator(Car car) {
        decoratedCar = car;

    public void Go() {

as you see it has decoratedCar wrapped, that is why patterns is also called Wrapper.
So in order to add some additional functionality we derive from Decorator class:

AmbulanceCar extends
CarDecorator {
AmbulanceCar(Car car) {

    public void Go() {

so it was slight extension – beeping :)

And usage looks very friendly – we cover Mersedes with Ambulance features, after that we can cover it with more abilities, in other words we can add features dynamically.

        Car doctorsDream = new
AmbulanceCar(new MercedesCar());


I’m Mercedes and I’m on my way…

I think you extected it. Now lets take a look at the UML diagram of this wisdom:

This pattern has some similarities to the Composite and Adapter patterns. Adapter could change the interface of behavior, but Decorator not (we are derived from Car). Composite works with lot of components, not like Decorator with only one.

What was interested for me here is usage of the IDEA instead of eclipse and I must say that this is just heaven to use it. I feel myself comfortable with Resharper so it was quite very easy to write code on the fly. And porting of code from eclipse did not make any issues…


I love Performance Profiler

March 14, 2010 IDE, Performance 2 comments

Honestly I haven’t used any Performance Profiler, since I did not feel need to use it and also I thought that it could be boring… How was I wrong! It is so easy and intuitive, I’m getting super good reports with highlighting of  expensive code and it keeps highlighting in Visual Studio. So I’m always aware which code is expensive.

Take a look:

I love it.


There is no “Edit WCF Configuration”

March 3, 2010 IDE, WCF, Workaround No comments

If you have no “Edit WCF Configuration” in the context menu on right click on the App.config.

I’m talking about this one:

Go to Tools -> WCF Service Configuration Editor

Open it and then close.
This is funny and strange solution to our issue.

No comments

Installation VS2010 RC on Windows XP – Issue: “To help protect your computer, Windows has closed this program. Name: Suite Integration Toolkit Executable”

February 23, 2010 Errors, IDE, VS2010 4 comments

I have found that not only my project has a lot of stupid bugs with more unexpected fixes, but also some well known products like Visual Studio.

Today I tried to install VS2010 RC on the XP system. Before that I had Beta 1 installed, but now it requires Service Pack 3.
So I installed Service Pack 3, deinstalled Beta 1 and was expecting to install VS2010 RC without any pain.

But what happen was interesting:

Installation process runs… and then just dies without explanations.
Playing with it I’ve got this
Error message:
To help protect your computer, Windows has closed this program. Name: Suite Integration Toolkit Executable

I searched over the internet how to fix this. And I found it:
Go to input languages settings and do the next for each input language you have:

I could not imagine that someone is able to guess such strange fix itself. :)

Of course there are explanations here and here.