12/2/2009 6:36:15 AM
RE:Precompiling and deployment
I think you have not missed anything. Regrettably the design of content staging does not allow this (in 5.0 it will be little bit improved for 2 server scenario).
You development scenario is pretty complicated. There is no ideal or easy to implement way for this. Using the content staging the synchronization works fine only in one way. If you will configure the staging also backwards, it can cause a loop in the synchronization tasks.
One option is to define a strict development and testing rules - for example when changing page template, the IDs of editable regions have to be the same, so the content won't be lost after the synchronization, or after you will push the new object to testing or live. This can work fine if on the live will be only content changes, but you need to be careful also when changing e.g. document types definitions and so on. You can push them to testing and after it will pass, you can reflect them on live server and ensure manually that no content will be lost or that the web parts will be set according to the live environment.
If you will do changes in object only on your development, you can use the import export of objects and select them according to the change date. But again, if you will change e.g. a page template and remove some web parts, or document type, you need to take care of it on the live server.