Asp.net release build vs debug build

笑着哭i 提交于 2019-11-27 05:32:53

If you want to know if the dll was built in Debug mode, with the debug attributes, then your best bet is reflection.

Taken from "How to tell if an existing assembly is debug or release":

Assembly assembly = Assembly.GetAssembly(GetType());
bool debug = false;
foreach (var attribute in assembly.GetCustomAttributes(false)){
  if (attribute.GetType() ==  typeof(System.Diagnostics.DebuggableAttribute)){
    if (((System.Diagnostics.DebuggableAttribute)attribute)
        .IsJITTrackingEnabled){
      debug = true;
      break;
    }
  }
}

This will get the assembly that is calling that code (in effect itself), and then set the debug boolean to true if the assembly was compiled in debug mode, otherwise it's false.

This could easily be dropped into a console app (as in the linked example), and then you pass in the path of the dll/exe you want to check. You would load the assembly from a path like this:

Assembly assembly = 
    Assembly.LoadFile(System.IO.Path.GetFullPath(m_DllPath.Text));

For one in Web.config debug will be set to true, however you can actually set this in a release application too.

In debug however defines like DEBUG are set, so it's simple to do:

bool is_debug;

#ifdef DEBUG
is_debug = true;
#else
is_debug = false;
#endif
Dave Black

You need to look for more than IsJITTrackingEnabled - which is completely independent of whether or not the code is compiled for optimization and JIT Optimization.

Also, the DebuggableAttribute is present if you compile in Release mode and choose DebugOutput to anything other than "none".

Please refer to my posts: How to Tell if an Assembly is Debug or Release and How to identify if the DLL is Debug or Release build (in .NET)

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!