Christopher Field
Christopher Field
In keeping with the CLI for `cargo`, there is the `--manifest-path ` option to specify the path to a manifest file, `Cargo.toml`. The default is to use the `Cargo.toml` file...
The `/fd ` is now required for the signtool (#149). The immediate fix is to hard-code the `certHash` value for the ``. This is fine for now, but a command...
As of Rust v1.53.0, the `authors` field is optional and _not_ automatically added to the project's manifest, `Cargo.toml`. The current minimum version supported by this project is v1.40.0 and the...
The [rustc-cfg](https://crates.io/crates/rustc-cfg) crate uses the `rustc --target --print cfg` command, which works for determining toolchain/target information but it will not work for determining Cargo-based compiler configurations, such as features enabled...
Following from discussions in #137, a paragraph mentioning that after initialization at the CLI with the `cargo wix init` command and its various flags and options, customization of the installer...
Following from #137, a `-o,--output` option to completely override the MSI file name, and not just the "name" component, would be useful and more aligned with convention. The current file...
See #114 for the initial information. A Windows built Rust binary (executable) needs a C RunTime (CRT). By default, the CRT is dynamically linked to the executable, which keeps the...
See #131, but the [rusty-fork](https://crates.io/crates/rusty-fork) crate might be useful for isolating each integration test and allowing them to run in parallel. However, there is an outstanding issue related to the...
The `Profile` WiX Variable has been replaced with the more descriptive `CargoProfile`. New projects should use the `CargoProfile` variable and existing projects should migrate accordingly.
As mentioned in #129, a test that actually runs an installer (MSI) created with the cargo-wix subcommand should be added and the correctness verified. The `msiexec` command could be used.