Q: In watching the keynote at TechEd, the "GDR release will support DB2". Since DB2 isn't just DB2, can anyone tell us if it will support
DB2 on iSeries? (yes there are differences, EF doesn't support DB2 on iSeries)
A: IBM is the only authoritative source to answer, but the way I understand it is that the current implementation targets their DB2 implementations on Windows, Linux and AIX, since it is a shared implementation. They are actively evaluation the need to support the other versions.
Q: In watching the keynote at TechEd, the "GDR release will support DB2". Since DB2 isn't just DB2, can anyone tell us if it will support DB2 on iSeries? (yes there are differences, EF doesn't support DB2 on iSeries)
I am not sure what you mean with "SQL Server Schema parts" that is a term that I am not familiar with. Please educate me on what this is or means.
With regards to plans to add Oracle support, we cannot make announcements on behalf of other companies. Microsoft will not develop providers for other data stores, but we are working with all major vendors and 3rd parties to make sure all major data stores are covered.
The index that gets dropped in the demo is a bug in the system right now, we only need to update text based objects like functions, default constraints, check constraints etc when renaming a column.
I will record a Camtasia once I am back in Redmond.
The deployment engine is two .NET assemblies, one core and one provider assembly.
However there is no direct way to run managed custom actions from an installer, which is what you would have to write to make this work. The reason why the installer folks do not like this is the unexpected behavior if you load mixed version assemblies from the same host.
The supported way will be to run a command line version from a custom action in WiX. We will provide a command line shell, vsdbcmd.exe, which will be able to deploy a .DBSCHEMA file. I will be demonstrate this on Friday at TechEd in my session TLA320.