The ability to access a member in the global namespace is useful when

the member might be hidden by another entity of the same name.

In this example, the namespace System is used to include the class TestClass therefore, global::System.Console must be used to reference the System.Console class, which is hidden by the System namespace. Also, the alias mcLovin is used to refer to the namespace System.Collections; therefore, the instance of a System.Collections..::.Hashtable was created using this alias instead of the namespace.

Thread t = new Thread (...);

t.SetApartmentState (ApartmentState.STA);

class Program {

  [STAThread]

  static void Main() {

  ...

• it will marshal over to a single-threaded apartment
• it will crumble and fail.

Need more cow bells ?

Except for the guys that work at a R&D software think-tank most of us have a business need that drives our software development, which in turn drives our paychecks.

To turn your back on business value is to bite the hand that feeds you.

Remember middle managment needs to look important also !!!

 This is a simple example of how to wrap your LINQ db.DataContext SubmitChanges() in a Transaction.

This is much like using transaction in SQL Server.

I used a simple add function to outline the pattern to use when wrapping your LINQ commits in transactions.

*Add a ref to System.Transactions;

New LINQ the home verion. now you and your friends can play "Map that Relational Object" on a Friday Night !!!

* Some assembily required.

   (database not included)

  using System.Transactions;