This year the SDL Web Dev Summit India was hosted in Delhi and I had the opportunity to present about the Tridion Alchemy Framework.  For the presentation I ported to Alchemy an older custom ASP script to delete (and unlocalize) All Blueprint Children.  In this article I will highlight the process I used and include a link to the sourcecode.  I stil need to polish a few things before I add it to the Alchemy store, but please have a look at my code and hopefully it will help you in building your Alchemy plugins.

Screen Shot 2016-02-08 at 18.45.53

Here I will outline the steps I followed to write the plugin.  I won’t dive into too much detail, but I hope this will help you get started.

Prep work

Writing a plugin involves looking at some good code samples.  So, my first step was to download and install every Alchemy plugin and also every sourcecode repository that was available.

The latest version of the Alchemy VSIX Visual Studio Plugin has a nice Project Type called ‘Starter Plugin Project’. This creates a nice example with a button in the ribbon and also context menu. In my presentation I was able to go from File, New Project to having an Alchemy Plugin in my Tridion system in under 3 minutes.  The reason I like the starter project so much (aside form the fact it’s very easy and fast to use) is it has a great clean structure of the files and folders, and provides an excellent reference.

Writing the GUI

The GUI is now much easier to write and install than ever before (especially if you’ve done GUI Extensions!).  However, there is some rhyme and reason for a lot of the things in the Alchemy framework and I will try to highlight a few here.

1.  Create the Static folder.  This holds your Commands .js file (which is executed when you fire the GUI event, and the same one we used in older GUI Extensions).  Also in static you’ll have any .aspx popup files and css/js files your popup uses.   In Static I create a Commands folder.

2. Next create a new Alchemy GUI item, Alchemy Javascript Command
Screen Shot 2016-02-22 at 17.36.19


3.  In the .js file, I define a command name, ‘UnLocalizeAllCommand’ that is very important and will be used later.  I also borrowed some code from Mark Richardson’s ‘Real Time Publishing Stats’ plugin to open the popup .aspx file.  *Note – in this version your popup must be an .aspx file and not .html.  Otherwise, it will not be deployed to the views folder when you deploy the .a4t file.

4.  Under static, create a Views folder and in there the .aspx page for the popup.  The Javascript code to call the WebApi Controller (with CoreSevrice) was quite tricky to get correct.  You can see it here on Github

5.  Next is to Add the button to the GUI.  The context menu is added with ContextMenuUnlocalizeAll.cs and Ribbon is from RibbonToolbar.cs.

6.  Next we tell Alchemy what files to include for us with the ResourceGroupFiles.cs and PopupResourceGroup.cs files.

7.  With the PluginCommandSet.cs we specify the same command name we used in step 3.

8.  Now we could build and deploy the Alchemy Plugin and we should be able to see the items in the context menu and ribbon bar.  The last step is to add the functionality to do something.

9.  Create the controller, UnLocalizeController.cs,  in a new Controllers folder and make sure to reference the Core Service Client.  Here is where the main functionality is impemented.  Carefully look at the AlchemyRootPrefix attribute and also the Route attribute on the class.  These 2 parameters define how we access the service.

10.  Finally, build the project to create the .A4T file.  If you get annoyed with the alchemy popup window, disable it by opening your .csproj file (in Notepad++ you’ll need to run it with the Admin user) and follow my tip here to disable it for Dev.

11.  Drag and drop your .A4T file into the Tridion Alchemy GUI Admin and then refresh the GUI.  With a bit of luck and the right star alignment your new Alchemy Plugin should be working.  If not, use the browser’s JavaScript console to help debug any .js errors coming from the plugin.

Full Source Code is available here:


I hope this article helped you understand the flow of building an Alchemy plugin and assists you in your plugin dev.  Please share your plugins on the Alchemy WebStore so we can all benefit from the community.  Special thanks to Pankaj Guar for inviting me to speak at the SDL Web Developer Summit India!  Big thanks to Content Bloom and Alex Klock for creating the Alchemy Framework and sharing with the world!

1SDL Web India Dev Summit - Group

1SDL Web India Dev Summit – Group


Starting an Alchemy plugin project is super easy. In this post I just want to mention a quick tip that will help you use the latest version of the framework for your Alchemy potions.

1. Download the Alchemy4Tridion Developer Pack (VSIX Visual Studio Project template). This gives us some really cool filetypes in the File, New dialog:

Screen Shot 2015-09-29 at 17.36.35


