We have an ASP app which compiles Silverlight DLLs and shoves them in a Xap package. The ASP app then needs to sign the Xap package with a certificate for elevated trust to work. This is done by calling signtool.exe. This has been working without a problem,
but it stopped working once I started using ASP.Net impersonation. For those who are unfamilar, impersonation simply allows the ASP app to talk to the hard drive or network file structure as the impersonated user. Signtool now fails with an exit code of 1.
I don't get any error to explain what is going wrong.
This is the line in web.config which causes impersonation to work
<identity impersonate="true" userName="[...]" password="[...]" />
So, the most obvious issue would be a security issue right? You would think that its an issue where the impersonated user doesn't have access to run signtool.exe. Well, what I did to rule ...
Go to the complete details ...