Return to Answer

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used this and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. Use Debugger object to break automatically when you want developer's attention even if s/he hasn't enabled automatic break on eception:

 #if DEBUG if (Debugger.IsAttached) Debugger.Break(); #endif 

8. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

 using ComplicatedDictionary = Dictionary<int, Dictionary<string, object>>; ComplicatedDictionary myDictionary = new ComplicatedDictionary(); 

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used it and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. Use Debugger object to break automatically when you want developer's attention even if s/he hasn't enabled automatic break on exception:

 #if DEBUG if (Debugger.IsAttached) Debugger.Break(); #endif 

8. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

 using ComplicatedDictionary = Dictionary<int, Dictionary<string, object>>; ComplicatedDictionary myDictionary = new ComplicatedDictionary(); 

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used this and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. Use Debugger object to break automatically when you want developer's attention even if s/he hasn't enabled automatic break on eception:

 #if DEBUG if (Debugger.IsAttached) Debugger.Break(); #endif 

8. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

 using ComplicatedDictionary = Dictionary>; ComplicatedDictionary myDictionary = new ComplicatedDictionary(); 

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used this and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. Use Debugger object to break automatically when you want developer's attention even if s/he hasn't enabled automatic break on eception:

 #if DEBUG if (Debugger.IsAttached) Debugger.Break(); #endif 

8. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

 using ComplicatedDictionary = Dictionary<int, Dictionary<string, object>>; ComplicatedDictionary myDictionary = new ComplicatedDictionary(); 

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used this and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

using ComplicatedDictionary = Dictionary<int, Dictionary<string, object>>; ComplicatedDictionary myDictionary = new ComplicatedDictionary();

C# + CLR:

1. Thread.MemoryBarrier: Most people wouldn't have used this and there is some inaccurate information on MSDN. But if you know intricacies then you can do nifty lock-free synchronization.

2. volatile, Thread.VolatileRead, Thread.VolatileWrite: There are very very few people who gets the use of these and even fewer who understands all the risks they avoid and introduce :).

3. ThreadStatic variables: There was only one situation in past few years I've found that ThreadStatic variables were absolutely god send and indispensable. When you want to do something for entire call chain, for example, they are very useful.

4. fixed keyword: It's a hidden weapon when you want to make access to elements of large array almost as fast as C++ (by default C# enforces bound checks that slows down things).

5. default(typeName) keyword can be used outside of generic class as well. It's useful to create empty copy of struct.

6. One of the handy feature I use is DataRow[columnName].ToString() always returns non-null value. If value in database was NULL, you get empty string.

7. Use Debugger object to break automatically when you want developer's attention even if s/he hasn't enabled automatic break on eception:

 #if DEBUG if (Debugger.IsAttached) Debugger.Break(); #endif 

8. You can alias complicated ugly looking generic types so you don't have to copy paste them again and again. Also you can make changes to that type in one place. For example,

 using ComplicatedDictionary = Dictionary>; ComplicatedDictionary myDictionary = new ComplicatedDictionary();