Re: [NAntC-Dev] Question about the <vb6> task

[Bevan A. <Bev...@rb...>]

Since you know the DLL, and presumably, it's location, why not use a
<fail> task before <vb6>?

 

Something like this:

 

<property name="critical.dll" value="..."/>

 

<fail message="Critical dll not found"
unless="${file::exists(critical.dll)}"/>

<vb6 ...>

 

Hope this helps,

Bevan.

 

 

From: nan...@li...
[mailto:nan...@li...] On Behalf
Of Robert Gelb
Sent: Wednesday, 10 September 2008 3:51 a.m.
To: nan...@li...
Subject: [NAntC-Dev] Question about the <vb6> task

 

Hello, not sure if this is the right forum to bitch, but couldn't really
find a forum on the nantcontrib site.

Anyway, using the <vb6> task to compile an ActiveX DLL project.  The
project has binary compatibility set to a DLL.  And the <vb6> task works
fine and compiles it fine.  However, I'd like the compilation to fail,
if the compatibility DLL is not there.  Currently, it just compiles the
project and assigns the resulting DLL a whole set of new GUIDs (which is
a problem for me).

So how do I make the task fail if the binary compatibility DLL is
missing?

Thanks.

 



******************************************************************************
"This message (and any files transmitted with it) are confidential and
may be legally privileged. If you are not the intended recipient please
notify the sender immediately and delete this message from your system.

This message does not necessarily reflect the views of the
Reserve Bank of New Zealand. If the recipient has any concerns about
the content of this message they should seek alternative confirmation
from the Reserve Bank of New Zealand."
******************************************************************************