Interesting article but please do something about the background.

Wrong comment added.

The fifteenth part of the C# Object-Oriented Programming tutorial explains the use of events. Events can be added to a class to allow it to indicate when a specific action has occurred or is about to occur. Subscribers may then react to the event.

I hear what you say but some people don't know this who should.

Not a bad article but like other readers, I can't agree with the items on casing or whitespace. There is an assumption here that colour coding will always be available (and that the user is not colour-blind enough to lose the distinctions). There is no harm in using upper case or additional whitespace (indeed, there is often a positive benefit) so there is no reason not to use it.

I have now added a final paragraph to the article regarding this. It is interesting to note that when you read the MSDN topic that their advice is different for differenct .NET versions.

Well spotted. Sometimes my fingers get carried away with themselves. I have fixed that omission.

An interesting article that puts forward some good reasons why you may not want to use third-party assemblies. This is probably very relevant to the software being developed in this case but the rule stated, "no third-party assemblies were allowed" is a little too wide-ranging.

A good example would be where in recent projects we have used the Infragistics controls for Windows. These have speeded up development of commerical bespoke developments and produced software with a user interface that would not have been possible to achieve within the customer's budget without using externally developed components. However, the interfaces for Infragistics are so complex that it has made the learning process for the controls be a long one. This validates one of the articles points though I think the overall effect of using the third party components has been positive.

An interesting comment, thank you. The article is supposed to be basic, it is a part of a large tutorial for beginners.

When I wrote this one I serious pondered over the extension of System.Exception or ApplicationException. SOME people consider it bad practice to extend ApplicationException. Indeed this is written about in the personal blog of at least one person at Microsoft. This is usually to keep the exception hierarchy flat. However, Microsoft also suggest within their own C# documentation that you should not extend the System.Exception. A case of one company giving to opposing views. In the end, I believe that both methods can be appropriate and that extending the ApplicationException to disassociate application-thrown rather than system-thrown exceptions is valid.

The final statement in the article alludes to the compiler’s ability to optimise the code. With a series of if statements, the executing code is forced down a decision path that may include complex comparisons rather than simple matches.

In the case of the switch statement, fall-throughs are not permitted (unlike in C++) and only matching of single, explicit values occurs. This provides the compiler with the option to optimise the ‘table’ of available match values in a similar manner to a simplified SQL indexing operation.

An example of this in operation with the initial code and IL code can be found at http://www.codeproject.com/cs/algorithms/soundex.asp