485
edits
Upgrading workspaces to a newer Visual DataFlex version: Difference between revisions
From DataFlex Wiki
Jump to navigationJump to search
Upgrading workspaces to a newer Visual DataFlex version (view source)
Revision as of 19:14, 21 January 2009
, 21 January 2009→External links
| (5 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
==== Upgrading workspaces ==== | ==== Upgrading workspaces ==== | ||
This is a subject that comes to revisit you at times and there are several ways in which you can tackle this little beastie. Ever since VDF8 there is a special wizard that helps you in migrating your applications from one version to another. | This is a subject that comes to revisit you at times and there are several ways in which you can tackle this little beastie. Ever since VDF8 there is a special wizard that helps you in migrating your applications from one version to another. | ||
However simple this event may seem for small projects, once your project is a little bigger you do want to plan this carefully. You do not want to give your end-users the typical "we added this and broke something else" experience that all too often happens. Does that sound familiar? Then have a look at the tips below.. If not, then you're the perfect developer and this doesn't count for you. | However simple this event may seem for small projects, once your project is a little bigger you do want to plan this carefully. You do not want to give your end-users the typical "we added this and broke something else" experience that all too often happens. | ||
Does that sound familiar? Then have a look at the tips below.. | |||
If not, then you're probably the perfect developer and this doesn't count for you.. do go read about some cool new tech on [http://slashdot.org /.] instead. | |||
==== Decisions, decisions ==== | ==== Decisions, decisions ==== | ||
| Line 12: | Line 16: | ||
# Stay up to date all the time... (DAW loves you!) This seems like a very nice goal and is only feasible if you have a product that is in tight control deployment wise. If you have to deploy at a thousand locations then this isn't likely for you.. (you don't want to overload your support desk or do you?) | # Stay up to date all the time... (DAW loves you!) This seems like a very nice goal and is only feasible if you have a product that is in tight control deployment wise. If you have to deploy at a thousand locations then this isn't likely for you.. (you don't want to overload your support desk or do you?) | ||
# Stay one version behind.. This is a more traditional approach where you take the time for the product to evolve and for your development and Q&A teams to find the version specific flaws. This works fine for most products, but is less do-able with Visual Dataflex. Why? DAW does not have the habit of patching older versions -even while they claim to support it- so that's a downside of this approach. Instead they tell you to move over to the newer betterer version (with newer bugs too... DAW are you reading this? Do YOU want us to update more often so YOU can sell more client licenses? Then make this scheme work and port your patches into all ''supported'' versions!) | # Stay one version behind.. This is a more traditional approach where you take the time for the product to evolve and for your development and Q&A teams to find the version specific flaws. This works fine for most products, but is less do-able with Visual Dataflex. Why? DAW does not have the habit of patching older versions -even while they claim to support it- so that's a downside of this approach. Instead they tell you to move over to the newer betterer version (with newer bugs too... DAW are you reading this? Do YOU want us to update more often so YOU can sell more client licenses? Then make this scheme work and port your patches into all ''supported'' versions!) | ||
# Switch on over when a good stable major version is released with enough new in there to make your users happy. | # Switch on over when a good stable major version is released with enough new in there to make your users happy. So for example switch from VDF 11.1 to VDF 14.0. This means you don't have to wait on your last version per definition.. pretty soon for example you could change this from 11.1 to VDF14.1 if that fancies you more. | ||
So for example switch from VDF 11.1 to VDF 14.0. This means you don't have to wait on your last version | |||
Suppose you already guessed what my favorite is? No? Correct, I'm on that last scheme, but don't let that stop you from following your own path. It works for me, that doesn't mean another upgrade scheme doesn't work for you. | Suppose you already guessed what my favorite is? No? Correct, I'm on that last scheme, but don't let that stop you from following your own path. It works for me, that doesn't mean another upgrade scheme doesn't work for you. | ||
| Line 38: | Line 41: | ||
* Move class definitions that ended up in your views and reports and put them in their own files. The studio doesn't like this type of construct. If you nested your class definition in your view, it is likely to cause your view not to be able to render itself in the designer. | * Move class definitions that ended up in your views and reports and put them in their own files. The studio doesn't like this type of construct. If you nested your class definition in your view, it is likely to cause your view not to be able to render itself in the designer. | ||
* Use the latest migration wizard you can get your hands on. The VDF14.1 wizard will catch more as the VDF14.0 one. Even if you are eventually going to migrate to VDF14.0, use the one from 14.1 for refining your code. | * Use the latest migration wizard you can get your hands on. The VDF14.1 wizard will catch more as the VDF14.0 one. Even if you are eventually going to migrate to VDF14.0, use the one from 14.1 for refining your code. | ||
==== Troubleshooting ==== | |||
* The AppHtml folder is not included in my migration | |||
Is the folder physically inside your project structure? Is it in your workspace? | |||
* The datadictionary files are not migrated and changed into the new syntax. | |||
Are all your DD classes registered in DDClassList.xml? | |||
==== External links ==== | ==== External links ==== | ||
| Line 44: | Line 55: | ||
* Why doesn't that webapp work in the newer VDF.. [[Object required global.asa error]] | * Why doesn't that webapp work in the newer VDF.. [[Object required global.asa error]] | ||
* Data Access KB article [http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2400 INFO: Why did some of my files not get migrated (when upgrading to VDF 12 and higher)? ] | |||
