S
Steve B.
Hi,
I've build a custom web service that is used to digitally signed cab files
that are used to install smart devices application.
Using a standard Process.start and processstartinfo pattern, I run this
command line :
filename :
c:\Program Files (x86)\Microsoft Visual Studio
8\Common7\Tools\Bin\signtool.exe
command line arguments :
sign /f "c:\test\mykey.pfx" -p "password" /v "c:\temp\cabfiletosign.cab"
When this process is executed, and even if the files actually exist (I've
check many times), I get the following error (from the standarderror stream
of the process object) :
--------------------------------------------------
Number of files successfully Signed: 0
Number of warnings: 0
Number of errors: 1
SignTool Error: File not found: c:\test\mykey.pfx
--------------------------------------------------
If I run exactly the same code (a class lib that is referenced in the WS)
from a windows desktop application, I get the following behavior :
--------------------------------------------------
The following certificate was selected:
Issued to: Our company
Issued by: the company
Expires: 01/01/2009 01:59:59
SHA1 hash: the hash
Done Adding Additional Store
Attempting to sign: c:\temp\cabfiletosign.cab
Successfully signed: c:\temp\cabfiletosign.cab
Number of files successfully Signed: 1
Number of warnings: 0
Number of errors: 0
--------------------------------------------------
I've set up IIS 6 to make the web service run with a specific user with it's
own app pool. I've also check that the web service's user can access to all
files that are needed..
Does anybody have an idea about this difference ?
Is there any env variable that could cause ASP.Net web apps to work
differently ?
Thanks in advance,
Steve
I've build a custom web service that is used to digitally signed cab files
that are used to install smart devices application.
Using a standard Process.start and processstartinfo pattern, I run this
command line :
filename :
c:\Program Files (x86)\Microsoft Visual Studio
8\Common7\Tools\Bin\signtool.exe
command line arguments :
sign /f "c:\test\mykey.pfx" -p "password" /v "c:\temp\cabfiletosign.cab"
When this process is executed, and even if the files actually exist (I've
check many times), I get the following error (from the standarderror stream
of the process object) :
--------------------------------------------------
Number of files successfully Signed: 0
Number of warnings: 0
Number of errors: 1
SignTool Error: File not found: c:\test\mykey.pfx
--------------------------------------------------
If I run exactly the same code (a class lib that is referenced in the WS)
from a windows desktop application, I get the following behavior :
--------------------------------------------------
The following certificate was selected:
Issued to: Our company
Issued by: the company
Expires: 01/01/2009 01:59:59
SHA1 hash: the hash
Done Adding Additional Store
Attempting to sign: c:\temp\cabfiletosign.cab
Successfully signed: c:\temp\cabfiletosign.cab
Number of files successfully Signed: 1
Number of warnings: 0
Number of errors: 0
--------------------------------------------------
I've set up IIS 6 to make the web service run with a specific user with it's
own app pool. I've also check that the web service's user can access to all
files that are needed..
Does anybody have an idea about this difference ?
Is there any env variable that could cause ASP.Net web apps to work
differently ?
Thanks in advance,
Steve