Windows 10: PowerShellGet 3.0 Preview 10 Release

Brink · Sep 11, 2020

In this blog post we are excited to share:

PowerShellGet 3.0 preview 10 is now available on the PowerShell Gallery

CompatPowerShellGet compatibility module is now publicly available on GitHub and PowerShell Gallery

Our current thoughts on migrating to PowerShellGet 3.0

PowerShellGet 3.0 Preview Updates

PowerShellGet 3.0 preview 10 is now available on the PowerShell Gallery. This blog post will cover all of the feature updates since we last published a blog post ( preview 6). These versions include completed functionality for updating PSResources, input-object support for installing PSResources as well as several bug fixes. To install the latest version of the module, open any console any run:

Install-Module PowerShellGet -AllowPrerelease -Force -Repository PSGallery -SkipPublisherCheck

Whatâs new in the preview releases

New Features

Completed functionality for Update-PSResource

Input-Object parameter for Install-PSResource

Add âsudoâ check for admin privileges in Unix in Install-PSResource

Adds DSCResources

Bug Fixes

Improved experience when loading module for different frameworks

Bug fix for assembly loading error in Publish-PSResource

Allow for relative paths when registering a PSRepository

Improved error handling for Install-PSResource and Update-PSResource

Remove prerelease tag from module version directory

Fix error getting thrown from paths with incorrectly formatted module versions

Fix bug with retrieving installed scripts in Get-PSResource

Fix bug with AllUsers scope in Windows in Install-PSResource

Fix bug with Uninstall-PSResource sometimes not fully uninstalling

Change installed file paths to contain original version number instead of normalized version

Fix bug related to finding dependencies that do not have a specified version in Find-PSResource

Fix bug related to parsing âRequiredModulesâ in .psd1 in Publish-PSResource

Improve error handling for when repository in Publish-PSResource does not exist

Fix for unix paths in Get-PSResource, Install-PSResource, and Uninstall-PSResource

Add debugging statements for Get-PSResource and Install-PSResource

Fix bug related to paths in Uninstall-PSResource

Bug fix for -ModuleName (used with -Version) in Find-PSResource returning incorrect resource type

Make repositories unique by name

Add tab completion for -Name parameter in Get-PSResource, Set-PSResource, and Unregister-PSResource

Remove credential argument from Register-PSResourceRepository

Change returned version type from âNuGet.Versionâ to âSystem.Versionâ

Have Install output verbose message on successful installation (error for unsuccessful installation)

Ensure that not passing credentials does not throw an error if searching through multiple repositories

Remove attempt to remove loaded assemblies in psm1

Whatâs Next

We plan to have a minimum of three more releases as we approach general availability (GA) of the 3.0 module. Our next planned release, preview 11 will address these issues. Once we are feature complete we will have the release candidate (RC) version. If no high risk or high impact issues are reported after this, we will ship that version of the module (plus any small bug fixes) as the GA version of PowerShellGet 3.0.

Once we reach this important milestone, we will re-evaluate next steps for the module by assessing the flow of incoming issues and re-evaluating issues marked with the âvNextâ milestone in the repository. After we reach GA of this module, we will continue to invest in making PowerShellâs package management experience great.

Availability in PowerShell

We plan to begin shipping PowerShellGet 3.0 in PowerShell 7.2 previews. In these releases of PowerShell 7.2 we will include 2 related modules:

PowerShellGet 3.0

CompatPowerShellGet

Introducing CompatPowerShellGet

CompatPowerShellGet is a compatibility module that allows use of PowerShellGet 2.x (and below) cmdlet syntax with PowerShellGet 3.0 (and newer) functionality by making a best effort mapping between the cmdlet interfaces of both versions of the module. For example, if a user has the CompatPowerShellGet module installed and runs the command: Install-Module PowerShellGet -MinimumVersion 1 -MaximumVersion 2 -AllowPrerelease The CompatPowerShellGet module will get auto loaded into the PowerShell Session and will map the command to PowerShellGet 3.0 syntax: Install-PSResource PowerShellGet -Version "[1,2]" -Prerelease" The command will then be executed by the PowerShellGet 3.0 implementation. The user will also get a warning to update their script to the new cmdlet interface: WARNING: The cmdlet 'Install-Module' is deprecated, please use 'Install-PSResourceâ.

