Don't forget also the language packs for WSS and MOSS.
I just got Julia ("Julie") Lerman's Programming Entity Framework book. You will find her site here.
I like the book, and I like EF, but I wasn't aware of the many limitations that the current version of Entity Framework has, particularly when comparing to LINQ to SQL. I will post some of my findings here, in future blogs.
If you are using Oracle Database Provider for .NET (ODP.NET) and you want to use TransactionScope'd transactions, you may have gotten the dreaded "Data provider internal error(-3000) [System.String]" exception. I'll explain how I fixed it.
First, if you want to support distributed transactions, make sure you have the OracleMTSRecoveryService service installed and running on your machine (it comes with the Oracle Data Access Components installation), or any other machine on your network, as long as properly configured on the MSDTC tab on the Component Services applet.
If you don't need distributed transactions, you can place the connection string setting PROMOTABLE TRANSACTION=LOCAL on your connection string, for example:
DATA SOURCE=(DESCRIPTION=(ADDRESS=(COMMUNITY=TCP.Some.Community)(PROTOCOL=TCP)(HOST=Some.Host)(PORT=1522))(CONNECT_DATA=(SID=SomeSid)));USER ID=SomeUsername;PASSWORD=SomePassword;PROMOTABLE TRANSACTION=LOCAL
Now you can have:using (TransactionScope tx = new TransactionScope())
con.Open(); //no longer crashes herecmd.CommandText = "SELECT sysdate FROM dual"; DateTime date = (DateTime)cmd.ExecuteScalar();
If you need more information, check the Oracle Data Provider for .NET Developer's Guide, it's the e10927.pdf file on the B28359_01\win.111 folder of the Oracle documentation (version 11g).