Flavien Michaleczek
My feedback
-
32 votes
This is something we’d like to fix, but we’re still evaluating at a high-level how to make future improvements to Out-GridView.
Thanks,
JoeyAn error occurred while saving the comment -
1 vote
An error occurred while saving the comment It's not a bug on powershell.
When you do Get-Module -ListAvailable | %{ Get-Command $_.Name } , powershell load modules to know which commands are available.
The module SQLPS, has a PSDrive mounted after loading.
So use Push-Location, Pop-Location inside foreach.
-
60 votes
-
10 votes
Yeah, that seems like it makes sense. Looking for more votes to drive prioritization.
An error occurred while saving the comment These syntaxes are working :
Write-Verbose ("Hello {0}" -f $var.prop)
or
"Hello {0}" -f $var.prop | Write-Verbose
-
5 votes
-
3 votes
-
35 votes
-
2 votes
-
13 votes
An error occurred while saving the comment Before registering PS Repository, you must add these lines :
if ((Get-Packageprovider -Name NuGet) -eq $null) {
Install-Packageprovider -name nuget -requiredVersion 2.8.5.201 -Scope CurrentUser -force
} -
10 votes
-
7 votes
-
7 votes
An error occurred while saving the comment We can't use a lot of words in method of a class.
But we can use these same words for a class name or a class property.By example, this is valid :
class Exit {
$Exit = 5
}But this is invalid :
class Myclass {
Exit() {}
}So, we can't use a class Name "Exit" in the real world, because it's impossible to use a constructor (but possible to create it without a constructor)
The normal behavior would be "same restriction" that Add-Member -MemberType ScriptMethod
By Example, this is valid :
$object = [psobject]::new() | Add-Member -MemberType ScriptMethod -Name if -Value { "Valid" } -PassThru
$object.If()There is more words we can't use than defined in the reserved word page
https://technet.microsoft.com/en-us/library/hh847868.aspx?f=255&MSPPError=-2147217396The banned word list came from the class "System.Management.Automation.Language.Tokenizer" :
elseif
if
else
switch
foreach
from
in
for
while
until
do
try
catch
finally
trap
data
return
continue
break
exit
throw
begin
process
end
dynamicparam
function
filter
param
class
define
var
using
workflow
parallel
sequence
inlinescript
configuration
public
private
static
interface
enum
namespace
module
type
assembly
command
hidden
baseSome words like "Parallel", "Configuration", "Exit", "Filter", "Data", "Base" are too generic to be forbidden.
This is a serious restriction that can slow down classes adoption for the mass.
Powershell can't be a "First-class citizen" with this kind of bug.
-
1 vote
From the GitHub Issue:
“I agree that it might be useful super forward-looking, but today this will only help in the case where:
You’re running PS 5.1+, the module you’re running is using a SuppressMessageAttribute, and you don’t have Script Analyzer installed
Given all that, this is firmly within the realm of “nice to have” for me, and I’m not sure anything nice to have can make it in PS 5.1 right now. I’m going to place it on UserVoice, though, as something we might want to do in the future for PowerShell." -
6 votes
We are working on enabling support for multiple psm1 files. This will allow you to group different class-based DSC resources into different files.
-
3 votes
This is an issue specific to the Chocolatey provider, which we acquired from that team. We will continue to work to get it resolved, but have no solution available at this time.
An error occurred while saving the comment The issue is still here.
PSVersion : 5.1.14328.1000 (Desktop)
PackageManagement Version : 1.0.0.1
ExecutionPolicy : RestrictedCommand to reproduce the problem : Install-package firefox -ProviderName Chocolatey
Package Firefox is installed BUT Firefox is not installed and there is no warning.
The script "chocolateyInstall.ps1" from Firefox Chocolatey package is not execute because of the execution policy and we need an error to indicate the package has not be installed.
-
125 votes
Thanks for the feedback! I have personally heard this request from a number of customers. IMHO having the ability to use GMS accounts would be a quite useful in DSC configurations. If this is an important feature for you as well, vote it up so that we can appropriately prioritize it as we move forward.
MarkG
-
13 votes
-
5 votes
-
5 votes
-
12 votes
Thanks for the suggestion. This is something we are investigating, but it requires some complex review to ensure proper operation across a range of Windows actions (eg: applying Windows updates). No decision has been made at this time.
@Jakob Windows PowerShell is archived. Microsoft release only security fixes through Windows 10
version. Upgrade to PowerShell 7 and open an issue on Github repository if you need enhancements.