EO2 Clarifications

In my previous blog post, I made a couple of statements about the new 2.0 CTP which I wish to clarify further, so there's no misunderstanding.

C# only

What I meant with this statement is that only the C# templates have been upgraded to generate the correct code. The VB template still generates 1.1-compatible code. This doesn't mean VB users are completely left out! If you are a VB user, create a separate DLL project in C# and generate your abstract classes in C#. Then create your concrete classes in VB and inherit from the abstract C# class. This is not ideal, but I will let you know here on the blog when I post updated VB templates.

SQL Server only

Again, I may have left you with the impression that the Oracle users are left out. This is not the case. What I removed was the ability to switch between Oracle and SQL Server with the DynamicQuery class (controlled by configuration). I did this by commenting out the switching code and just hard-coding the SQL Server class in its place. If you need Oracle, just replace the SqlDynamicQueryProvider with the Oracle one. The only thing you can't truly do in this version is switch between the two dynamically at runtime.

I hope that clears things up!