Click here to Skip to main content
Click here to Skip to main content
Technical Blog

.NET - Determine Whether an Assembly was compiled in Debug Mode

, 14 Apr 2010 CPOL
Rate this:
Please Sign up or sign in to vote.
Finding out whether an assembly was compiled in Debug or Release mode is a task we must do from time to time...

Finding out whether an assembly was compiled in Debug or Release mode is a task we must do from time to time.

I know two ways to accomplish this:

Either attributes are applied to Assemblies and can be found in the Assembly Manifest but there are major differences between them:

  • AssemblyConfigurationAttribute must be added by the programmer but is human readable.
  • DebuggableAttribute is added automatically and is always present but is not human readable

You can easily get the Assembly Manifest by using the amazing ILDASM from your Visual Studio Studio Command Prompt:

ildasm_1

ildasm_2

And if you double click the MANIFEST item, you will get all manifest data.

Looking carefully, you will find the DebuggableAttribute:

ildasm_3

And perhaps the AssemblyConfigurationAttribute:

ildasm_4 

AssemblyConfigurationAttribute

Locate the AssemblyConfigurationAttribute – this attribute can be easily interpreted: its value can either be Debug or Release.

ildasm_5

DebuggableAttribute

If AssemblyConfigurationAttribute is not present, then we must use the DebuggableAttribute to achieve our goal.

Since we cannot understand the DebuggableAttribute value, we have to open the assembly from another tool and read this attribute content. There’s no such tool available out-of-the-box but we can easily create a Command Line tool and use a method similar to:

private bool IsAssemblyDebugBuild(string filepath)
{    
    return IsAssemblyDebugBuild(Assembly.LoadFile(Path.GetFullPath(filepath)));
}
private bool IsAssemblyDebugBuild(Assembly assembly)
{    
    foreach (var attribute in assembly.GetCustomAttributes(false))    
    {        
        var debuggableAttribute = attribute as DebuggableAttribute;        
        if (debuggableAttribute != null)        
        {            
            return debuggableAttribute.IsJITTrackingEnabled;        
        }    
    }    
    return false;
}

or (if you prefer LINQ):

private bool IsAssemblyDebugBuild(Assembly assembly)
{    
    return assembly.GetCustomAttributes(false).Any(x => 
	(x as DebuggableAttribute) != null ? 
	(x as DebuggableAttribute).IsJITTrackingEnabled : false);
}

As you can see … it’s pretty simple.

Note

Typically, I add a pre-build task to my build server so that the AssemblyConfigurationAttribute is added to the CommonAssemblyInfo file with the appropriated value: either “Debug” or “Release”. This way anyone can easily see, using only the ILDASM, which kind of compilation was used to generate my assemblies.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Nuno M. F. Gomes
Software Developer (Senior)
Portugal Portugal
Nuno Gomes currently works as a Senior Developer for one of the major portuguese banks.
 
Gomes graduated from Instituto Superior Tecnico with a Electronics and Computers degree in 1999.
 
His daily work main focus is, since 2003, on ASP.NET. A true .NET developer with great passion for the simple solution.

Comments and Discussions

 
QuestionReflector shows Debuggable attributes PinmemberMichael Freidgeim16-Oct-11 15:20 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.141220.1 | Last Updated 14 Apr 2010
Article Copyright 2010 by Nuno M. F. Gomes
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid