Stephen --- Please take no offense, but is there a one-page, completely self-contained (think black box here), summary of how to use the log4net "component"? I'd been thinking of using it in an IWLG project, but I could write and document at least three commercial products in the time it would take to read and assimilate these disconnected stream-of-consciousness dissertations that lack even drawings.
-----Original Message----- From: Nicko Cadell [mailto:[EMAIL PROTECTED] Sent: Sunday, March 06, 2005 5:25 PM To: Log4NET User Subject: RE: Having trouble signing log4net.dll The DEBUG builds produced by the NAnt build script are NOT strongly named, only the release builds are strongly named. If you add the STRONG define to Visual Studio .NET and then build a debug build, the output file will be strongly named, however it will go to a different output folder. For reasons lost in the mists of time the NAnt builds go to '\bin\net\1.1\debug' but the Visual Studio .NET builds go to '\build\bin\net\1.0\debug' so that it where you will find your strongly named output assembly. The file in '\src\obj\Debug' is an intermediate file produced by Visual Studio .NET and while it is technically the same as the output assembly it should not be referenced from that location as it will upset the Visual Studio .NET compiler. > So we've learned that NANT is evil. 8^) NAnt is not evil it is just misunderstood! Nicko > -----Original Message----- > From: Pardee, Roy [mailto:[EMAIL PROTECTED] > Sent: 05 March 2005 02:47 > To: Log4NET User > Subject: RE: Having trouble signing log4net.dll > > Interesting. When I said I 'rebuilt', I meant I re-ran > BUILD.cmd. I just now did a rebuild in vs.net & the assembly > that winds up here: > > C:\DeleteMe\log4net-1.2.0-beta8\src\obj\Debug > > *Is* strongly named. > > And when I reference that, I can build *my* app. > > So we've learned that NANT is evil. 8^) > > Seriously, I think I'm in shape now --thanks so much for the help! > > -Roy > > -----Original Message----- > From: M. d'Entremont [mailto:[EMAIL PROTECTED] > Sent: Friday, March 04, 2005 5:17 PM > To: Log4NET User > Subject: Re: Having trouble signing log4net.dll > > > The only difference seems to be that the *.snk file I was > using was from > Verisign. I'm under the impression that for development purposes that > that should not make a difference. > > Does your build window give you any info on what is > happening with that > file? > > Marc > > Pardee, Roy wrote: > That makes a ton of sense--but I'm either doing it wrong or it's not > working. I opened up > C:\DeleteMe\log4net-1.2.0-beta8\src\log4net.sln in > vs.net, allowed it to convert the project to 2003 format, > right-clicked > on the project & selected 'properties', and then 'configuration > properties'. I changed the Conditional Compilation Constants from > > DEBUG;TRACE;NET;NET_1_0;NUNIT_TESTS > > to > > DEBUG;TRACE;NET;NET_1_0;NUNIT_TESTS;STRONG > > and then rebuilt. But no difference--sn still says the dll isn't > strong-named. > > Thanks! > -----Original Message----- > From: M. d'Entremont [mailto:[EMAIL PROTECTED] > Sent: Friday, March 04, 2005 4:42 PM > To: Log4NET User > Subject: Re: Having trouble signing log4net.dll > > > When I had that problem I had to go into the project and set > the STRONG > environment variable so that it could execute the stuff in the #if > STRONG clause > > Marc > >
