Comments on: Deploying patches in your Flex application http://flexblog.faratasystems.com/2007/12/24/deploying-patches-in-your-flex-application A blog about our experience with Adobe Flex Tue, 31 Jan 2012 19:52:28 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Yakov Fain http://flexblog.faratasystems.com/2007/12/24/deploying-patches-in-your-flex-application/comment-page-1#comment-34714 Yakov Fain Wed, 02 Jan 2008 10:58:13 +0000 http://flexblog.faratasystems.com/?p=279#comment-34714 A patch is a patch. It's a temp solution between scheduled releases. Many enterprises have pretty strict and formal release procedures, and releasing just one patches.swc, even if it has a bunch of classes, can be a viable solution. Italso may be easier to approve an emergency release that consists of replacing just one file patches.swc with another one. Needless to say that you are implementing the same changes in the original classes located where they're supposed to be, and on the next scheduled release you empty patches.swc. A patch is a patch. It’s a temp solution between scheduled releases. Many enterprises have pretty strict and formal release procedures, and releasing just one patches.swc, even if it has a bunch of classes, can be a viable solution. Italso may be easier to approve an emergency release that consists of replacing just one file patches.swc with another one.

Needless to say that you are implementing the same changes in the original classes located where they’re supposed to be, and on the next scheduled release you empty patches.swc.

]]> By: barry.b http://flexblog.faratasystems.com/2007/12/24/deploying-patches-in-your-flex-application/comment-page-1#comment-34685 barry.b Wed, 02 Jan 2008 00:11:36 +0000 http://flexblog.faratasystems.com/?p=279#comment-34685 I can see how that works fine for small changes, but what about changes that have dependencies? where you're needing to update a bunch of classes that are from different parts of an application (eg a new minor feature that adds UI, processing, code from different parts of the application, etc). I can just see that lumping all that into a "patches" swc may be a bridge too far. thoughts? I can see how that works fine for small changes, but what about changes that have dependencies? where you’re needing to update a bunch of classes that are from different parts of an application (eg a new minor feature that adds UI, processing, code from different parts of the application, etc). I can just see that lumping all that into a “patches” swc may be a bridge too far.

thoughts?

]]>