I'm using .NET 2.0 to develop my product. I've built a build system using
MSBuild that is building my C# assemblies.  I've created a strong name key
pair, and I've extracted the public key into a separate file.  The MSBuild
build process is using the standard Microsoft.CSharp.targets file to build
my assemblies.  I've also configured my MSBuild build process to delay sign
my assemblies using the extracted public key.

Here's the problem that I'm seeing.

My build process is producing 4 assemblies.  Three of the assemblies are
based on C# code that I have written.  The fourth assembly is an
XmlSerializers assembly that is being generated by the sgen.exe utility.

In the output directory where my assemblies are being written to, only two
of my assemblies and the XmlSerializers assembly appear to have been delay
signed.  According to the sn.exe utility, the last assembly isn't delay
signed.

However, looking at the MSBuild log, the csc.exe tool is being run with both
the key file and the delay sign flag.  When I look in the intermediate obj
file where the compiler writes the assembly to, the generated assembly is
delay signed.

So when the assembly is being copied by MSBuild into the output directory,
somehow, something is thinking that this assembly is not delay signed.  I am
seeing the same behavior for both of my debug and release builds.

Has anyone seen anything similar to this? Any ideas on what I can do to
correct the problem?

Thanks.

Michael