I’m now playing with Entity Framework and Azure. Stay tuned, some posts are almost finished.

Best example yet on peeling back the covers underneath DbContext.

Curious how you learned all of the various methods that can be applied to objects for the EF metadata creation behind the scenes? Is there a documentation resource you went to in order to learn these? (They don’t seem intuitive).

I also noticed you have a SqlConnection object you pass into DbContext upon instance creation, instead of allowing DbContext to create it by itself. I think this approach lends itself to replacing the SqlConnection with a new class that can handle SQL Azure connection retry logic very easily as well, since EF doesn’t handle this out of the box, and deploying any Code-First type approach on SQL Azure today will cause problems without that logic in place.

Have you experimented yet with using Code-First on SQL Azure and investigated what changes you’d have to introduce to make your “connection” object more robust, while keeping your code elegant?

There are a few examples on the web (not very elegant), including an implementation of a SqlAzureConnection, but I haven’t seen an implementation yet that uses it with Code-First.

Sure. Firebird has no idea whether database exists, until you actually use it (but if this fails, it may be as well wrong username etc.). There’s no master database.

FirebirdClient, as name suggests, is about Firebird. With InterBase you should use provider for InterBase.

Database.SetInitializer(null);

And often the application has more layers so the annotations may not be available to UI or the UI needs more validation than that.