Arguably one of the best new aspects of C# 2.0 is Generics.  Generics gives us the best of two worlds.  The one world is the ability to write generic non-type specific code that can be reused with many different types.   The other world is the world of strongly typed objects. 

I, along with several others in my group, have quite a bit of experience with SQL-DMO (SQL Distributed Management Objects).  However, with the recent introduction of SQL Server Management Objects (SMO), we recently found ourselves taking a look at some of that functionality.  This article will take a look at and discuss some of the new features in SMO.

 

Just like SQL-DMO, SMO provides you with a set of objects that allows you to manage many aspects of Microsoft SQL Server.  SMO contains a vastly improved programming and object model to provide a more robust programming experience.

SOA.  Service-Oriented Architecture.  This buzzword has been around for quite a while now and in the last year and a half or so Microsoft has taken quite a step into anchoring themselves into the SOA soil.  It wasn’t too long ago that they announced that they were working on something really cool called “Indigo” and that it would be the latest thing that should be added to the Service-Oriented application utility belt.

The more developers read about “Indigo” they realized that it wasn’t anything to sneeze at.  They read about a fusion of current distributed-system technologies and ease of deployment.  They read about increased productivity and, lo and behold, a single programming model.  So, we (I am including myself in this “we” and “they”) began to ask “What is Indigo?”.