Madhan,
Compiling licx files has always been a major PITA. I'm afraid this won't be
easy to fix.
Would it be possible to create a repro for this ?
Gert
- Original Message -
From: "Madhan Retnaswamy" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent:
Gert,
I still couldnt get rid of this Active Reports license error. The error says...
"error LC0003 : Unabled to resolve type
'DataDynamics.ActiveReports.ActiveReport,
ActiveReports'"
I removed the license tag from my build script and allowed it to the
solution task to figure out the license fil
Steve,
Mono has some issues with AppDomain unloading, and I think that this is the
issue what you're running into here.
Can you try this http://nant.sourceforge.net/faq.html#building-mono-1, to
see if that "fixes" your problem ?
I advise you to report the issue to the Mono team anyway ...
Gert
Madhan,
You should add a refererence for the ActiveReports assembly to the
task :
or you could leave it up to the task to handle this.
Gert
- Original Message -
From: "Madhan Retnaswamy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday,
Gert,
Thanks very very much
SP3 did the magic and my vbc compiler error vanished...
Now there is a new error with lc.exe compiling the license.licx files
that comes with DataDynamics Active Reports. I am assuming that this
should be a simple fix in the build script. I have seen some people
al
>From: "John Debay" <[EMAIL PROTECTED]>
>Sent: Thursday, September 02, 2004 7:42 PM
> I want to create a NAnt build script that can easily handle either debug
or
> release builds, or both. In other words, from the command line, I want to
be
> able to do any of:
I strongly encourage you to look at
HI Folks,
I'm having problems getting the latest nighty to build under Mono 1.0.1
on my OS-X 10.3.5. I have included the output from 'make' at the bottom
of this email.
Mono is otherwise installed and working properly.
Any ideas?
Cheers,
Steve
--
Steve Webster
Interactive Developer
Featurec
John,
NAnt properties can be readonly (if you specifically set the readonly attribute) or
read-write (the default). If they are read-write, then you can set the same property
as many times has you want, much like any programming variable.
The thing that catches a lot of people is that command
This worked. I had read on the web somewhere that you couldn't set a
property twice in the same build file -- that the properties were set before
the build ran, so if you did this:
The value of debug would be either true or false (I'm not sure if the first
or second value wins), but not change
Thanks, Troy. Duh. It's even documented! It never even occurred to me to
RTFM because there is no other case that I know of where a property has
a non-global scope. While I like it, it seems contrary to the behavior
of properties everywhere else in nant. I wish properties had implicit
scope everywh
McCullough, Gary wrote:
Can anyone explain this to me? Is it a bug or a feature? This code:
It's in the documentation, so I'd go feature.
http://nant.sourceforge.net/help/tasks/foreach.html
"The property is returned to its normal value once it is used."
Bonus question:
Anyone know an easier way to
11 matches
Mail list logo
