| title | ms.custom | ms.date | ms.prod | ms.reviewer | ms.suite | ms.technology | ms.tgt_pltfrm | ms.topic | f1_keywords | dev_langs | helpviewer_keywords | ms.assetid | caps.latest.revision | author | ms.author | manager | translation.priority.ht | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
-DELAYSIGN (Partially Sign an Assembly) | Microsoft Docs |
11/04/2016 |
visual-studio-dev14 |
|
article |
|
|
|
15244d30-3ecb-492f-a408-ffe81f38de20 |
11 |
corob-msft |
corob |
ghogen |
|
/DELAYSIGN[:NO]
where,
NO
Specifies that the assembly should not be partially signed.
Use /DELAYSIGN if you only want to place the public key in the assembly. The default is /DELAYSIGN:NO.
The /DELAYSIGN option has no effect unless used with /KEYFILE or /KEYCONTAINER.
When you request a fully signed assembly, the compiler hashes the file that contains the manifest (assembly metadata) and signs that hash with the private key. The resulting digital signature is stored in the file that contains the manifest. When an assembly is delay signed, the linker does not compute and store the signature, but reserves space in the file so the signature can be added later.
For example, using /DELAYSIGN allows a tester to put the assembly in the global cache. After testing, you can fully sign the assembly by placing the private key in the assembly.
See Strong Name Assemblies (Assembly Signing) (C++/CLI) and Delay Signing an Assembly for more information on signing an assembly.
Other linker options that affect assembly generation are:
-
Open the project's Property Pages dialog box. For details, see Setting Visual C++ Project Properties.
-
Click the Linker folder.
-
Click the Command Line property page.
-
Type the option into the Additional Options box.
- See xref:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.AdditionalOptions%2A.