Kbase P173551: When generating a .NET proxy in ProxyGen selecting the strongnamed-signed runtime option does not ma
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/16/2010 |
|
Status: Unverified
SYMPTOM(s):
Generating .NET proxy from ProxyGen
Selected the strongnamed-signed runtime option
Generated proxy is not strongnamed and signed
FACT(s) (Environment):
OpenEdge 10.x
Windows
CAUSE:
Selecting the strongnamed-signed option for the Runtime field only tells ProxyGen what version of the Progress.*.dll files the generated proxy should be linked against. This option does nothing regarding strongnaming and signing the generated proxy itself. Selecting this option does give the application developer the option of then manually strongnaming and signing both the generated proxy and the .NET application which uses the proxy. Without selecting this option it would not be possible to make the proxy and the .NET application strongnamed & signed.
FIX:
To strongname & sign the resulting proxy (and .NET application) please refer to the Microsoft documentation for the SN.EXE utility. This utility is used to do the strongnaming and signing process.