Timeline for How does Sitecore handle serialization with TDS?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Nov 26, 2018 at 15:01 | comment | added | tjans | I'm not familiar with the validation section, but I will look it up, thanks. | |
| Nov 22, 2018 at 4:28 | comment | added | Chris Auer | You can use the Validation section of your TDS project to ensure that if the home node is there, that it is Deploy Once. Or use the validation to make sure it is never there. hhogdev.com/help/tds/propvalidation/tdsa002 hhogdev.com/help/tds/propvalidation/tdsa006 | |
| Nov 21, 2018 at 22:27 | comment | added | Pete Navarra | Added Troubleshooting steps | |
| Nov 21, 2018 at 22:23 | history | edited | Pete Navarra | CC BY-SA 4.0 |
added 425 characters in body; deleted 1 character in body
|
| Nov 21, 2018 at 22:20 | comment | added | Pete Navarra | Yeah, its hard to say. These are likely scenarios. I am going to add a troubleshooting step into the answer. | |
| Nov 21, 2018 at 22:10 | comment | added | tjans | Thanks, like you said, customizing Sitecore to do automated serialization isn't likely, as we control the code-base pretty tightly. #2 seems plausible, though we've never seen caching like that hang onto an item for that long. | |
| Nov 21, 2018 at 22:06 | history | answered | Pete Navarra | CC BY-SA 4.0 |