This module is designed so that users will not need to immediately update their scripts in order to update to the latest version of PowerShell or to begin taking advantage of the performance improvements already available in PowerShellGet 3.0. We still do recommend that authors begin making the minimal changes required to update their scripts to the new cmdlet interface.

This compatibility module is designed so that it takes precedence over legacy versions of PowerShellGet. If you have this compatibility module installed and would not like it to be used, you can remove it from the PowerShell session using the Remove-Module command.

Please note that this flow is only possible if the user has both the CompatPowerShellGet module installed and the PowerShellGet 3.0 preview module installed. Once PowerShellGet 3.0 is generally available it will be a dependency of CompatPowerShellGet.

Please also note that this compatibility module will not be called if you use fully qualified cmdlets. For example, if you use PowerShellGet\Install-Module this will call a legacy version of PowerShellGet. If this is a common scenario for you, and will be a barrier to migrating to PowerShellGet 3.0 we would appreciate that feedback in our GitHub repository

Goals of Migration to PowerShellGet 3.0

While creating a migration plan for PowerShellGet users we had the following goals in mind.

Have the quality of PowerShellGet 3.0 be so high that users want to migrate their scripts

Reduce friction for users to take immediate advantage of improvements in PowerShellGet 3.0

Not break any scripts in the short term for user who adopt the latest available version of PowerShell

Create a low friction migration path for script and module owners

Have a single, widely used version of PowerShellGet (for supportability, and improvement reasons)

Look forward to the next blog post (coordinated with our RC release of PowerShellGet 3.0) detailing the feature and performance improvements in PowerShellGet 3.0. We hope this post will give insight into why we believe users will have the best possible experience by migrating to PowerShellGet 3.0.

Migration Timeline

Beginning with PowerShell 7.2 preview 1 release we will ship the latest versions of the PowerShellGet 3.0 and CompatPowerShellGet modules.

As we continue to track usage and feedback around the compatibility layer, as well as the PowerShellGet 3.0 module, we hope to move towards a long term goal of only shipping the latest version of PowerShellGet in new versions of PowerShell.

Feedback and Support

At this stage in our development of the module user feedback is critical. For support or feedback on PowerShellGet please open an issue in this GitHub repository. For support or feedback on the CompatPowerShellGet module, or the migration plan please open an issue in this GitHub Repository.

Sydney Smith
PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...ew-10-release/

:)

Brink · Sep 11, 2020

PowerShellGet 3.0 Preview 3 now available

PowerShellGet 3.0 preview 3 is now available on the PowerShell Gallery. The focus of this release is the -RequiredResource parameter for Install-PSResource which now allows for json, hashtable, or .json files as input. For a full list of the issues addressed by this release please refer to this GitHub project.

Note: For background information on PowerShellGet 3.0 please refer to the blog post for the first preview release and the second preview release.

How to install the module

To install this version of PowerShellGet open any PowerShell console and run: Install-Module -Name PowerShellGet -AllowPrerelease -Force

New Features of this release

New Features

RequiredResource parameter for Install-PSResource

RequiredResourceFile parameter for Install-PSResource

IncludeXML parameter in Save-PSResource

Bug Fix

Resolved paths in Install-PSResource and Save-PSResource

What is next

GitHub is the best place to track the bugs/feature requests related to this module. We have used a combination of projects and labels on our GitHub repo to track issues for this upcoming release. We are using the label Resolved-3.0 to mark issues that we plan to release at some point before we release the module as GA (generally available). To track issues/features to particular preview and GA releases we are using GitHub projects which are titled to reflect the release.

The focus feature for our next preview release (preview 4) is publishing functionality.