2. After creating a new project, go to the Nuget Package manager and search for ‘A4T’ and install the framework. This makes sure your Alchemy DLL is the latest, and also gives you the goodness of the Visual Studio templates.
Screen Shot 2015-09-29 at 17.37.30


3. Get a good clean example to follow. As of September, 2015 this is the CopyInfo example from Alex Klock for me. The Big Box of Samples is intended to be the ‘Unit Testing’ plugin for the Alchemy devs, so lots of goodies to be found there too!


Have you built an Alchemy plugin that is a good starting point? Leave a comment below with a link to the source code. Thanks!

Update: The Alchemy Dev team has been at it again – they’ve added a checkbox to the popup GUI so we don’t need to anymore change the config file! The below tips were for an older version of Alchemy but today in version 1.03 they set it to ‘None’, so the correct fix to the config file would be:


Happy Plugin Making!

Getting started with the Alchemy Framework for Tridion GUI Extensions is made easy with the great documentation provided on the online A4T API documentation site.

When first getting started you might use the HelloWorld sample project or the Big Box of Samples project.  Both are great places to start exploring the structure of an Alchemy plugin.

After the exploration you’ll want to make a small change, possibly some new text in the popup in the BBS project.  The popup text is in the View files at /Static/Views.

Then you’ll build the project and get an upload to alchemy webstore popup.   While this is great and we want to use this when our plugin is ready, we probably don’t intend to put our personal Hello World project in the Alchemy webstore.

My Current Flow for Developing Plugins

(September, 2015)
1. Make a change in the VS project
2. Build
3. Open the Alchemy GUI
4. Uninstall existing plugin
5. Open windows explorer – drag and drop the .a4t file
6. Open gui and see change

Improved Flow

To help us all and also “celebrate the Anti-RSI gods”, Mark Williams has written a great blog post of how to automate the above steps, leaning on the PowerShell script from Jan Horsman. Get it setup to speed up your Alchemy Plugin hacking.


Writing Alchemy Plugins is fun and easy thanks to all the hard work Alex Klock and the team at Content Bloom have put into the Framework.  It’s quite addictive and has been described as a ‘lifestyle’ by Tanner Brine at this year’s Tridion Developer Summit Alchemy Presentation.  Good luck with your own alchemy concoctions!

1. Pair-programming is as much about learning new keyboard shortcuts as it is supporting the one doing the typing. We avoided many environment and coding issues by being able to swap people or computers when the going got rough.

2. Code > Powerpoint
3. Drinks > Sleep

4. Alchemy is not only a framework, it’s a way of life. Think of a WordPress plugins-type system all baked into Tridion, and with Dev tools that integrate directly into Visual Studio. Yes. Yes! This is the coolest thing since sliced Razor Mediator code!

5.  Using the Tridion Content Porter for moving Pages and all dependencies is like asking a car salesman for a car that flies.  Also, Content Porter is not called Magic Porter or Page Porter.

6. After 2 days of hard work our there was more talk about work on our off day than work on our work day

7. There’s a common feeling within the group of a ‘wish list’ of requested features.

8. Where there’s a song there’s a way.

9. Bottle-fed sheep eat during the middle of the night. Peacocks are louder than roosters.

10. Never look at John Winter’s phone when he says he wants to show you a photo. Ever.

11. Shellfish and Seafood are the same word in Portugese, and in English Shellfish and Sea Insects is also the same word (well, kind of)

12. Gin and tonic drinks never go out of style and they do a great job of making them in Portugal. (Ice in the glass first!)

13. When the bell rings, run for the bus.

Tridion VBScript Mediator*

April 1st, 2015 | Posted by Robert Curlette in Tridion - (2 Comments)

One of the many things I miss in Tridion 2013 SP1 is the ability to write VBScript code combined with Compound Templates.  Tridion was kind enough to provide the legacy pack for us ‘hardcore hackers’ who have our 10,000 line VBScript functions library perfected over the years in VBScript.  However, when we want to move to Compound Template programming, we’re left out in the cold with our VBScript skills and have to suffer with DWT, Razor, XSLT or C# coding.  Who wants to do that?  If we want to use the OOTB TBBs provided by Tridion to enable XPM or publish to FredHopper (for SmartTarget) the best way is to do this with a Compound Template.  But, Compound Templating and VBScript templates are not compatible – until now.

Using the VBScript Mediator we’ll have the best of both worlds – the fluency of the VBScript language and TOM API with the power of Compound Template modules.

