Sonufa! Now I get the same (well, different public key, but the .dll is indeed signed). I could swear it wasn't when last I looked... No doubt I just got confused somewhere along the way.
Sorry for the waste of bandwidth. Thanks! -Roy -----Original Message----- From: Nicko Cadell [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 9:09 AM To: Log4NET User Subject: RE: Having trouble signing log4net.dll This is what I get when verifying the strong name of the NAnt built release assembly: C:\work\cvs_root\apache\logging-log4net\bin\net\1.1\release>sn -v log4net.dll Microsoft (R) .NET Framework Strong Name Utility Version 1.1.4322.573 Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Assembly 'log4net.dll' is valid C:\work\cvs_root\apache\logging-log4net\bin\net\1.1\release>sn -Tp log4net.dll Microsoft (R) .NET Framework Strong Name Utility Version 1.1.4322.573 Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Public key is 0024000004800000940000000602000000240000525341310004000001000100c19260cb 986b47 b86fbde915bc1558d79aa7b4cd20e0b0b78d50a187fda9d62cf26354a90f53b7edc715e9 177a67 9870d90dd400b62e244c2a28047b60405ff68649921f0c619bd62c0893beeb42d5bf2727 235317 af401b3a7c9486a7f7e1bcf63ca2734577ea31a8dd4ed3bae7b75f0918b69c45d9d0b48e 8bb69d b1dd08d4 Public key token is 1b44e1d426115821 What output are you seeing? Nicko > -----Original Message----- > From: Pardee, Roy [mailto:[EMAIL PROTECTED] > Sent: 07 March 2005 16:58 > To: Log4NET User > Subject: RE: Having trouble signing log4net.dll > > Hmmm... Confusing--it looks to me like the > \bin\net\1.1\release version of the .dll is *not* signed. > > Is there a NAnt command for causing these assemblies to be named? > > Thanks! > > -Roy > > -----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 > > > > >
