How to build into a folder use vs2022

kenkendk · February 11, 2025, 11:22pm

Hi @ nadirvishun, welcome to the forum.

I have updated the README to point to the current location:

That executable is a thin wrapper for the Windows Service. Yes, it can be built by the .NET8 SDK, and by extension, also VS2022.

That is done by the tool ReleaseBuilder.

See the README:

github.com

duplicati/duplicati/blob/master/ReleaseBuilder/README.md

# Release Builder tool

This folder contains the `ReleaseBuilder` tool which builds installers and packages for all supported operating systems.

The tool is tested and used only on MacOS, but can be configured for other operating systems, including WSL and to some extent Windows.

The setup is a mix of environment variables, settings files and commandline arguments.

# Required environment

The environment variables used by the tool are:

- `UPDATER_KEYFILE`: The file containing the key used to sign the manifest. Create one with the `create-key` command.
- `GPG_KEYFILE`: A file encrypted with AESCrypt and the general password. The file has two lines: `GPGID` and `GPGPassphrase` which are given to the `GPG` command.
- `AUTHENTICODE_PFXFILE`: A PFX file containing a signing key for Authenticode signing of Windows executables (needs to be purchased at a certificate vendor).
- `AUTHENTICODE_PASSWORD`: A file encrypted with AESCrypt and the general password. The file contains a single line, which is the password used for `osslsigncode`
- `GITHUB_TOKEN_FILE`: A personal access token for Github API used to create releases and upload packages to Github.
- `DISCOURSE_TOKEN_FILE`: A personal access token for Discourse, used to create release posts.
- `CODESIGN_IDENTITY`: The identity used for MacOS `codesign` when signing the binary packages.
- `NOTARIZE_PROFILE`: The name of the profile used for notarizing MacOS packages.

This file has been truncated. show original

Near the end is an example for how to build the zip files.

This is done with wixl from the msitools project. This does not work on Windows, but it should be somewhat compatible with WiX 3.