I have some migrations that are seeding data with NHibernate.
My nant scripts are passing the appropriate connection string to the runner.
Can my C# code in a Migration, being run by the nant migration task, get the connection string that was passed to the runner and pass it along to nhibernate?
Right now, the connection string is not exposed in the migration. But it wouldn't be too hard to change that.
Anyone got an opinion on this?
I am also using NHibenate inside some of the migrations and I would love to be able to access the connection string passed by the runner. Right now I am using the ApplicationContext to pass the connection string (again).
Ok, I'll fix that.
That sounds good, thanks!
Closed by pull #414