Of
[EMAIL PROTECTED]
Sent: Tuesday, March 30, 2004 4:08 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: AW: [Nant-users] Solution Task and Strong Names
Yup, you're right. I've just tries it in C# and it's a no go. VB seems to
cope OK with referencing the .snk f
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: AW: [Nant-users] Solution Task and Strong Names
>-Original Message-
>From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
>Sent: Tuesday, March 30, 2004 07:19 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, March 30, 2004 07:19 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: RE: AW: [Nant-users] Solution Task and Strong Names
>
>"... Are you sure this works from Vi
file when I compile the application.
Cheers,
Bill
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: 29 March 2004 21:50
To: Bill Martin; [EMAIL PROTECTED]
Subject: Re: AW: [Nant-users] Solution Task and Strong Names
> - Original Message -
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, March 29, 2004 9:31 AM
> Subject: RE: AW: [Nant-users] Solution Task and Strong Names
>
> I'm slightly confused (it doesn't take much!). Which task
pgrade to 0.85?
Thanks,
Bill
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: 28 March 2004 09:08
To: Ian MacLean; Eric Fetzer
Cc: Florian Benischke; Nant Users
Subject: Re: AW: [Nant-users] Solution Task and Strong Names
I looked into this, and appare
OTECTED]>
Sent: Monday, March 29, 2004 4:16 AM
Subject: RE: AW: [Nant-users] Solution Task and Strong Names
> Hi all,
>
> Firstly, quick thanks to the team for a great tool and responsive mailing
> list! Our entire dev + build process is slowly being built around nant (+
> n
;
<[EMAIL PROTECTED]>
Cc: "Florian Benischke" <[EMAIL PROTECTED]>; "Nant Users"
<[EMAIL PROTECTED]>
Sent: Sunday, March 28, 2004 10:07 AM
Subject: Re: AW: [Nant-users] Solution Task and Strong Names
> I looked into this, and apparently VS.NET runs csc with dire
IL PROTECTED]>; "Nant Users"
<[EMAIL PROTECTED]>
Sent: Sunday, March 28, 2004 10:07 AM
Subject: Re: AW: [Nant-users] Solution Task and Strong Names
> I looked into this, and apparently VS.NET runs csc with directory>\obj\ as working directory or output directory
(the
> co
ymbols) to the actual output
directory ?
Gert
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Eric Fetzer" <[EMAIL PROTECTED]>
Cc: "Florian Benischke" <[EMAIL PROTECTED]>; "Nant Users"
<[EMAIL PROTECTED]>
Sen
Hmm,
It looks like csc.exe is run with the project folder as the working
directory when to be consistent with vs.net it should be the
output/object folder.
ie line 423 of Project.cs
psi.WorkingDirectory = _projectDirectory;
should be setting WorkingDirectory to the directory of the output path.
OK, I changed the path for release mode and get a bit
past this. Then It's crashing trying to run the post
event macro. The output is:
[solution] Building myProject.Library [release]...
[solution] Pre/post event macro $(DevEnvDir) not
implemented.
[solution] PostBuildEvent failed with exit code
Florian,
If I did that, it wouldn't compile for the developers
here (who use Visual Studio), only the daily build.
The key file exists in the same place as the csproj
file. Visual Studio is referencing the snk file from
the Object folder. Any other suggestions out there?
Thanks,
Eric
--- Flo
Hi Eric,
looks like nant just can't find your key file. I'm using assembly signing
too and I'm not having any problems.
You can try setting the key file reference to a "strong" path, like
D:\mykeyfile.snk (well you also have to copy the file there ;) ), to see
that key file signing is possible.
14 matches
Mail list logo
