This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hey there, I've encountered a problem with LS4's migrations. On one of my machines, LS4 migrations cause VS2010 to crash.
Machine specs : Intel dual core + Win7 Professional (32bit) 2 GB Ram + VS 2010 ultimate. I've recently re-installed the VS after much fighting with the installer. Database is MySQL 5, connector ver is 6.3.7
When "creating" a migration - VS 2010 crashes and restarts. There's no error message or log (unless I don't know where to look). After the restart, the migration code is present in the solution. (I have reason to suspect that Ankh SVN is to blame - but I can't be sure - when I disabled the source control and "created" another migration VS didn't crash) When "running" a migration - only the dbversion table is generated, otherwise - no effect. connection defined via connection string + provider. When "running" a migration in "Generate SQL" mode w. Database disconnected option - no effect is visible, no new window with generated SQL etc. When "running" a migration vs a connected database with connection from the server explorer specified explicitly - it seemed to work, no crash, and the tables showed up properly. If possible, let me know how to retrieve more details so that I can provide you with more info. Cheers. |
|
|
|
|
When "running" a migration vs a connected database with connection from the server explorer specified explicitly - it seemed to work, no crash, and the tables showed up properly. I take it back, it didn't work for me this time. only the dbversion table got created. In the mean time I've noticed an error window saying that an app domain has been unloaded. |
|
|
|
|
Hmm, we use AnkhSVN and haven't seen any problems, but it's possible your configuration is slightly and fatally different. I've added some diagnostics to try to identify the crash error when creating the migration -- could you try it again with the next nightly build and let us know what comes up including the exception detail? Thanks! (NOTE: The diagnostics are only in LightSpeed 4 at the moment. If you need to stick with LS3, let me know and I will backport them.) It's likely, though not certain, that the issues when running a migration are related to the issues when creating one. Both paths you describe should display messages on any exception, though, so it's possible something deeper is going on. Hopefully we'll have a clearer idea whether this is the same or a different issue once we get the diagnostics from the "create" issue. One thing you could try is dropping back to MySQL Connector 6.3.6 in case there is a versioning issue. We don't think this should be an issue but it could be worth trying just to eliminate it as a possible source. |
|
|
|
|
Also, just to confirm, this is happening on one of your machines, but not on others, right? |
|
|
|
|
Correct, it's happening on my laptop (x86 OS), my desktop (x64 OS) seems to be unaffected. |
|
|
|
|
I'll be sure to try to "trace" that error asap. I need to hit the sack now, it's 2 am lol |
|
|
|
