ToddFrankson 14 Posted 18 hours ago 9 hours ago, Uwe Raabe said: Unfortunately the migration tool just copies the Known Packages list from 12.3 to 13 per default. This can only work when packages are binary compatible like from 12.2 to 12.3, but as packages from 12.3 cannot work in 13 the failing is expected. There are means to use the migration tool in a way that avoids this, but it requires some manual steps. Known Packages and Experts cannot be migrated between major versions, so you always need to compile (or get the right versions from the vendor) and install these packages and dlls with D13 anyway. I would love to see the migration tool getting some love for its details and default behavior. As it often is used by less experienced (or lazy) users, a stable and correct click-and-run experience should be mandatory. I never used it before. The first time trying it. Sad it isn't smarter or easier to use. Share this post Link to post
Anders Melander 2116 Posted 16 hours ago (edited) 12 hours ago, Uwe Raabe said: Unfortunately the migration tool just copies the Known Packages list from 12.3 to 13 per default. This can only work when packages are binary compatible like from 12.2 to 12.3, but as packages from 12.3 cannot work in 13 the failing is expected. That's not entirely true. If you do an Upgrade migration then it copies the package settings. If you do a Version migration then it doesn't. The UI could have made the distinction clearer... [Edit] Sorry, I see you already made this point. For some reason you later posts didn't show when I wrote the above. The forum has been extremely slow for me the last few days. It's almost unusable. We're probably getting DDOSed harvested by some engine. Edited 16 hours ago by Anders Melander Share this post Link to post