Right now, the UX for enabling / disabling the listing status for PowerShell modules and scripts is a bit challenging, if you have many versions. Could we improve upon this somehow, to enable batch enable / disable of module / script versions?3 votes
Thanks for the feedback, understand the request.
Get-Service -Name $Null returns all services. Expected behavior would be for Name to have ValidateNotNullOrEmpty attribute assigned.4 votes
Because this is technically a breaking change, can you guys provide some data on what kind of scenario this might be impacting for you?
Add a category for DSC Configurations in the PowerShell gallery just like scripts can be posted to the gallery6 votes
We have in plan adding a new filter for “DSCConfiguration”, which will list any module or script with that tag. (Note: case is for readability, only – as usual for PowerShell.) We do not have an ETA, but it is in plan.
Users should be aware that DSC Configurations are scripts, so if they want to see items that are JUST DSC Configurations, they will need to set the filter to show only scripts, not scripts and modules.
As of the time this response is being written, the huge majority of items tagged with DSCCOnfiguration are modules, many of which have sample DSC Configurations included.
In ISE Preview 5.1.1 (running on Windows 10.10586.164, FWIW), this hangs:
"foo" | out-gridview
Then if you hit Ctrl+C, ISEP says "Stopping"... forever.12 votes
When executing the Get-Winevent cmdlet with only the -MaxEvents parameter specified the cmdlet ends up in an infinite loop spewing errors:
Get-WinEvent -MaxEvents 1
Get-WinEvent : The data is invalid
At line:1 char:9
+ $null = Get-WinEvent -MaxEvents 1
+ CategoryInfo : NotSpecified: (:) [Get-WinEvent], EventLogInvalidDataException
+ FullyQualifiedErrorId : The data is invalid,Microsoft.PowerShell.Commands.GetWinEventCommand
I reproduced this error on PowerShell 5.1 and 4.0 on multiple systems. The behavior I expected was to receive the most recent event from any of the event logs. I feel this error could be prevented by using proper parameter validation.3 votes
Not critical, but definitely annoying. I’ve filed a bug internally.
Moved over from this connect issue:10 votes
The v5 online help for ConvertTo-Html shows the content for ConvertTo-Xml instead. Switching to v4 or v3 show the correct content. All languages seem to affected1 vote
In WMF5 Production Preview the [nullable] flag was required to allow a DSC Property to be null valued. Without this flag a default value was being added to the mof file.
In WMF5 RTM (Windows 10 installation) the [nullable] flag causes a System.NotSupportedException error to be thrown when running a configuration block.
In WMF5 RTM, if the [nullable] flag is not used, null values are allowed. I believe this is the same functionality as WMF4.
The [nullable] flag is shown in the MSDN documentation for DSC. https://msdn.microsoft.com/en-us/powershell/dsc/authoringresourceclass
This should be fixed/clarified to the community.1 vote
Finally got this one filed on GitHub: https://github.com/PowerShell/PowerShell/issues/3542
- Don't see your idea?