H
High and dRy
I as a developer do not have access to the private key of the company.
So we are using delayed signing to use our .NET dlls in our computer.
Right now the only way we can get out dlls strongly signed is to wait
for the nightly build. That brings up a problem as we need to do a
quick change and send our dlls to the test computers. But it would not
work in the test computer as the dlls are not strongly signed.
I would like to know what are the possible solutions to this problem ?
Can we do some config file manipulation or if we can start a server in
the "Master Computer" that has access to the private key and make a
client that calls on the Master Computer to sign the dlls.
Thanks,
- Saurabh
So we are using delayed signing to use our .NET dlls in our computer.
Right now the only way we can get out dlls strongly signed is to wait
for the nightly build. That brings up a problem as we need to do a
quick change and send our dlls to the test computers. But it would not
work in the test computer as the dlls are not strongly signed.
I would like to know what are the possible solutions to this problem ?
Can we do some config file manipulation or if we can start a server in
the "Master Computer" that has access to the private key and make a
client that calls on the Master Computer to sign the dlls.
Thanks,
- Saurabh