1

Closed

include option to generate assembly without trace info

description

Hi,

First of all, thank you for great utilty!

Here's my issue: I use LibZ to compose a helper library I use with unit tests. When I run those tests, first of them includes the following text (example for NCrunch):

nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Resolving: 'Ploeh.AutoFixture, Version=3.16.1.0, Culture=neutral, PublicKeyToken=b24654c590009d4f'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Trying to load 'Ploeh.AutoFixture, Version=3.16.1.0, Culture=neutral, PublicKeyToken=b24654c590009d4f'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Found: 'Ploeh.AutoFixture, Version=3.16.1.0, Culture=neutral, PublicKeyToken=b24654c590009d4f'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Resolving: 'Castle.Core, Version=3.2.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Trying to load 'Castle.Core, Version=3.2.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Found: 'Castle.Core, Version=3.2.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Resolving: 'FluentAssertions, Version=2.1.0.0, Culture=neutral, PublicKeyToken=33f2691a05b67b6a'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Trying to load 'FluentAssertions, Version=2.1.0.0, Culture=neutral, PublicKeyToken=33f2691a05b67b6a'
nCrunch.TestHost.x86.exe Information: 0 : INFO (AsmZ/TddToolkit) Found: 'FluentAssertions, Version=2.1.0.0, Culture=neutral, PublicKeyToken=33f2691a05b67b6a'

which bloats the outcome. When I run dozens of tests, this does not matter too much, but when I run a single one (or toolks like NCrunch do it for me), this is visible and I have to scroll way down to see the outcome.

The workaround would be to disable the trace, but this would mean any member of my team would have to do it for one or both tools they use (resharper/ncrunch). Is there a possibility to instead have in the commandline utility that creates the combined assembly an option to disable the libz-specific trace in the generated assembly?
Closed Apr 23, 2014 at 8:16 PM by Krashan

comments

Krashan wrote Dec 20, 2013 at 8:30 AM

It definitely possible, although it's all about cost/benefit. I think modifying it to, for example, read 'HKLM\Software\LibZ\Trace' registry key and use trace or not accordingly would be the quickest to implement. Would it be acceptable?

galezowski wrote Dec 20, 2013 at 12:00 PM

Hi,

Thank you for answering my comment.

As long as it would mean I have to change the registry only on the machine I am generating the assembly on, it's enough for me :-). What I would not want to do is modify registry on each computer that actually uses the generated dll.

Krashan wrote Dec 20, 2013 at 12:47 PM

It means that you would need to change registry on machines you DO WANT to see trace from LibZ.

galezowski wrote Dec 20, 2013 at 1:51 PM

I see. Great idea! From my perspective, this is even better than what I originally proposed.

Krashan wrote Mar 9, 2014 at 12:04 PM

This issue has been addressed in 1.1.0.0