How to Give feedback and Get Support

We cannot overstate how critical user feedback is at this stage in the development of the module. Feedback from preview releases help inform design decisions without incurring a breaking change once generally available and used in production. In order to help us to make key decisions around the behavior of the module please give us feedback by opening issues in our GitHub repository.

Sydney Smith PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...3-0-preview-3/

Brink · Sep 11, 2020

PowerShellGet 3.0 Preview 6 now available

Since our last blog post we have released two preview versions (previews 4 and 6) of the PowerShellGet 3.0 module. These releases have introduced publish functionality, repository wildcard search, and fixed error handling when a repository is not accessible in Find-PSResource. Note that preview 5 was unlisted due to a packaging error discovered post-publish.

To install the latest version module, open any PowerShell console and run:

Install-Module PowerShellGet -Force -AllowPrerelease -Repository PSGallery

Highlights of the releases

Preview 4 (3.0.0-beta4) Highlights

New Feature
Wildcard search for the -Repository parameter in Find-PSResource. This allows the user to return results from all registered PSRepositories instead of just their prioritized repository. To use this feature add -Repository '*' to your call to Find-PSResource.

Bug Fix
Fixed poor error handling for when repository is not accessible in Find-PSResource.

Preview 6 (3.0.0-beta6) Highlight

New Feature
The cmdlet Publish-PSResource was introduced which allows users to publish PowerShell resources to any registered PSRepository.

What’s next

We have 3 planned upcoming releases for the module:

The Preview 7 release will focus on update functionality, along with several bug fixes that have been reported by users through our preview releases.

The Release Candidate (RC) release will resolve any remaining bugs not resolved in our Preview 6 release.

The 3.0 General Availability (GA) release will be the same as the RC version so long as no blocking or high-risk bugs are found in the release candidate. If there are any blocking or high-risk bugs, we will release another release candidate before GA.

Migration to PowerShellGet 3.0

We hope to ship the the latest preview of PowerShellGet 3.0 in the next preview of PowerShell 7.1 (preview 6). The goal for this version of PowerShellGet, which will ship in PowerShell 7.1 preview 6, is to contain a compatibility module that will enable scripts with PowerShell 2.x cmdlets (ex. Install-Module) to be run using the PowerShellGet 3.0 module. This means that users will likely not need to update their scripts to use PowerShellGet 2.x cmdlets with PowerShell 7.1. It is important to note, as well, that on systems which contain any other version of PowerShell, the PowerShellGet 2.x module will still be available and used.

We hope to ship PowerShellGet 3.0 with a compatibility layer into PowerShell 7.1 as the sole version of PowerShellGet in the package. However, we will only do this if we reach GA, with a high bar for release quality, in time for the PowerShell 7.1 release candidate.

How to get support and give feedback

We cannot overstate how critical user feedback is at this stage in the development of the module. Feedback from preview releases help inform design decisions without incurring a breaking change once generally available and used in production. To help us to make key decisions around the behavior of the module please give us feedback by opening issues in our GitHub repository.

Sydney Smith PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...iew-6-release/

Brink · Sep 11, 2020

PowerShellGet 3.0 Preview 1 now available

We are excited to announce that our first preview release of PowerShellGet 3.0 is now available on the PowerShell Gallery. This is a major update to PowerShell’s experience for discovering, installing, updating and publishing PowerShell resources like modules, DSC resources, role capabilities and scripts. This was first proposed in RFC PR #185 and superseded by RFC PR #237. Thanks for all the community feedback! For a detailed view of the update to PowerShellGet please refer to the RFC.

This early preview release of the module is not feature complete and has breaking changes intended to improve the user experience. For this reason, the preview release will work side-by-side with your existing PowerShellGet v2 module.

The purpose of this release to begin gathering the critical user feedback to improve the module through subsequent preview releases before we finalize the design for General Availability later this year.

How to Install PowerShellGet 3.0 Preview 1

Prerequisites

