|
I recently had a Visual Studio solution that was being built
using the Solution task which was working fine. There were updates to a referenced assembly (log4net) which
also ended up changing the path for the log4net.dll assembly. Since those
changes, manual builds via VS work ok. However, nant fails because of log4net
as shown below. [solution] Commands:
[solution] /target:library
[solution] /nologo [lots of deleted lines]
[solution] /incremental-
[solution] /checked-
[solution] /unsafe-
[solution] /warnaserror-
[solution]
/out:"C:\working\VisionAIR\2.0_Development\Core\obj\Debug\VisionAir.Core.dll" [lots of deleted lines]
[solution] /r:"C:\Program
Files\VisionAIR\PSS\log4net.dll" [lots of deleted lines] [solution] AssemblyInfo.cs(7,27): error CS0234: The
type or namespace name 'XmlConfiguratorAttribute' does not exist in the class
or namespace 'log4net.Config' (are you missing an assembly reference?) [solution] Failure! (exit code = 1) [solution] Building satellite assemblies... The path reference to log4net was the old reference and was
since changed. The previous version of log4net still resides at that location. Examining the project and solution files do not show any
references whatsoever to log4net at the old location… only the new one. Looking
at the output, I do have one Interop assembly that gets built and after its
generation, during the resource generation, it copies files to a temp
directory. That is actually the first place that I see that it is referencing
the incorrect source dll path. Thus, my question is; Where can nant possibly be picking up the old path from? Any thoughts? |
