Archive for June, 2008

System.Diagnostics + ASP.Net Web Site – remember to set compilerOptions=”/d:TRACE”

Tuesday, June 3rd, 2008

Today I was looking at Ukadc.Diagnostics, an extension to the System.Diagnostics namespace, and decided to build a test website myself to get more familiar with it. After reading through Ukadc.Diagnostics Reference Example I thought it would be a homerun in the first try, but it turns out that without adding compilerOptions="/d:TRACE" to each compiler in the compilers section in the Web.config, the tracing code is never compiled into the assemblies at runtime. Needless to say, I was scratching my head since my sample console application worked as expected the first time.

My compilers section ended up looking like this (it is located in the system.codedom section)

<compilers>
	<compiler language="c#;cs;csharp" extension=".cs" 
            compilerOptions="/d:TRACE"
            warningLevel="4"
            type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
		<providerOption name="CompilerVersion" value="v3.5"/>
		<providerOption name="WarnAsError" value="false"/>
	</compiler>
	<compiler language="vb;vbs;visualbasic;vbscript"
            compilerOptions="/d:Trace=true"
            extension=".vb"
            warningLevel="4" 
            type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
		<providerOption name="CompilerVersion" value="v3.5"/>
		<providerOption name="OptionInfer" value="true"/>
		<providerOption name="WarnAsError" value="false"/>
	</compiler>
</compilers>

Do note that this is not an issue with ASP.Net Web Applications, since they are precompiled. For more on the subject, MSDN has a great article which certainly saved me in this instance.

Tags: , ,
Posted in ASP.NET | No Comments »