Please ensure that you have the latest (non-prerelease) version of PowerShellGet and PackageManagement installed.

To check the version you currently have installed run the command:

Get-InstalledModule PowerShellGet, PackageManagement

The latest version of PowerShellGet is 2.2.3, and the latest version of PackageManagement is 1.4.6.

To install the latest versions of these modules run the following at the start of a fresh PowerShell session:

Install-Module PowerShellGet -Force -AllowClobber

Installing the Preview side by side

To install this preview release side-by-side with your existing PowerShellGet version, open any PowerShell console and run:

Install-Module PowerShellGet -Force -AllowPrerelease

To register the PSGallery run the command:

Register-PSResourceRepository -PSGallery

If you run the command Get-Command -Module PowerShellGet you will get a good picture of the side-by-side cmdlet interfaces.

High-Level Goals of PowerShellGet 3.0

PowerShellGet 3.0 is a complete re-write of PowerShellGet with the following goals:

Improve maintainability of the codebase: This goal is addressed by removing the provider model that PowerShellGet was originally built on. This means that PowerShellGet 3.0 does not take a dependency on OneGet, NuGet or any other package provider. Further, this version is written in C# instead of PowerShell script which has allowed us to simplify the code base. By using the lessons learned from previous versions of the module we hope that a cleaner implementation and interface will allow us to more quickly address bugs as they arise and iterate on our vNext issues more efficiently.

Address top customer issues. Many of the top customer issues in previous versions of the module have been challenging to resolve because of architecture decisions made early on in the development of PowerShellGet. Below we enumerate many of these issues we hope to resolve, to view a full enumeration of these issues view this GitHub query.

Features of this Release

A new set of cmdlets which abstract all PSResource types (Module, Script, DSCResource, RoleCapability, Command) to a single set of cmdlets which use the noun “PSResource”. Many of these cmdlets use a -Type parameter for the user to specify the PSResource type if they would like.

Code:

Find-PSResource
Get-PSResource
Get-PSResourceRepository
Install-PSResource
Register-PSResourceRepository
Set-PSResourceRepository
Uninstall-PSResource
Unregister-PSResourceRepository
Update-PSResource
SYNTAX
Find-PSResource [[-Name] <string[]>] [-Type {Module | Script | DscResource | RoleCapability | Command}] [-Version <string>] [-Prerelease] [-ModuleName <string>] [-Tags <string[]>] [-Repository <string[]>] [-Credential <pscredential>] [-IncludeDependencies] [-WhatIf] [-Confirm] [<CommonParameters>] EXAMPLE Find-PSResource -Name PowerShellGet -Type Module -Prerelease
Click to expand...

For the cmdlets Register-PSRepository and Set-PSRepository a -Priority parameter allows setting the search order of repositories with a lower value indicating a higher priority. If not specified, the default value is 50. The PSGallery, which is registered by default, has an editable value of 50. If two PSRepositories have the same priority the “Trusted” one will be chosen, if they also have the same level of trust the first one alphabetically will be selected.

For Find-PSResource the -Repository parameter supports wildcard search. If no repository is specified, the cmdlet will return the latest version found from the repository with the highest priority.

Find-PSResource Az.Sql -Repository *Name Version Repository Description
—- —————– ———–
Az.Sql 2.5.0 PSGallery Microsoft Azure PowerShell – SQL service cmdlets for Azure Resource…
Az.Sql 2.5.0 PoshTestGallery Microsoft Azure PowerShell – SQL service cmdlets for Azure Resource…Find-PSResource Az.SqlName Version Repository Description
—- ——– ———- ———–
Az.Sql 2.5.0 PSGallery Microsoft Azure PowerShell – SQL service cmdlets for Azure Resource…

For Find-PSResource and Install-PSResource the -Version parameter will accept strings (with wildcard support) based on the Nuget version range syntax

