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
