What steps will reproduce the problem?
1. run wizardby info /c:<any valid connection string>
2. The connection string from command prompt is never used.
What is the expected output? What do you see instead?
Is expected that Wizardby uses the connection string passed by the command line
parameter. Instead, it uses the parameters in database.wdi.
What version of the product are you using? On what operating system?
1.0a3, on win7 x64 (using x86 binaries)
Please provide any additional information below.
This issue seems to be in how MigrationCommandBase.cs handles
parameters.ConnectionString. At line 130, parameters.ConnectionString is always
assigned with one built from dbPlatform. I didn't test it, so I could be wrong.
Original issue reported on code.google.com by danl...@gmail.com on 1 Mar 2011 at 6:16
Original issue reported on code.google.com by
danl...@gmail.comon 1 Mar 2011 at 6:16