T414 Sitecore Best Practices Part 2: Solution Structure and Working with TDS
Posted 02/07/2012 by techphoria414
The T414 Sitecore Best Practices Series is a screencast overview of the foundational pieces we use at Hanson Dodge Creative in our Sitecore development projects. Part 2 dives into the specifics of Visual Studio solution structure, TDS project configuration, and using TDS.
Part 1: Introduction to TDS is available here.
Part 3: Sublayout Development with Custom Items and Scriptlets is available here.
Sean Holmesby of Igloo Digital has a nice series of posts that also get into some details of TDS use and configuration, including some known "gotchas" that you may run into.
If you're having trouble getting your Sitecore.* DLLs to copy on build, check this out.
Francesco Gallarotti said:
5/14/2013 2:16 AM
Hi Nick, I just wanted to thank you for the time you are taking making these screencasts. It's nice to be able to virtually sit next to someone like you and take a peek at what are your best practices. It's very generous of you to share this with the community!
Mark Ursino said:
5/15/2012 12:31 PM
Nick, after I posted here I reached out to TDS support and brought up the Sitecore.*.dll "feature". It turns out its an issue for us because our project is of the form Sitecore.SharedSource.xxx.dll. I was told v4 of TDS will have a built-in way to change that. For now, we've taken another approach and created another assemblies folder in our web app, e.g. "bin_deployableAssemblies". Our Sitecore.SharedSource.xxx project output to that folder, then we use File Replacements in TDS to copy to our web root. Thanks for the feedback! I'll stay tuned...
Mark Ursino said:
5/15/2012 6:10 AM
Nick, this is an awesome video! We're using it to structure our TDS solution. Quick question: how do you manage 3rd party assemblies referenced in a project of your source so that they are copied to the web root upon a TDS build? We found that some but not all DLLs in the /bin/ are moved over. We're considering an approach of an extra folder of assemblies and using the File Replacements feature of TDS to copy them over upon a build. I'm curious how you have managed this. Thanks!