Best practice for developing with LiveCycle Workbench ES2 – Application structure, iteration and transition

This blog has been posted to LiveCycle Product Bloghttp://blogs.adobe.com/livecycle/.

Please visit and comment the post there. Thanks.
http://blogs.adobe.com/livecycle/2011/06/best-practice-for-developing-with-livecycle-workbench-es2-%e2%80%93-application-structure-iteration-and-transition.html

2 Responses to Best practice for developing with LiveCycle Workbench ES2 – Application structure, iteration and transition

  1. c@tc.se says:

    Hi mjiao,

    Thanks for your post. I’d be interested in hearing about best practises regarding maintaining conformance on dev, test and prod regarding versions of assets. It would be nice to be able to track versions of individual forms, e.g. Form.xdp version 1.13, between different environments.

    Also, what can you tell us about best practises regarding keeping multiple versions of the same application available? My experience is that we need to start each version of an application in descending order to have them published simultaneously. Obviously, there’s a better approach.

    • Mark Jiao says:

      I just posted another article “Best Practice for Developing with LiveCycle Workbench ES2 – Fixing Commonly Made Errors”. Please take a look whether it could help you. Some points say references may help you. Let me know if you have any other question.