sitecore7 - Sitecore TDS Deployment Property Setup Guide -

sitecore7 - Sitecore TDS Deployment Property Setup Guide -

we using tds 5.0 sitecore 7.2 solution.

could please help best practices following?

which config take current config? which kid sync state take , items? which deploy setting take items?

basically i'm after best practices has worked project experience.

thanks.

the settings take tds project setup have lot of solution is. next best practices use:

current config:

this value based off build configurations. typically have debug, test, , release configurations, each configuration corresponds different deployment environment (your test sever, production server, etc.) set setting each item based on whether want item deployed in particular configuration. e.g. utilize current config - exclude not include test info items in release/production build.

child sync state:

the value utilize depend on item , particular intentions of solution.

for template items, best create sure child sync - children used, why template modifications create picked when perform sync operation.

for items under content tree (/sitecore/content), value utilize vary based on purpose of item. if illustration site has folder item news items, set kid sync state news folder child sync - no sync unlikely new items create in development environment needs automatically synced project.

if need sync direct children of item , not children's children (descendants) utilize child sync - direct descendants option.

deploy:

use deploy - once bulk of items in tds project. tell generated bundle deploy item if doesn't existing in database beingness installed to. means can ensure solution critical items nowadays in target environment, if have been modified in environment, bundle not overwrite existing changes.

such illustration home page item website. want create sure there, have been modified content authors between releases.

use deploy - always if want bundle overwrite existing item in target environment values have in source control. best not utilize setting on items content authors editing, otherwise lose of info occur making content authors upset.

additional: utilize deploy - always on template items since assumption template items in source command required create tested solution work. hence want override changes made in target environment ensure have stable instance.

sitecore sitecore7