Le Roi Est Mort, Vive Le Roi!

Now that SQL Server 2008 is out the door, I’m full throttle on my new job. I’m totally excited about the improvement I’m working on, and I can’t wait to start blogging about it (once it’s out of secrecy.)   Today I’m only changing the outlook of my blog to reflect my new emploi. Yes,…

2

Moving On…

I have to admit publically that I’ve decided to take on new challenges unrelated to EDM and Entity Framework. Starting today I’ll be working on the lower levels of the SQL Server Connectivity stack.   I’d like to thank all of you who’ve been reading my Entity SQL blog and who’ve been using Entity Framework….

2

New version of eSqlBlast – compatible with .NET Framework 3.5 SP1 Beta

The .NET Framework SP1 Beta-compatible version of eSqlBlast is available at http://code.msdn.microsoft.com/esql/Release/ProjectReleases.aspx?ReleaseId=991. The release includes a source code zip as well.    The SP1 Beta distributions of .NET Framework 3.5 and Visual Studio 2008 are available through: http://msdn.microsoft.com/en-us/vstudio/cc533448.aspx

1

Primer to EntityConnectionStringBuilder

Following the spirit of Primer to ConnectionStringBuilder from ADO.NET 2.0, let’s see how the pattern has evolved in Entity Framework.   Building an Entity Connection String from Scratch What’s important to keep in mind before we dive into code samples, is that an entity connection string consists of two separate connection strings – one for…

1

Why Should I Use Entity Framework?

If your app is small enough, i.e. you write your own database schema (for SQL Server) and you write the only app over that schema, you don’t really need Entity Framework. In that case, you may consider LINQ to SQL.   Now let’s think big. Let’s say you are an app/service vendor but your are not…

2

eSqlBlast on Code Gallery

MSDN Code Gallery is now live! It’s a place to download compiled binaries rather than source code. The latest eSqlBlast is available at http://code.msdn.com/esql.

0