The saving grace here is .Net. The CLR is the great religious equalizer. Regardless of the syntactical implementation of personal and team preference, it all gets compiled to run on the CLR. We all bow and pray to the Father, Son, and Holy Microsoft. (I'm a VB and C++ and C# developer)

Oh, don't start the debate as to where the best cars come from.... it's not Japan!

I believe you can script the DB objects, but not the data. I have been wondering myself how to do this with scripting... The way we handle the problem is to include a script, which is run to create the tables, views, SPs, etc. Then, we also ship an XML file of "base" or "setup" data that we load into a dataset, and then save to the database, right after initial setup.