Remove the functions which generated Nuget packages for Windows.
Add function New-UnifiedNugetPackage to generate nuget packages for each assembly with unix and windows runtimes.
Add function New-NuSpec and New-ReferenceAssembly for creating the required items forNew-UnifiedNugetPackage.
Add a sample for cross platform project with conditional compilation for Linux.
Add function Publish-NugetToMyGet to publish nuget packages to powershell.myget.or
Based on standard practices, we need to have a copyright and license notice at the top of each source file. Removed existing copyrights and updated/added copyright notices for .h, .cpp, .cs, .ps1, and .psm1 files.
Updated module manifests for consistency to have Author = "PowerShell" and Company = "Microsoft Corporation". Removed multiple line breaks.
Separate PR coming to update contribution document for new source files: #6140
Manually reviewed each change.
Fix#6073
* Test fixes and changes needed to support Pester 4.0.8
* Replace 'Should Contain' with new 'Should FileContentMatch' assertion
Explicitly check for string creation with write-output
* Use the current version of pester and install it in modulesDir
* Simplify logic for relative path test.
Multiple '..' is not needed for a relative path, a single one will do. Also, on multi-drive systems using split-path -noqualifier will probably do the wrong thing with regard to constructing a correct path.
Remove extraneous Should Not Throw test, if this throws, the test will fail, we don't need to explicitly assert the not throw
* In some environments it is possible that computer name is 'localhost', so that should be allowed
* [feature] Add link for migrating tests from Pester v3 to v4
Fix up capitalization and white space issues
Change one test to check FullyQualifiedErrorId rather than just `Should Throw`
* [feature] update invoke-item test to handle the case where multiple notepad processes are running
* Fix spelling issue with Pester 4x, calling it Pester 4 should be sufficient
Instead of building PSReadLine from this repo, pull it from the gallery using nuget cache.
This pulls v2.0 of PSReadLine which does have documented breaking changes from v1.2, but the risk is small - the features that have changed are typically only used in a profile and aren't used all that often anyway.
Fix#996
Hardcodes version of modules pulled from PSGallery
Since Pester is not a submodule anymore, replace submodule example in git submodule docs/FAQ.md with the only leftover submodule src/libpsl-native/test/googletest
Since Pester is not a submodule anymore, replace submodule example in git submodule docs/FAQ.md with the only leftover submodule src/libpsl-native/test/googletest
refactor code to restore pester into a separate function called Restore-PSPester
update message on what to do when pester is missing
Add ability for get-psoptions to default to new-psoptions
fix an issue with publish-pstesttools when a build has not been run since build.psm1 has been imported (try to use the default options)
make start-pspester use the last build, not just use the default options
fix an issue in restore caused some files not to be removed
* Add dependency nuget packaging instructions for PowerShell.Core.Instrumentation ETW resource binary.
* Fix markdown MD031 Fenced code blocks errors.
* Fix MD022 Headers should be surrounded by blank lines
* Add a note about Authenticode Dual-signing requirement.
* PR Feedback.
* Set version to Beta.10
- Support '[package]' tag in PR CI to validate packaging changes in PR CI runs.
When using '[package]' tag, regular CI tests will run and packaging steps will also run.
- Fix nightly build on macOS.
- Update `installpsh-suse.sh` to work with the .tar.gz binary archive.
- Remove `download.sh` as it's not used anywhere now. (checked with PowerShellGet and OneGet, they are using a local copy of download.sh).
* Skip check 'vsruntime140.dll' on Win10
* Make the precheck accurate
* Update windows installation prerequisites
* Change 'higher' to 'above'
* Address comments
* Address more comments
* Address some more comments
* [Feature] Update the installer test
* Update coding guidelines to make it more concrete and useful in a review process.
* Add a section about security
* Address comments
* Update .spelling
* Address more comments
* Address comment about the security section
* Fix 'i.e.' and 'e.g.'
* Update .spelling
* One more tweak
* Add motivation for using 'nameof'
Update pull-request-process to clarify role/responsibility of author and reviewers based on recent feedback from team and community. Also moved it to `.github/CONTRIBUTING.md` so that all related information can be found at one place.
The updates to build.psm1 and packaging.psm1 create a single package (per bitness), which works on all the Windows OS versions, namely Windows 7 / Windows Server 2008 R2, Windows 8.1 / Windows Server 2012 R2, Windows 10 / Windows Server 2016.
* #4458 MSI installer checks that the Windows C Runtime and VS Studio 2015 C++ redistributables are present and returns error message if not.
Includes tests to check that the Wix file contains the download URLs and those URLs are not dead.
* Fix the path on windows containers (#4241)
* Updated string to reflect beta.4 version (#4238)
* Add beta.4 changelog (#4245)
* first pass at beta.4 changelog
* grammar and spelling fixes (#1)
* sort and add new words to dictionary (#4248)
* Update release documentation to reflect the desired release steps and order.
* Update in-doc links
* Update .spelling
* Address comments
* Additional changes to build/package example
* Update .spelling
* Remove another internal URL
* Name and link updates could be automated
* Move 'Note' to the top of 'Release Steps' section
* First iteration
* Second iteration
* Third iteration
* Fourth iteration
* Fifth iteration
* Revert the temporary workaround
* beta.1 release only support Mac OSX 10.12+
* Debian8 update
* RHEL7 update
* Main page update
* Fixed 'MD024 Multiple headers with the same content'
* Update linux.md
Added explicit text about compatibility of Ubuntu14.04 pkg on Debian8 to avoid confusion about URLs
* Update linux.md
- FullCLR build is disabled in this change.
- FullCLR build related functionalities in `build.psm1` and `AppVeyor.psm1` are disabled. They are not cleaned up from `build.psm1` and `AppVeyor.psm1` yet. We need to adopt .NET Core 2.0 to verify the portable module concept, and if that works well, we will remove the Windows PowerShell source code and clean up our scripts.
- `dnxcore50` and `portable-net5+win8` target framework monikers are removed.
- Dependency on `Microsoft.NETCore.Portable.Compatibility` is removed. It's not necessary, but it may come back when we work on supporting the `portable module`. Its necessity can be reviewed at that time.
- I didn't spend the time to try building powershell in Visual Studio 2017. We should have a separate issue for that. It's tracked by #3400
The `TypeCatalogParser` project is replaced by a MSBuild target to gather the dependency information.
Due to .NET Core SDK issue [#1021](https://github.com/dotnet/sdk/issues/1021), our meta-package project `Microsoft.PowerShell.SDK` starts to generate an empty assembly during the build and that results in an empty assembly `Microsoft.PowerShell.SDK.dll` appear in `publish` folder and in `.deps.json` file. We cannot simply remove the assembly because it's now part of the TPA, and removing it will cause powershell to crash at startup. We have to live with this empty assembly until that .NET Core SDK issue is fixed. It's tracked by #3401.
* Fix Markdown lint issues
Make header styles consistent
Make header names unique (make anchors usable)
* Fix spelling of sign up
* Add words used in readme to spelling dictionary.
* corrected use of PSModulePath casing to be consistent with Windows PowerShell
addresses #3227
* addressing review feedback
make "PSModulePath" into const
fixed some test workarounds due to failures for external reasons that wasn't meant to be checked in
* addressing review feedback
make "PSModulePath" into const
fixed some test workarounds due to failures for external reasons that wasn't meant to be checked in
* Changed broken link to a working blog post
"run-ps" isn't a linkable document, so I changed the "Running PowerShell Scripts Is as Easy as 1-2-3" to link to an external article on Windows IT Pro with the same name.
* Rebase onto .NET Core 1.1
Modify `Build.psm1` and `project.json` files to use .NET Core 1.1.
.NET Core 1.1 ships with an older dotnet/cli than has currently been used,
so we revert to use case-sensitive directory names for dependencies.
.NET Core 1.1 is a pre-requisite for supporting Fedora 24.
* PSReadLine: Bump major version of PSReadline to 6.0.0-*
* Microsoft.PowerShell.Commands.Utility: Bump major version of Microsoft.CodeAnalysis.Csharp
* Microsoft.PowerShell.SDK: Revert attempt to import netcoreapp1.1 instead of dnxcore
* build.psm1: Restore ability to specify version of dotnet-install.sh
Add test roadmap plan document
Update document with clarifying language for code coverage
Also add an acceptance criteria for remoting tests
include Jenkins with mention of MS Build Lab for possible test infrastructure
- Add RequireAdminOnWindows to the list of blessed tags
- Fix a bug in Get-PesterTag where we accepted 'Slow' as a proper priority
- Fix missed comma in Start-PSPester parameters
- Add documentation about new Pester tag
- Fix finishing logic for Start-PSPester -Unelevate
* correct links in test-guidelines.md (issue #1665)
added specific links for PesterDoAndDont and WritingPesterTests
added new section in WritingPesterTests.md on bulk skipping tests
* update test directories to include a directory for remoting tests
* fix lines in document to use semantic line breaks
also remove trailing spaces after "."
Again, .NET Core expects users to forcibly link the third party OpenSSL
libraries into system directories, which the Homebrew team advises
strongly against (and attempts to prevent). This also affects the
System.Net.Http library, and results in runtime errors during SSL
certificate validation. So instead, we patch what we can, when we can.
Use `dpkg -i` followed by `apt-get install -f`. Alternatives considered
included using `apt install`, which does not work, and copying the
PowerShell package to `/var/cache/apt/archives` which is just as messy
as this. At least this follows the same steps as `download.sh`.
* Move PesterDoAndDont.md into WritingPesterTests.md
* Add powershell language moniker to codesnippets
in WritingPesterTests.md
Add extra new-lines for formatting
* Adding here-string info to testings docs
This change fixes a broken link in the Using Visual Studio Code
documentation. This link is pointing to a GitHub repo that will never
made public. The resolution is to change the link to point to the public
vscode-powershell repo.
* Clarifying OSX, adding issue with Install-Package
- Changing first section to "non-Windows" and clarifying that most of these issues apply to both Linux & OSX.
- Fixed a few typos.
- Adding known issue with Install-Package per #1773
* Mac OSX -> macOS
Complying with convention used in #1934
* added alpha build # to install-package notice
* typo
* Typo
This change updates the "Using Visual Studio Code" documentation to
mention the requirement of having OpenSSL installed on OS X. Brief
installation instructions have been included.
