.NET news » C#

As class libraries evolve over time, new functionality will be added and existing classes, methods and properties will be improved. Sometimes this means that older code is superseded and it is preferable that it is marked as obsolete and no longer used.

Describes a technique for displaying localized text for enums

A list-style collection for fast insert and remove operations.

Use nullable types to assign null values to value types and avoid run-time exceptions in your applications.

How to make a class look like an enum with added functionality

Explains how to properly implement the IEquatable interface.

I'm currently in the process of developing an object relation mapper for use with Microsoft SQL server. During this process I've been faced with a number of challenges related to the fact that I will be working with objects rather than datatables. If you've ever tried binding a datagrid to a list of objects, I'm sure you have come across the problem where you wanted to display properties that is not part of the object type itself.

This is normally referred to as nested property binding. Many people create special view objects when this becomes a necessity. I wanted a smoother solution and I wanted it design time. The component I've created derives from Bindingsource and is called ObjectBindingSource. As the name implies the components is designed to be working with objects and not datasets/datatables..

This Article will teach you about C# delegates in the most simpliest way to understand (for newbies).

Q: I'm using locks in my application to synchronize work on a bunch of threads. Unfortunately, I'm doing something incorrectly and my threads seem to just stop sometimes. I think I'm running into deadlocks, but I'm not sure how to find them. Is there any way I can do so programmatically? I'd like an exception to be thrown when a deadlock is encountered.
A: First, it's important to understand what a deadlock among threads is and the conditions that lead to one. Threads deadlock when waiting on each other to release some resources, but by performing that blocking wait, they're not releasing the resources the other threads need in order to unblock. The threads can't make any progress until the resources are released, but because they're not making progress, the resources will never be released, the threads are locked up, and thus "deadlock"...

This is a simple example taken from MSDN about multi-threading or, the way I like to say it, "Doing two things at once." I've modified the original example to make it easier to see how everything interacts. Easier for me anyway, since we are all different. One explanation may be adequate for some and not for others. I hope this can shine some light for some, as it did for me.

Far from being any type of Guru on the subject, I'll try and explain it the best I can from my point of view. I honestly don't understand everything about threads, delegates and so on. The important thing in my mind is that I understood enough to have it do what I wanted in the end. The next step is understanding the rest.