You'll need to download the InstallShield StandAlone builder. You also
need to copy the merge modules to the build machine. Then you can set up
an task like the following.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary
Feldman
Sent: Wedne
Our master build file does the first part. However, it doesn't care
about dependencies. Any dependencies we have we address through the
solutions (i.e. if one project depends on another, they are both in the
same solution so that the solution can track the dependencies).
Try deleting your obj folder as well as your bin folder when you do the
clean.
-Original Message-
Does anyone have any answers? Is there some undocumented
parameter I can use to force rebuilding?
***
Note: The information
x27;m guessing that VS.NET didn't have a problem with it because it uses
the project names to track dependencies while NAnt uses the project
GUIDs.
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, February 13, 2006 11:44 AM
To: Craig Wagner;
I'm getting this
message when using the task.
I've stripped my
.build file to the following:
http://nant.sf.net/release/0.85-rc3/nant.xsd">
solutionfile="FileListenerService.sln"
includevsfolders="false"
configuration="Release"
Lopez Mena
[mailto:[EMAIL PROTECTED] Sent: Tuesday, April 19, 2005
9:18 AMTo: Craig Wagner;
nant-users@lists.sourceforge.netSubject: RE: [Nant-users] Get VSS
Labelled version
Hello everyone,
It looks like the VSS has a bug, because I can see the
folder creation but for some reason there is
Title: RE: [Nant-users] Get VSS Labelled version
localpath="..\..\..\..\libraries\dotNET\Microsoft\EnterpriseLibrary\bin"
replace="true"
removedeleted="true"
dbpath="${vssPath}"
version="${build.label}"
path="$/Appli
he /r line makes me curious though. The other weird thing is that
it is copying the Aspose.Excel.xml file from the install location to my bin
folder.
As I said, I've got a workaround by adding the
includevsfolders="false" to the task, but it is
odd.
From: Gert Driesen
[
rogram
Files\Aspose\Aspose.Excel\Bin.
I believe I've solved
the problem by adding the includevsfolders attribute.
I'd still like to
know why I was getting different behavior from VS.NET vs
nant.
--
Craig Wagner
I've run into it.
From what I've been able to figure out, NAnt looks in
the registry to find the location of the SDK. But apparently the keys in the
registry are different depending on whether the SDK was installed as part of a
VS.NET installation or standalone.
Look in your nant.exe.conf
Below is the [trimmed] output from a nant run. I understand what the
error is telling me and how to fix it, but I'm confused about how we get
to that point.
It appears to successfully build the Nwea.Core and Nwea.Pdf projects out
of the solution but then dies when trying to build Nwea.Data. What
out how to fix it).
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 9:50 AM
To: Craig Wagner; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Framework not available or not configured
Craig,
In order to compile resource files or import
If it's the same problem I ran into it is a bug in VSS not nantcontrib.
There is a hotfix available for it from Microsoft.
http://support.microsoft.com/default.aspx?scid=kb;en-us;837417
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy
Heyworth
Sent:
I wasn't paying attention and
originally sent this to Gert instead of the list.
Apologies.
I'm interested in your PS comment. I thought that the NAntContrib assemblies were all
private so I just copied them to the nant\bin folder. Should I have installed
them in the GAC or is there an ent
I'm not sure I understand why you can't keep them in a solution. Maybe
I'm just tired today, but I don't see a circular reference problem with
the project dependencies that you have described.
You might want to just lock down your version numbers so developers have
to change them rather than chang
I'm building a couple of web projects as well. What I found was that if
you use the tag you don't need to create the IIS virtual
directory at all. My build will work on any machine just by pulling the
.build file out of VSS and running nant against it.
Here's my .build file.
the heck am I doing wrong?
---
Craig Wagner
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Jav
[EMAIL PROTECTED](Void* , UInt32 , Void* )
BUILD SUCCEEDED
Total time: 0.7 seconds.
---
Craig Wagner
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relationa
18 matches
Mail list logo
