I can happily confirm that this version is working great:
It is both debuggable, and compatible with existing assemblies that
reference it.
Ron - thank you very very much!

Omer.

On Mon, Nov 9, 2009 at 1:09 AM, Ron Grabowski <[email protected]>wrote:

> I've contacted Omer off list to have him verify the .pdb file. If its
> correct I'll publish it somewhere.
>
> ------------------------------
> *From:* Omer Mor <[email protected]>
> *To:* Log4NET Dev <[email protected]>
> *Sent:* Mon, October 19, 2009 1:09:24 AM
>
> *Subject:* Re: Debugging log4net source
>
> Thanks!
>
> On Mon, Oct 19, 2009 at 5:04 AM, Ron Grabowski <[email protected]>wrote:
>
>> I emailed Nicko asking him what I need to do to get the .snk file onto my
>> system. It looks like the version in source control is encrypted.
>>
>> ------------------------------
>> *From:* Omer Mor <[email protected]>
>> *To:* Log4NET Dev <[email protected]>
>> *Sent:* Wed, October 7, 2009 9:01:18 AM
>>
>> *Subject:* Re: Debugging log4net source
>>
>> I'm trying again to get some help from the log4net developers community:
>> I really need to get a release build with pdb.
>> I explained blow exactly what needs to be changed in the nant script to
>> build it this way.
>> It should only take a couple of minutes to do this.
>> I would have done it myself if the assembly signing key would have been
>> public.
>> Maybe if no one is free to compile it, then I could join the log4net dev
>> team, and get permission to access the signing key?
>>
>> Thanks in advance,
>>   Omer Mor.
>>
>> On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <[email protected]> wrote:
>>
>>> Thanks.
>>> First - you should change the nant script:
>>> In the file <root>\log4net.include line 171 should be changed from:
>>>         <property name="build.debug" value="false" />
>>> to:
>>>         <property name="build.debug" value="pdbonly" />
>>> then just run the build script (build.cmd) and the release folder (
>>> <root>\bin\net\2.0\release\) should contain both the dll and pdb files.
>>>
>>> I suggest making the change in the nant script permanent as it does not
>>> affect performance and allows for debugging into log4net source.
>>>
>>> Thanks in advance,
>>>   Omer Mor.
>>>
>>> On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski 
>>> <[email protected]>wrote:
>>>
>>>> Tell me the exact nant command line to run and I'll run it.
>>>>
>>>> ------------------------------
>>>> *From:* Omer Mor <[email protected]>
>>>> *To:* Log4NET Dev <[email protected]>
>>>> *Sent:* Sunday, August 23, 2009 11:49:03 AM
>>>> *Subject:* Re: Debugging log4net source
>>>>
>>>> I would like to ask again the developer community of log4net for a
>>>> signed build of 1.2.10 assembly that was compiled with a PDB file.
>>>> This is the best way for us to enable live debugging of the log4net
>>>> source.
>>>> I believe it would only take a couple of minutes to compile it this way,
>>>> and it would help us tremendously.
>>>>
>>>> Thanks again,
>>>>   Omer Mor ([email protected])
>>>>
>>>> On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <[email protected]> wrote:
>>>>
>>>>> I prefer debugging the situation live.
>>>>> Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a
>>>>> slight tweak in the project settings.
>>>>>
>>>>>
>>>>> On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> Have you tried specifying a custom error handler on the appender to
>>>>>> track down when it enters a failed state?
>>>>>>
>>>>>> <appender name=".." >
>>>>>>   ...
>>>>>>   <errorHandler type="Your.ErrorHandler, YourAssembly" />
>>>>>> </appender>
>>>>>>
>>>>>> You would write one that sends an email when the file can't be
>>>>>> created.
>>>>>>
>>>>>> ------------------------------
>>>>>> *From:* Omer Mor <[email protected]>
>>>>>> *To:* [email protected]
>>>>>> *Sent:* Thursday, August 6, 2009 3:02:17 AM
>>>>>> *Subject:* Debugging log4net source
>>>>>>
>>>>>> Hi,
>>>>>> to research a (rare) bug we have with log4net (log file is not being
>>>>>> created) we wanted to debug its source.
>>>>>> However, the release build of 1.2.10 is supplied without a pdb file.
>>>>>> And since it is a signed assembly we can't compile it ourself and
>>>>>> replace it.
>>>>>> Also - the debug build of 1.2.10 is supplied with a pdb, but is not
>>>>>> signed, so it is not substitutable.
>>>>>> What I'd like to ask is that one of the developers compile a release
>>>>>> build of 1.2.10 and enable pdb creation, so that we could debug the 
>>>>>> source.
>>>>>>
>>>>>> Using a non-signed copy of log4net is not an option for us, because
>>>>>> some of our 3rd-party assemblies are compiled against the signed 1.2.10
>>>>>> log4net assembly.
>>>>>>
>>>>>> The files could be sent irectly to me at [email protected] .
>>>>>>
>>>>>> Thanks in advance,
>>>>>>   Omer Mor.
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to