Code:

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version *

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.2.0 PSGallery Cross-platform GUI Tools for Pow.
Microsoft.PowerShell.GraphicalTools 0.1.0 PSGallery Cross-platform GUI Tools for Pow.

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version "(0.0,1.0)"

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.2.0 PSGallery Cross-platform GUI Tools for Pow.

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version "0.1.1"

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.1.0 PSGallery Cross-platform GUI Tools for Pow.
Click to expand...

Install-PSResource has a -DestinationPath parameter which allows the user to specify the target directory instead of the default one. Note that in this release “x86” paths, and Linux paths are not yet supported. Expect to see this support in future releases.

Update-PSResource has an -UpdateTo parameter with values MinorVersion (the default), MajorVersion and, PatchVersion.

There is support for NuGet v2 and v3 endpoints for PSRepositories.

If any of the features on this list are not behaving how you would expect them to, or would prefer them to be sure to open an issue in our GitHub repository.

Table of Implemented Parameters in this Release

[table][tr][td]Cmdlet[/td] [td]Implemented parameters[/td] [td]Not implemented[/td] [/tr] [tr][td]Install-PSResource[/td] [td]-Name-Version -Prerelease -Repository -Credential -Scope -Reinstall[/td] [td]-InputObject-DestinationPath [partially implemented] -NoClobber -IgnoreDifferentPublisher -TrustRepository -Force [there hasn’t been a need for force yet since the things you would force aren’t implemented] -Quiet -AcceptLicense -PassThru[/td] [/tr] [tr][td]Update-PSResource[/td] [td]-Name-Version -Prerelease -Credential -Repository [Update should be discovering the repository from the xml metadata instead of from user input, this will be fixed in future releases][/td] [td]-InputObject-UpdateTo -Force -Quiet -AcceptLicense -PassThru[/td] [/tr] [tr][td]Find-PSResource[/td] [td]-Name-Type -Version – Prerelease -ModuleName -Tags -Repository -Credential -IncludeDependencies[/td] [td][Nothing][/td] [/tr] [tr][td]Uninstall-PSResource[/td] [td]-Name-Version -PrereleaseOnly[/td] [td][Nothing][/td] [/tr] [tr][td]Save-PSResource[/td] [td]-Name-Version -Prerelease -Repository -Credential -AsNupkg -Path[/td] [td]-AcceptLicense[/td] [/tr] [tr][td]Get-PSResource[/td] [td]-Name-Version[/td] [td]-Prerelease[/td] [/tr] [tr][td]Register-PSResourceRepository[/td] [td]-Name-URL -PSGallery -Credential -Trusted -Priority[/td] [td]-Repositories-Proxy[for any proxies other than the default proxy] -ProxyCredential[see above regarding -Proxy][/td] [/tr] [tr][td]Unregister-PSResourceRepository[/td] [td]-Name[/td] [td][Nothing][/td] [/tr] [tr][td]Get-PSResourceRepository[/td] [td]-Name-URL -Credential -Trusted -Priority[/td] [td]-Repositories-Proxy [for any proxies other than the default proxy] -ProxyCredential [see above regarding -Proxy][/td] [/tr] [/table]

What’s Coming Next

Features to Expect in Coming Preview Releases

This module is not feature complete, meaning many issues/bugs in this release may just be features we have not finished implementing.

Below is a list of features that we are still in the process of implementing which you can expect to see in future preview releases.

Publish functionality (in the meantime the publish functionality of PowerShellGet2.x works nicely side-by-side)

Error handling, warnings, -Verbose, and -Debug parameters (for the full list of missing parameter see the table above).

Local cache–this important feature significantly improves the performance of Find/Install operations. Look forward to it in future releases.

Dependency management. In future releases, Install-PSResource will accept a path to a psd1 or json file (using -RequiredResourceFile), or a hash table or json (using -RequiredResource) where the key is the module name and the value is either the required version specified using Nuget version range syntax or a hash table where repository is set to the URL of the repository and version contains the Nuget version range syntax.

