8

I am working on migrating an existing solution to Helix conventions. The existing solution has TDS projects for Master, Content and Media. How do I set up TDS projects in the newly refactored solution following Helix conventions?

Improve this question
4
  • That sounds pretty broad. What aspects of TDS project setup are you wondering about, exactly?
    – Dmytro Shevchenko
    Commented Dec 16, 2016 at 14:54
  • Basically I am looking for some understanding on how to set up TDS projects in a Helix setup? For example we are not using transforms for config files. We are using TDS file replacement to deploy environment specific config files. Secondly, how do we go about syncing items? Does all of that remain the same or would change now that we are implementing Helix conventions? And also, in which layer of solution should I besetting up TDS projects? Foundation, Feature or Project?
    – Hetal Dave
    Commented Dec 16, 2016 at 14:59
  • 1
    Have you seen this repository? It contains an example project structure with TDS that follows the Helix guidelines.
    – Dmytro Shevchenko
    Commented Dec 16, 2016 at 15:06
  • You create a TDS project for each feature, foundation and project. The code and serialization needs to be separate for each project.
    – Chris Auer
    Commented Dec 16, 2016 at 15:40

1 Answer 1

Reset to default
5

I tried to find a commit when Habitat when it used to be TDS (https://github.com/Sitecore/Habitat) to no avail. But what you want to do is create a TDS project for each Feature/Foundation/Project. In the same way that their is a Unicorn serialization folder for each Feature/Foundation/Project, you would do the same TDS.

Improve this answer
3

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.