New features in a service pack!?!

With the beta release of VS2008 SP1 and .NET 3.5 SP1 there was something that struck me as quite odd. Isn't a service pack meant to contain only bug fixes? Not brand new features (ADO.NET Entity Framework, ASP.NET Dynamic Data, ASP.NET Routing, the list goes on)?

This got me back to thinking about a query I raised at the last VBUG Newcastle event when Richard Fennell was talking about VS2008 and discussed the different versions of the .NET Framework.

What happens if I build in VS2008 for a 2.0 solution and use something that is only is 2.0 SP1 but then try to run on 2.0 RTM?

I only realised this when doing some work with Communtiy Server 2.1. It has it's own SortOrder enumeration but when I moved the solution to VS2008 from VS2005 it wouldn't build as there is a new to 2.0 SP1 enumeration in the System.Data.SqlClient namespace called SortOrder. Both namespaces were imported so the compiler couldn't resolve which one was intended. An easy change to get this working but won't this cause problems?