Prior to .NET 2.0, there wasn’t the facility in C# to opt the visibility level for the get and set property or indexers.

I read about this interesting thing somewhere in MSDN. There are two types of programming or programming languages.

When I was working on the .NET reflection extravaganza thing that I explained in my previous column, i learnt one another interesting thing, that is about the Type.

Over the past few weeks, I have been involved with this module that got the best of both worlds - .NET and I, 😁.

Ok, this was the problem. We have a COM server, let us name it Server. I had to write an assembly in C#, let us call it Bridge, that will listen to all of the events fired by the Server and perform an action Action. To keep that Action simple, let us assume we have to log them to the database. But the Server fires hundreds of events, and it is not wise to write up static event handlers for all of them. Also, if more events are (ever) added in the future, the Bridge should be able to support it without code changes.

The twist in the game was that this was a brown + green field development project. That demanded a wise solution - learn from the past and better the future.

I have been using C# for quite some time now, and that too VS 2005.

Though I knew that there are quite a few languages for the .

Had to implement our COM OOP Server project in .NET, and I found this solution from the internet after a great deal of search, but unfortunately the whole idea was ruled out, and we wrapped it as a .

I am not a UI guy. More specifically, I love to work with UIs.

I am just like Alice in Wonderland, and not yet got out of the wonders of the .

If you have long been programming in C++/COM and then you move to C#.