Install-PSResource -RequiredResource @{ "Configuration" = "[1.3.1,2.0)" "Pester" = @{ version = "[4.4.2,4.7.0]" repository = "PowerShell Gallery | Home" credential = $cred allowPrerelease = $true } }

In this case the modules named “Configuration”, and “Pester” will be installed.

The JSON format will be the same as if this hashtable is passed to ConvertTo-Json:

{ "Configuration": "[1.3.1,2.0)", "Pester": { "version": "[4.4.2,4.7.0]", "credential": null, "repository": "PowerShell Gallery | Home", "allowPrerelease": true } }

We will introduce a New-RequiredResourceFile cmdlet which will create a template file.
If the switch -AsPSD1 is used it will create a psd1 file, otherwise it will default to JSON.

Save-PSResource -Type Library will download nupkgs that have a lib folder. The dependent native library in runtimes matching the current system runtime will be copied to the root of the destination specified. A -IncludeAllRuntimes can be used to explicitly retain the runtimes directory hierarchy within the nupkg to the root of the destination.

Native credential management/credential persistence for registered PSRepositories

Improvements we are Considering Post-GA

One important goal of PowerShellGet 3.0 is to improve the supportability of the module. As a result, once this work is complete,we hope to iterate more quickly, and tackle other top customer issues. This list represents issues we are considering tackling but have not committed to yet.

We will explore automatic updating of the cache in which on any operation that reaches out to a repository, a REST API will be called to see if the hash of the cache matches the current cache and if not, a new one is downloaded. This system may also take into consideration how recently the cache has been updated to avoid constant updates.

We will explore an Enable-PowerShellGetAlias cmdlet that will allow users to use known cmdlets like Install-Module from the PowerShellGet 3.0 implementation.

We will explore uninstalling orphaned dependencies automatically.

To track the full list of issues we are considering we are using the label vNext in our GitHub Repository.

How to Track the Development of this Module

GitHub is the best place to track the bugs/feature requests related to this module. We have used a combination of projects and labels on our GitHub repo to track issues for this upcoming release. We are using the label Resolved-3.0 to label issues that we plan to release at some point in before we release the module as GA (generally available). To track issues/features to particular preview and GA releases we are using GitHub projects which are titled to reflect the release.

Please note that PowerShell/PowerShellGet now represents the codebase for PowerShellGet 3.0. If you are looking for the source code, or issues related to previous versions of PowerShellGet, use PowerShell/PowerShellGetV2.

Timeline/Roadmap

Expect to see preview releases as new functionality is added/changes are made at approximately a monthly cadence until the module is feature-complete. Through this process we will also be adapting the module based on user feedback. Once we feel we have reached a sufficient quality and completeness, we will release a “Release Candidate” version of the module. Assuming this release does not require any high impact changes, we will then release that version of the module as “Generally Available”. Since these milestones are quality, rather than date, driven we can not offer an exact timeline at this point, but hope to release the module later this year.

How to Give feedback and Get Support

We cannot overstate how critical user feedback is at this stage in the development of the module. Feedback from preview releases help inform design decisions without incurring a breaking change once generally available and used in production. In order to help us to make key decisions around the behavior of the module please give us feedback by opening issues in our GitHub repository.

Sydney Smith
PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...3-0-preview-1/

Windows 10: PowerShellGet 3.0 Preview 10 Release

PowerShellGet 3.0 Preview 10 Release

PowerShellGet 3.0 Preview 10 Release

PowerShellGet 3.0 Preview 10 Release

PowerShellGet 3.0 Preview 10 Release - Similar Threads - PowerShellGet Preview Release

No Insider Release Preview Available Since 3/8

No Insider Release Preview Available Since 3/8

PowerShell 7.2.0 preview 3 released - Feb. 11

PowerShellGet 3.0 Preview 6 now available

PowerShell 7.1.0 preview 3 released

PowerShellGet 3.0 Preview 3 now available

PowerShellGet 3.0 Preview 1 now available

Visual Studio "15" Preview 3 released

Preview release.