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.
I am getting the following error trying to build a new
project with the solution task:
[compile] error CS1548: Cryptographic failure while
signing assembly 'd:\myproject\myDll.dll' -- 'Error
reading key file '..\..\myproject.myDll.snk' -- The
system cannot find the file specified. '
Does solution
Yes, that's a lot better - the build still fails but that my problem
now.
Thanks
---
Peter G Jones
University of Canterbury, NZ
---
Senior Analyst/Programmer
Microsoft .Net MVP
Blog: http://jonsie.net
> -Original Message-
> Fr
I’d like to ask this user group for advice on how they
layout their directory structures when working with complex solutions.
For instance, we typically like to have (in our version
control repository and then our working space) directories such as:
RepositoryRoot/
Clie
Title: Message
Hi
Vishal,
You
first have to change to the nant sandbox directory, then you should have the bin
directory in a sub-folder and the NAnt.build file in the root folder. If
you then run:
bin\nant.exe package
this
should work. I have updated the readme.txt to (hopefully) b
Can I third this request? I am in much the same position as the other posters
here. What specifically needs to happen in order to take the nightly builds to
a full release? Are there tasks that do not have someone assigned to them? If
so, I am willing to help.
Kevin Dickover
-Original Mess
