Install your app in dev/test against a clean install of MX 6/7 and start pounding on it. It is almost guaranteed that some stuff will break- things you may not realize are even a problem. If you want to have a smooth transition you will test everything in your application using detailed test scripts to verify functionality. Otherwise stuff is bound to fall through the cracks.
I had one developer who was fond of using a variable called "url". That worked in CF5 but in MX it is reserved for the url scope. There are all kinds of little things like that you will find when you start digging into your app. How much pain you experience depends on how your code is written. In my example above, that was a poorly named variable and should have never been in our code-base to begin with. >All, > We are in the process of moving our CF5 sites to MX6 or MX7. We >have a custom built CMS which talks to a SQL 2000 server. > > I'm looking to compile lessons learned from those who've already >gone through this in an effort to minimize my frustration when bugs >crop up etc. > >Thanks in advance >jonese ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194359 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