First, if you don’t have it already, you’ll want to download the great VbsEdit program.  They have a really nice walkthrough on their homepage of all the features.

Next, you might want to download the VBScript Reference guide in case you’ve forgotten some of the commands in VBScript, such as setting an array to nothing.

Finally, go grab the code for the VBScript Mediator and start to have fun again with programming templates!

* This is an April Fools Joke!  VBScript in 2015….really?!

File, New Template

February 27th, 2015 | Posted by Robert Curlette in Tridion - (0 Comments)

Going back in time, year 2000, Active Server Pages was all the rage, performing server-side magic and integrating with databases with ADO. Tridion had just released version 4.0 and adopted the MS Scripting Host, supporting VBScript and JScript as the de-facto standard scripting languages. We had DTD Schemas, XML, Blueprinting, and re-usable content. Content Delivery was 1 ISAPI filter to render the dynamic links. Life was good.

Today the landscape is very different and complex, with lots of the magic happening on the front-end Content Delivery tier, Context aware web applications serving mobile and desktop devices, running the latest SDL Content Delivery stack.

Today the standard supported template languages from the CMS is almost the same as it was in 2000 – we publish content – .aspx or .jsp files, from the CMS to the Content Delivery tier. We can still use the good old deprectated VBScript language, or the SDL-created DWT scripting tags, or the recent XSLT mediator, if XSLT is your thing. So, you want to stay within the ‘supported SDL technologies and products’ arena – this is it. Not cool.

But, look around and see what the SDL community has been up to, and hang on to your hat! It’s been a very busy last few years in the SDL community and today this is where all the cool kids hang out. .NET MVC – got it, with DD4T, created by Quirijn Slings – with great Forum support (185 questions answered) on StackExchange, classroom training from Trivident, and even a ‘Reference Implementation‘ built BY SDL on top of DD4T, called DXA (as of Feb 2015). Yes, the Reference Implementation is built on top of open-source SDL community software, by SDL, and yet DD4T is community software and not officially licensed or supported by SDL.

Maybe DD4T and a dynamic MVC runtime is not your thing. Your content or design is not changing too often, and your development team is happy with the static publishing model from years past.

If this is the case then the best option today is the Razor Mediator, created by Alexander Klock – again an open-source project, and again the most cool and often used technology on new SDL Tridion projects requiring static template programming, and again not officially supported by SDL. It also has good forum support (50 answers), great documentation with plenty of examples, and is widely used. With this mediator you might publish to a .NET Web Forms site or JSP files to a Web Application.

The good news is both of these solutions play well with the _really_ cool technology SDL has been creating and supporting in the Content Delivery tier. Yes, I’m referring to the pieces that make up SDL Mobile, including the Ambient Data Framework, Context Engine and Contextual Image Delivery. In addition, all of these open source frameworks also play well with other SDL supported software including SmartTarget, FredHopper, and Media Manager.

The community has grown by leaps and bounds in the past 15 years, and today this is where all the cool stuff is happening. It’s great to see so many active members in the community. If you have written your own framework, or built on top of the existing great frameworks out there, please share your solutions so we can together build the great frameworks of tomorrow.  If you’re thinking about using one of the frameworks above, go ahead and embrace these open source frameworks and be part of the community that created them.

These frameworks and solutions would not be where they are today without the time and support of developers at these organizations:  Trivident, Indivirtual, HintTech, Building Blocks, Cap Gemini, SDL and Yabolka.  Also, a big thanks to Nuno Linhares for his continued support of the SDL Community and organizing of the SDL Tridion MVP program.

Using the Core Service we can easily get a list of all the Publish Targets in the system. We might want to do this if we are creating an app to publish items to a target (like the publish window) or if we want to Decommission a Publication Target in an environment, such as when we restore a database from one environment to the next.

The following code will get a list of all PublishTargets available within the context of a Publication. If you want to get all targets in the system then using the Admin user is the best. However, if you want to use the logged on user, then see my previous article to use the Core Service as the authenticated user (for a web app).

The data returned from the GetSystemWideList call changed between 2011 and 2013, and with the code below you will get all the info from the 2013 method. Special thanks to Likhan for the tip on the Tridion StackExchange.

