You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# The application name for any ClickOnce files being signed.
285
+
clickonce-application-name: My ClickOnce application name.
286
+
287
+
# The publisher name for any ClickOnce files being signed.
288
+
clickonce-publisher-name: My ClickOnce publisher name.
289
+
```
290
+
282
291
### Miscellaneous
283
292
```yaml
284
293
# The number of seconds that the Trusted Signing service will wait for all files to be signed before it exits. The default value is 300 seconds.
@@ -295,6 +304,38 @@ trace: false
295
304
```
296
305
297
306
## Best Practices
307
+
### ClickOnce
308
+
Generally you will want to sign an entire package and all its contents i.e. the deployment manifest (`.application` or `.vsto`), application manifest (`.exe.manifest` or `.dll.manifest`) and the underlying `.exe` and `.dll` files themselves. To do this, ensure that the entire contents of the package are available (i.e. the whole `publish` folder from your build) and pass the deployment manifest (`.application` or `.vsto`) as the file to sign - the rest of the files will be detected and signed in the proper order automatically.
309
+
310
+
In the example below, it is only necessary to pass `ClickOnceApp.application` and `setup.exe` to the Trusted Signing Action. The remaining "Application Files" will be signed automatically.
311
+
312
+
```txt
313
+
C:\TEST\ASSETS\SAMPLE-FILES\CLICKONCE
314
+
│ ClickOnceApp.application
315
+
│ setup.exe
316
+
└───Application Files
317
+
└───ClickOnceApp_1_0_0_0
318
+
ClickOnceApp.deps.json.deploy
319
+
ClickOnceApp.dll.deploy
320
+
ClickOnceApp.dll.manifest
321
+
ClickOnceApp.exe.deploy
322
+
ClickOnceApp.runtimeconfig.json.deploy
323
+
Launcher.exe.deploy
324
+
```
325
+
326
+
The following inputs are ignored when signing ClickOnce files:
327
+
- `append-signature`
328
+
- `generate-digest-path`
329
+
- `generate-digest-xml`
330
+
- `ingest-digest-path`
331
+
- `sign-digest`
332
+
- `generate-page-hashes`
333
+
- `suppress-page-hashes`
334
+
- `generate-pkcs7`
335
+
- `pkcs7-options`
336
+
- `pkcs7-oid`
337
+
- `enhanced-key-usage`
338
+
298
339
### Timestamping
299
340
The files must be signed with timestamping enabled in order for the signatures to be valid for longer than 3 days. It is recommended to use the Trusted Signing timestamp server:
0 commit comments