Skip to main content

Read Tridion Install Path from Registry Key

Image
By
Tridion install path is stored in Windows Registry on the machine where Tridion CM is installed. It might be useful sometimes to read this value programmatically -- e.g. when you need to read some configuration files placed in the Tridion_Home\config folder.

A little issue might occur when you try to read a Registry key in a Windows 32bit vs 64bit, because these values are stored in different Registry locations.

My fellow colleague, Principal Developer Frank van Puffelen (or @puf, for friends :) ), shows a neat way of reading a Registry key irrespective of the code running on a Windows 32 or 64 bit machine:

// Opens a registry either from its normal location or from the Wow6432Node and either from HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE.
private static RegistryKey FindKeyInRegistry(string registryKey)
{
    RegistryKey key = Registry.CurrentUser.OpenSubKey(registryKey);
    if (key == null)
    {
        key = Registry.CurrentUser.OpenSubKey(
            registryKey.Replace(@"Software\", @"Software\Wow6432Node\"));
        if (key == null)
        {
            key = Registry.LocalMachine.OpenSubKey(registryKey);
            if (key == null)
            {
                key = Registry.LocalMachine.OpenSubKey(
                    registryKey.Replace(@"Software\", @"Software\Wow6432Node\"));
            }
        }
    }

    return key;
}

Therefore, to read the Tridion_Home directory, you can use the method below:

/// <summary>
/// Gets the Tridion Install Path
/// </summary>
/// <returns></returns>
private String GetTridionInstallPath()
{
    String output = String.Empty;

    try
    {
        RegistryKey RegKey = FindKeyInRegistry(@"Software\Tridion");
        output = RegKey.GetValue("InstallDir").ToString();
    }
    catch (Exception ex)
    {
        throw new Exception("Could not get install path!", ex);
    }

    return output;
}

Labels:

Comments

Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
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...
2 comments
Read more

REL Standard Tag Library

By
The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...
2 comments
Read more

Publish Binaries to Mapped Structure Groups

By Unknown
Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...
10 comments
Read more