David Thielen wrote:
Hi;
For my compile task I do a and then an to sign (authenticode)
the code. How can I set it to not sign it unless it is recompiled?
you could do somthing like:
...
unfortunately you have to do the convert:to-datetime as properties are
stored as strings once set.
Ia
Hi;
For my compile task I do a and then an
to sign (authenticode) the code. How can I set it to not sign it
unless it is recompiled?
Thanks - dave
Hi;
I added
To Nant.exe.config.
I have nunit 2.2 (actually 2.1.91 acording to gacutil)
installed and in the GAC.
I set my task as:
Title: Project reference problem with solution task
I just downloaded the 8/17 nightly build of NAnt 0.85 and have an issue with project references that does not seem to match Visual Studio .NET's behavior.
Project A contains a project reference to Project B
Project B contains a project ref
As usual -- patches welcome. The ant-contrib ( not NAnt-contrib ) has a
ccTask that would be a good candidate for porting:
http://ant-contrib.sourceforge.net/cc.html
of course there is nothing stopping you from using to call out to
makefiles for the c/c++ parts and having a 'mixed' build for no
Madham,
If you can isolate the offending project, please send it to me ...
Gert
- Original Message -
From: "Madhan Retnaswamy" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "NAnt Users Mailing List"
<[EMAIL PROTECTED]>
Sent: Wednesday, August 18, 2004
Gert,
Thank you so much! i got the latest nightly build and my issue is
fixed now. Build can now reference the assembly folders for dlls. But
iam getting stuck with another error. This is the error..
[solution] vbc : Command line error BC2001 : file
'C:\Development\VisualStudioNet\Projects\s
Hi Kevin,
Can you please send code to reproduce the error. For example, the two
component elements that link to these files and then your directories
element.
Thanks
Jim
> Ran into another error with
>
> Unable to build MSI database 'ApplicationServerSetup.msi'.
>Item
Loren,
This should actually have been fixed in the latest nightly build.
Can you please provide a small repro for this issue ?
Thanks,
Gert
- Original Message -
From: "Loren Halvorson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 18, 2004 9:22 PM
Subject: [Nant-users
I just downloaded the 8/17 nightly build of NAnt 0.85 and am seeing an issue
with project references that does not seem to match Visual Studio .NET's
behavior.
Project A contains a project reference to Project B
Project B contains a project reference to Project C
I believe Project A's references
I removed the directory that had sub directories until I get a suggestion to resolve
that. Now I am getting the following error:
D:\Projects\Visa\MR0804A\Application Server
Code\ApplicationServerSetup\default.build(6,10):
Unable to build MSI database 'ApplicationServerSet
Title: Feature request: building complex cross-platfrom-cross-technology projects
Hello!
Currently I am working on packaging new math library written in C#/C++ (unmanaged) into user friendly binary and source distros. My plan is to base it on NAnt with source part. Unfortunately, when I hav
Ran into another error with
Unable to build MSI database 'ApplicationServerSetup.msi'.
Item has already been added. Key in dictionary:
"TARGETDIR|incHomeContent.htm" Key being added: "TARGETDIR|incHomeContent.htm"
There are not two files but there are two different
Paco,
We don't need to be able to determine the version number of the mono version
that is in the path, we need to be able to determine which versions of Mono
are installed.
Did you have a look at the bug report I submitted
(http://bugzilla.ximian.com/show_bug.cgi?id=63278) ?
I'll talk to you
I am trying to use the task but one part of that task is giving me
an error.
The error message shows:
Validation Error: The required attribute 'file' is missing. An error
occurred at , (19, 8).
I see no mention of a 'file' attribute for
Kevin Burton
[EMA
Title: RE: [Nant-users] references to interop dll's
Well, I humble myself and give all credit to a person named Ryan Cromwell. You probably recognize the name. I just modified the script that he sent me to suit my needs. In fact, I also use the same thing for aximp.
I am not using the solut
When I run the MSI
task it finds some keyfiles and complains that other are missing. I am using the
latest nightly build. Anyone know of an open issue with
this?
Dan Pupek
Software
Engineer
Advanced Systems
Technology, Inc
[EMAIL PROTECTED]
(850)
475-4038
BEGIN:VCARD
VERSION:2.1
N
Hola:
I was the one who wrote the installers for the Combined Mono Installer
that is available at Novell Forge and that later was adopted by Novell
at mono-project.com/downloads. During my design I intended to make the
presence of Mono perceivable from the Windows Registry as well as
through o
Bonnett, Evan A wrote:
So, what is the "preferred" practice to do this? Is it to create the
wrappers and store the wrapped component in source control to be pulled at
build-time? Or is it to wrap at build-time?
the nay-sayers will say that you should *never* put the outputs of a
tool in source
Merrill Cornish wrote:
Thanks. However, NAnt needs a bit more graceful "type mismatch" syntax
message than triggering a stack tract starting in the temporary
directory of Gert's workstation. :-)
That's a valid comment :-)
Gert Driesen wrote:
> Implicit conversion has not yet been removed from NA
Title: RE: [Nant-users] references to interop dll's
So, what is the "preferred" practice to do this? Is it to create the wrappers and store the wrapped component in source control to be pulled at build-time? Or is it to wrap at build-time?
Hello!
Thanks for info on error source. After updating nant.exe.config manually to
new registry keys everything seems to work fine.
Checking the way NAnt is using for detecting presence of any framework or
sdk one can conclude that there is, in my opinion, a design bug which will
prevent NAnt fr
Hi everyone, I've knocked together a little build framework called NBuild
(what an exciting name) that compiles and executes C# build scripts.
Extending it to compile VB.NET build scripts should be easy if C# isn't your
cup of tea.
The format is similar to Gerry Shaw's comment
(http://www.iunknown
Gert Driesen wrote:
Ian,
I just found out that the new installer registers itself in a
different location (HKLM\Novell\Mono).
I've added some info to the bug report
(http://bugzilla.ximian.com/show_bug.cgi?id=63278). Can you have a
look at it, and perhaps correct me if necessary (or make a bett
- Original Message -
From: "Jacek Blaszczynski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 2004 7:22 PM
Subject: [Nant-users] Detecting Mono or "Mono-SDK" on Win
Hello!
Trying to use framework::sdk-exists for Mono-1.0 I have noticed that it is
not detected by N
Dave,
NAnt currently doesn't include the VS.NET documenter. In normal
circumstances, you would just be able to copy the documenter assembly from
the corresponding NDoc release to the NAnt bin directory. However, we
curerntly use a post-beta1 version of NDoc, so there's no matching NDoc
distribu
Ian,
I just found out that the new installer registers itself in a different
location (HKLM\Novell\Mono).
I've added some info to the bug report
(http://bugzilla.ximian.com/show_bug.cgi?id=63278). Can you have a look at
it, and perhaps correct me if necessary (or make a better proposal) ...
Ge
Madhan,
If you downloaded a nightly build, then you don't have to build NAnt as it
includes a fully functional version of NAnt.
Gert
- Original Message -
From: "Madhan Retnaswamy" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "NAnt Users Mailing List
Hi Steve,
Can you try using a more recent nightly build as a file locking issue was
fixed recently ?
Please let us know if that fixed your problem.
Thanks
Gert
- Original Message -
From: "Steve Burkett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Michael Gerfen" <[EMAIL PROTECTED]>
29 matches
Mail list logo
