We would like to sign our assemblies with a password-protected .pfx file. We also would like our project to build unattended on our build server (msbuild is kicked off by CruiseControl.NET running as a service). The problem is that the automated build fails when attempting to prompt for the .pfx password. We suspect a potential solution lies in the certificate store but could use some help if anyone has a solution or ideas.

Thanks!
Luke

Luke,
I haven't tried this myself, but here's what the developer that owns that feature says,

"If you build once when entering the password, MSBuild will import the data in to a Windows key container and use it from there. You’ll have to input the password once for each build machine but as long as you don’t reimage the box, you should be able to build without a password."

Hope this helps.
Dan (msbuild@microsoft.com)

Luke,
I haven't tried this myself, but here's what the developer that owns that feature says,

"If you build once when entering the password, MSBuild will import the data in to a Windows key container and use it from there. You’ll have to input the password once for each build machine but as long as you don’t reimage the box, you should be able to build without a password."

Hope this helps.
Dan (msbuild@microsoft.com)

Dan,

I'm trying this with MSBuild 3.5 and extensions (MSBuild.ExtensionPack.Framework.Signing). It does not seem to work. I'm being asked for the PFX password every time I run MSBuild, and for each and every assembly that is signed.

Is this a bug or because of the extension pack?

Thanks,
Stefan