depends on the framework and the update. most framework updates try and maintain backwards compatibility, although fusebox 3 to fusebox 4 was an exception to this.
Your choices are always to stay put or upgrade with any associated effort involved, same as with any software. To stay put cuts you out of furture advantages and sometimes you are forced to upgrade by circumstances (like a CF server upgrade which means your old framework code no longer works). But I guess you know all that :-) On 5/18/06, george. earl @ ssa. gov george. earl @ ssa. gov < [EMAIL PROTECTED]> wrote: > > So what happens when you adopt a framework and you build a bunch of stuff > using this framework and the framework has one of its regularly scheduled > updates to a new version? > > What are the implications for the existing applications written using the > old version of the framework? > > I assume you can either continue to use the old version of the framework > or you can migrate the application to the new one. > > Typically what is involved in updating an application to a new version of > a framework? Does it require an extensive rewrite of the application or are > old framework modules simply replaced with new ones? > > What if you have this huge application that is growing and will continue > to grow into the foreseeable future and you want to keep in step with the > updates to the framework you have chosen? How do you handle this? > > Thanks! > > George > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240887 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