The Tridion Core Service is a powerful API that gives us access to everything in the Tridion system. Sometimes we want to use an account with Admin permissions to get lists of items or delete items, for example. However, when creating or publishing items, we often want to do this in the context of the user logged into our Web Application built with the Core Service. This article is going to explain how to use the logged in user to perform Core Service actions and also give you a small debugging tip for Visual Studio.

Creating the Core Service Connection

I use a SessionAwareCoreService client which allows me to impersonate the user only with the username and not requiring a password. However, we do need port 2660 open between my local Visual Studio instance and the server if I debug against the server. Otherwise, if I work on my own local Virtual Machine with Tridion installed, I do not need to worry about this limitation. Then, after deploying to the server, it will work as expected.


Making it work in Visual Studio

This user is normally empty when debugging in Visual Studio and this caused a small issue for me. Luckily, I found this great StackOverflow post explaining the solution. The one that worked for me is this:

“look at the properties of the web project, hit F4 to get the project properties when you have the top level of the project selected. Do not right click on the project and select properties, this is something entirely different.

Change Anonymous Authentication to be Disabled and Windows Authentication to be Enabled.”

Happy Core Service hacking!

The Tridion Event System is used to automatically perform actions for us when an event is ‘triggered’, such as saving a Component or Publishing a page. While programming our Event System solutions we sometimes need to specify the name of a Schema, WebDAV URL path of a Component, or (gasp) a Tridion URI. We don’t want this in our code and it’s better to have it in a config file. However, the Event System is a ‘Class’ project type, and we can’t simply put an app.config file in the folder and expect it to work. In this article I’ll show a small code sample that will allow you to read values from a config file.


This original code comes from the Mihai’s Google Code solution here:

However, in Mihai’s article the code is fairly complex and has lots of functionality I didn’t need, and instead I prefer a more simple approach for getting the config file and getting a key. So, I’ve give the code a haircut and present to you just the bits you need to store the config values outside the Event System.


1. Create a config file and add your appSettings:

2. Name the configuration file the same as the Event System DLL with ‘.config’ at the end. Put the config file in the same place as the DLL. This might be in the Debug folder on your Dev system or in the Bin folder on the Tridion server. For example, TridionEventSystem.dll.config


Use the GetAppSetting(keyName) method to get your app.config variables.


If in your Event System code you use static variables they will be “cached” and stay in Scope as long as the Event System is running. If you restart the TCM Service Host and TCM Publisher services then the static variables will be refreshed.

I also use the .Net ObjectCache in the code to cache the values and this would be helpful in case your variables are not static in the Event System class.

External Libraries

Finally, a small note, but the Tridion Event System likes to have 1 DLL, so if you reference any external libraries, or if you create many .Net projects with the solution (that produce their own DLLs) then you will need to put those DLLs in the GAC or use ILMerge to combine them. So, in that case, when possible, use 1 .Net project for the Event System and minimize the abstraction of the layers into their own .Net projects, as is often done with .Net solutions. For example, I created a ‘Model’ .Net project for the Models to share between the Event System and another project, but in the end this proved to be too much of a headache and instead I moved the Models into the Event System project.

Happy healthy hacking!

OrmLite SQL Server Example

December 24th, 2014 | Posted by Robert Curlette in OrmLite | ServiceStack - (0 Comments)

ORMLite is a great example of a framework that does one thing and does it well. If we’re looking for a efficient and solid way to get and put data in a DB within .Net (or Mono) then the ServiceStack ORMLite micro-orm is a great choice. It was created by Demis Bellot. One of the great things about ServiceStack is the high level of support from Demis and you can find many of his answers on StackExchange. In this post I will explain how to quickly setup a connection to SQL Server and add / query 1 row. If you have used ORMLite before this article might not shed any new light into the ORMLite scenario for you. Note that the current version of OrmLite (v4) is paid software and uses a quota system for small projects and evaluations. The license allows a developer to use it for a DB of up to 10 tables for free.

Getting Started

1. Create a new .Net Console Application
2. Add a NuGet reference to OrmLite.SqlServer library

Prepare SQL Server

1. Create a new Database User (if needed) for your new DB.
2. Create a new Database (ORMLite does not do this for you)
3. Give the DB User permissions to the new DB
4. Create the connection string: “Server=Dev2011;Database=ItemInfoDb;User Id=MyNewDbUser;Password=S3cr3tPw;”

Write the code

The below code creates an instance of a POCO, and then saves it to the DB. Note the AutoIncrement data attribute. This creates our PK.

For more in-depth information I highly recommend the official ServiceStack documentation. and ORMLite example here.