Skip to main content

Why Should You Use the /uploadpdb Option with TcmUploadAssembly.exe ?

A Bit of Background

TcmUploadAssembly.exe is a utility program that allows you to upload a DLL into the SDL Tridion Content Manager. It does the following:
  • Create a TBB (of type .NET Assembly) that holds the actual .NET DLL;
  • Create a TBB (of type C# Code Fragment) for each class in the .NET DLL that implements the ITemplate interface;
  • Optionally, creates Parameter Schemas and associates them with the individual template TBBs;
  • Optionally, uploads the PDB corresponding to the .NET DLL;
The following command line arguments are accepted:

Usage: TcmUploadAssembly [options] [ConfigurationFilePath] [AssemblyPath]
  ConfigurationFilePath    The location where the configuration file for this
                           tool can be found.
  AssemblyPath             The location of the assembly to be uploaded.

Basic Options:
  /verbose                 Output extra debug information.
  /help                    Print this message.
Overriding Options (overriding either assembly or configuration file values):
  /folder:tcmuri           Override the folder to store the assembly
                           specified in the assembly.
  /targeturl:cmsurl        Override the target url of the CMS
                           specified in the configuration file.
  /username:nameofuser     Override the username to use in authentication
                           with the web service.
  /password:clearpassword  Override the password to use in authentication
                           with the web service.
  /uploadpdb:true|false    Override whether the PDB should be uploaded from
                           together with the assembly.
  /timeout:in seconds      Override the time it needs to upload the assembly
                           to the web service.


Why the PDB?

To put it simply, without the PDB, you won't be able to debug your code. A PDB file contains information about the source file names with line numbers and the local variable names. So, without a PDB, you won't know in which file the particular class is and at which line your execution pointer is. You will only know the name of the class and method you are in. That is not enough information a debugger can go by.

You can find a techie, yet excellent article here PDB Files: What Every Developer Must Know.

Without a PDB, a stack trace would look something like this (I'm attempting a division by zero in my code to yield an exception):

Attempted to divide by zero.
   at CwaReferenceImplementation.Templates.Generic.FormatDate.Transform(Engine engine, Package package)

While with the PDB present, the exact same code shows the following stack trace:

Attempted to divide by zero.
   at CwaReferenceImplementation.Templates.Generic.FormatDate.Transform(Engine engine, Package package) in C:\Reference Implementations\CWA Reference Implementation\Tridion Templates\Reference Implementation Templates\Generic\FormatDate.cs:line 25

TcmUploadAssembly will upload the PDB either to C:\temp or to %TRIDION_CM_HOME%\temp.

Comments

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

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

I Have Gone Dark

Maybe it's the Holidays, but my mood has gone pretty dark. That is, regarding the look and feel of my computer and Tridion CME, of course. What I did was to dim the lights on the operating system, so I installed Placebo themes for Windows 7 . I went for the Ashtray look -- great name :) My VM looks now like this: But, once you change the theme on Windows, you should 'match' the theme of your applications. Some skin easily, some not. The Office suite has an in-built scheme, which can be set to Black , but it doesn't actually dim the ribbon tool bars -- it looks quite weird. Yahoo Messenger is skinnable, but you can't change the big white panels where you actually 'chat'. Skype is not skinnable at all. For Chrome, there are plenty of grey themes. Now i'm using Pro Grey . But then I got into changing the theme of websites. While very few offer skinnable interfaces (as GMail does), I had to find a way to darken the websites... Enter Stylish -- a pl