Dave
11a7448d7a
Remember installation options and used them to initialize options for the next installation ( #20420 )
2024-05-07 21:45:50 +00:00
Aditya Patwardhan
7144ec707d
Add ProductCode in registry for MSI install ( #19590 )
...
* Add ProductCode in registry for MSI install
* Add test for validating ProductCode regkey is created
* Add test better validation
2023-05-10 05:36:34 +00:00
6dfba03aa3
MSI installer: Add checkbox and MSI property DISABLE_TELEMETRY to optionally disable telemetry. ( #10725 )
...
Co-authored-by: Christoph Bergmeister <christoph.bergmeister@bjss.com >
Co-authored-by: Christoph Bergmeister <christoph.bergmeister@justbeonline.onmicrosoft.com >
Co-authored-by: travis plunk <github@ez13.net >
2023-03-06 13:18:34 -08:00
Aditya Patwardhan
813d38875d
Revert "Replace win7 runtime with win8 and remove APISets ( #18304 )" ( #18322 )
2022-10-18 16:48:07 -07:00
Aditya Patwardhan
cc86f9ffd1
Replace win7 runtime with win8 and remove APISets ( #18304 )
2022-10-18 11:07:22 -07:00
Travis Plunk
f922883757
Set clean state before testing UseMU in the MSI ( #16543 )
2021-12-06 21:18:44 +00:00
Travis Plunk
6317e4e39a
Add Microsoft Update opt out to MSI install ( #15727 )
2021-07-14 15:41:56 -07:00
Travis Plunk
046dec4d7c
Make sure GA revision increases from RC and Preview releases ( #15558 )
2021-06-15 13:44:08 -07:00
Travis Plunk
b1ad606818
Add exe wrapper for Microsoft Update scenarios ( #14737 )
2021-02-19 15:39:35 -08:00
Travis Plunk
6c633e7fc2
A separate Windows packaging CI ( #14670 )
2021-02-08 13:25:14 -08:00
Travis Plunk
d1aa11e367
Fix Path for the Preview MSI ( #13070 )
2020-07-01 09:56:12 -07:00
1397deffe4
Correct stable and preview upgrade codes for MSI ( #13036 )
...
Co-authored-by: Robert Holt <rjmholt_msft@outlook.com >
Co-authored-by: Aditya Patwardhan <adityap@microsoft.com >
2020-06-29 14:13:10 -07:00
xtqqczze
1f252f8bba
Wrap tests in pester blocks ( #12700 )
...
# PR Summary
Wrap tests in pester blocks to prepare for pesterv5
## PR Context
<!-- Provide a little reasoning as to why this Pull Request helps and why you have opened it. -->
## PR Checklist
- [x] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission )
- Use the present tense and imperative mood when describing your changes
- [x] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission )
- [x] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission )
- [x] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress ).
- If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the title (the `WIP` bot will keep its status check at `Pending` while the prefix is present) and remove the prefix when the PR is ready.
- **[Breaking changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes )**
- [x] None
- **OR**
- [ ] [Experimental feature(s) needed](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/6/Microsoft.PowerShell.Core/About/about_Experimental_Features.md )
- [ ] Experimental feature name(s): <!-- Experimental feature name(s) here -->
- **User-facing changes**
- [x] Not Applicable
- **OR**
- [ ] [Documentation needed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission )
- [ ] Issue filed: <!-- Number/link of that issue here -->
- **Testing - New and feature**
- [x] N/A or can only be tested interactively
- **OR**
- [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting )
- **Tooling**
- [x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
- **OR**
- [ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
- Impact on [PowerShell Editor Services](https://github.com/PowerShell/PowerShellEditorServices ) which is used in the [PowerShell extension](https://github.com/PowerShell/vscode-powershell ) for VSCode (which runs in a different PS Host).
- Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
- Impact on [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer ) (which provides linting & formatting in the editor extensions).
- Impact on [EditorSyntax](https://github.com/PowerShell/EditorSyntax ) (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
2020-05-23 13:24:53 +00:00
Steve Lee
b7cb335f03
Update copyright notice to latest guidance ( #12190 )
2020-03-24 11:08:37 -07:00
xtqqczze
b6a687bf21
Correct case of $error special variable
2020-01-13 19:19:39 +00:00
xtqqczze
42d50434f8
Correct case of $PSCmdlet special variable
2020-01-13 19:19:12 +00:00
Steve Lee
a96b4c0404
Update use of "PowerShell Core" to just "PowerShell" ( #9513 )
2019-05-10 15:34:27 -07:00
Reece Dunham
3ab7e2ec4d
Remove extra AppVeyor environment check ( #8709 )
...
Removes a check for AppVeyor env
## PR Context
AppVeyor removed (#8686 extension)
2019-02-08 10:57:41 -08:00
Travis Plunk
77f36498e6
Simplify the paths the MSI uses ( #6442 )
...
- Implementation of PowerShell/PowerShell-RFC#115 (If anything changes in the RFC, we will treat it as a bug, and fix it later)
- Update registry and directory paths to use 6 for the version for stable and 6-preview for a preview release
- Add checkbox to set path
- default checkbox to off for preview builds and on for stable builds
2018-04-02 10:47:29 -07:00
Dave