I'm in the process of doing this now.  And 4.0 to 6.1 before that - on
another box.  For the most part the update is going well.  I have a few
niggling details with how variables are referenced, but that has been the
biggest issue to date.

The "code-scanner"  in the administrator can be helpful but it will not
catch everything.

It will probably depend a lot on how many less obscure features you use too
- if any.  The one that reads and writes windows registry is the one that
comes to mind.

-Nate

> -----Original Message-----
> From: Mark Fuqua [mailto:[EMAIL PROTECTED] 
> Sent: Monday, February 05, 2007 3:15 PM
> To: CF-Talk
> Subject: RE: moving from CF 4.5 to 7.0
> 
> No personal experience, but I think the info you find about 
> 4.5 to MX or
> especially 6.1 would translate well.  I think 7.0 was mostly 
> about adding
> features and fixing bugs, not a big rewrite of the code base.
> 
> Mark
> 
> -----Original Message-----
> From: So Kenfused [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 05, 2007 2:49 PM
> To: CF-Talk
> Subject: moving from CF 4.5 to 7.0
> 
> 
> Just started a new job and they are looking at moving from CF 
> 4.5 to CF7.
> We do have a Dev box, so we can play a little before doing it on the
> production boxes.
> 
> I'm finding several posts about going from 4.5 to 5, or MX 
> and the issues
> people ran into however, I am wondering if anyone who has 
> made the jump from
> 4.5 to 7 can provide details to any issues they might have 
> experienced.
> 
> 
> 
> 
> 
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Upgrade to Adobe ColdFusion MX7 
Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs 
http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268747
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to