I sent this to the list a couple days ago, but my organization's email
filter blocked it because it had the word "error" in the subject.

-----Original Message-----
From: Dennison, Oran 
Sent: Tuesday, September 07, 2004 7:29 PM
To: '[EMAIL PROTECTED]'
Subject: Re: [Nant-users] Error with license.licx which comes with
Active Reports.

I encountered the same licenses.licx error Madhan Retnaswamy has been
experiencing, and just fixed it today (at least, it works on my box!).
We had been using a trial version of ActiveReports, and our
CruiseControl.NET build server had been handling it just fine with our
NAnt solution task (which uses the license task under the hood).  The
.licenses file was being created and properly embedded in the main
executable.  But when we installed the licensed version, the build
started breaking with error LC0003 : Unable to resolve type
'DataDynamics.ActiveReports.ActiveReport, ActiveReports'.

It turns out the solution was to update our licenses.licx file to
contain version, culture, and the public key token.

So instead of the original license file that looked like this:

DataDynamics.ActiveReports.ActiveReport, ActiveReports

It now looks like this:

DataDynamics.ActiveReports.ActiveReport, ActiveReports,
Version=3.3.0.1999, Culture=neutral,
PublicKeyToken=PublicKeyTokenGoesHere

I copied the previous text straight out of the intermediate .licenses
file created by Visual Studio in my obj folder.  Alternatively, you
could open up the executable file created by Visual Studio in Reflector,
navigate to the embedded resources, view the .licenses embedded
resource, and get the same thing.  You'll need to do this to get the
actual value for PublicKeyToken.  I'm pretty sure that's just
ActiveReports.dll's strong-name public key, but I don't want to risk
accidentally giving out my particular license key...

A few more notes on our particular configuration: we originally had
ActiveReports.dll nested several folders deep in the project folder and
used a relative path reference to it from the project's references.
Before trying the above solution, we moved ActiveReports.dll to the root
project folder, which is where the licenses.licx file lives.  As far as
I can tell, the relative HintPath should have been working properly, but
I wanted to ensure that wasn't a factor in the inability to resolve the
type.

Another possible solution I was going to try but didn't get around to is
to make a copy of the intermediate .licenses file from my box and
manually embed it from the NAnt script, but that would mean replacing my
solution task with a nitty-gritty csc-based task, not something I want
to do if I can avoid it.

Oran


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to