I know this has been a long time coming and there are enough good and bad excuses, finally a post about my talk at TDS this year. In case you've missed my talk. Below the video are my slides. The MS Build toolset is still in progress and will be released very soon (I promise! Stay tuned)! Enjoy! To watch
read moreLast wednesday (18th of November 2015) I gave a small talk about my work on DD4T.NET 2.0. I've done some work on how DD4T.NET 2.0 is distributed to developers and clients. I hoped you enjoyed it, for those who weren't there enjoy it too! Here are my slides: Slide 1 My start slide. Slide 2 So,
read moreWhen developing compound templates for SDL Tridion you might want to use the Post Build trick that is explained in the SDL Tridion docs here, but there is a generic solution for all of your projects. First create a TcmUploadAssembly directory in the root of your solution folder. Put the TcmUploadAssembly files there and generate the config.xml here too.
read moreThe way we're developing SDL Tridion websites is changing. We we're used to templating everything in Tridion and Tridion was our version control system. The web application we published were jsp pages, aspx pages, or pages based on some other technology. We're moving away from this way of working now and we're moving towards Software Development. We're hearing things like
read moreAs a Tridion developer I'm used to adding the Tridion dll's and jar files to the source code. But this isn't the way it should be done. There are better ways to organize those dependencies. In a purist thought, there is no place for compiled code in your source code repository. Nexus You already know about NuGet right, that package
read moreDid you know that DD4T metadata for component templates support more than just the view name? You can also provide a controller and an action. This allows for some powerful new options. If for example you've created a custom forms solutions, you could create a seperate FormsController. This controller will then be called instead of the default ComponentController for the
read moreWhen deploying a .NET application on multiple environments you have to deal with multiple configuration settings for each server. This can be fixed by creating multiple packages, publishing from Tridion or creating parameter files. MSDeploy parameter files Multiple packages takes too long to finish and there are multiple files you might want to change. That will take multiple transform files.
read moreQuirijn Slings wrote a post about previewing pages using DD4T and a Configuration file. There is an alternative for configuring previews. In the preview TBB there is a hidden feature (nobody blogged about it I think) that is looking for a metadata variable on the Publication Metadata called "StagingUrl". This variable is used to POST an XML to that url.
read moreWhen using DD4T or using dynamic publishing with a .NET application you might want to have a writable directory to store your binaries. When using Web Deploy, you can choose to do this when you publish. Create a file called [ProjectName].wpp.Targets where [ProjectName] is the same name as your .csproj file of your Web project. Copy/Paste the
read moreDo you remember Tridion Deployments to be copy paste tasks, Running Content Porter to transport to your Test, Acceptation and Production environments? Always forgetting some dependency? DLL files, css, js files and other static dependencies need to be copied from one environment to another. Creating large installation instruction documents. It is deployment hell... Let's make it a bit easier This
read more