Have you tried using with vs.net IDE to build
instead of ?
Another thing to try is this: Before building each
assembly, copy it's dependencies locally.
i.e. build Common, copy it to local folder for the
Accounting project, build Accounting having it reference
it's own copy of Common. Then copy
I agree. This may not be an issue with the SNK file at
all because I added a copy task to copy the SNK file
to the bin/release file and changed the
AssemblyKeyFile path to "DriveTime.snk" and the path
resolves but I still am getting the following error
randomly:
[csc] error CS1606: Assembly signi
I have a nested build that runs nightly. Very
frequently lately, the build fails, randomly. The
failure appears to be due to a locking issue with the
snk file that is used to strongly name each output
assembly.
I have the snk file on the build server in the
following location C:\Temp\.
When the b
Flow of my continuous integration process right now is as
follows:
1. CC.NET detects change in StarTeam
2. CC.NET calls nant bootstrapper script
3. bootstrapper cleans working dir
4. bootstrapper labels current code in StarTeam with build
label from CC.NET
4. bootstrapper checks out current code