Skip to main content

A DD4T.net Implementation - The Model Generator Tool

The post presents a tool that automatically generates DD4T .net strongly typed models from Tridion Schemas.

In the previous posts Strong Typed Models and Umbrella Models, I presented a flavour of strongly type models to be used with DD4T .NET. The tedious part with these models, is that one needs to write them manually one by one, while carefully checking the type of each field in the Schema, the single vs multi-value property, the Allowed Schemas, etc.

This is an ideal candidate for automation and code generation and that's exactly what this Model Generator is doing:
  • Connect to a Tridion CM instance using Core Service and download all Schemas of type Component, Multimedia and Embedded
  • Build an internal model for each Schema, each field in it, retaining all return types, field name, allowed Schemas, multi- and single-value
  • Generate individual C# classes for each Schema model, generating the using statements, class, properties for each Schema field, constructor

The Model Generator is in fact a simple Console application, making use of Core Service client and creating .cs files in a predefined location.

The application .config file must define the following settings:

<add key="TridionCmeUrl" value="http://my.tridion.com"/>  - defines the Tridion CME URL to connect to using Core Service
<add key="Username" value="mihai.cadariu"/>  - the username to use when connecting
<add key="Password" value="password"/>  - the password to use when connecting
<add key="StartTcmUri" value="tcm:0-13-1"/>  - the Publication or Folder to search Schemas under
<add key="Namespace" value="Mitza.DD4T.Model"/>  - the namespace to use when generating models
<add key="Folder" value="C:\Mitza.DD4T.Model"/>  - the folder on local file system where .cs files are generated

The entire Model Generator solution, including sources, dlls and executable are available on this blog's GitHub page, project Model Generator.



Comments

Anonymous said…
Nice post Mihai. Did you look at using T4 templates to do the generation?
Mihai Cădariu said…
I will now :)
So far I'm only writing strings to a file. Quick and it gets the job done.

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven