For generic PowerShell questions you can use the community slack http://slack.poshcode.org/
I've been going through Create a Crescendo cmdlet - PowerShell | Microsoft Docs. Unfortunately, there's a problem with the samples is that a parameter might be optional in one parameter set, but mandatory in another.
In my case, I'm working on a cmdlet where several parameters can be specified, but you must specify at least one.
No mention is made of the Position option for the
ParameterAttribute.
Also, can a parameter be one of several types? For instance, if the parameter is a URL, I like to accept either a
System.URI or a string. For a folder, I like to take either a System.IO.Directory or a string.
4 replies
Hi guys, I raised a feature request issue ~2 years ago, and the thread is pretty dead. I've just realised that the issue doesn't have a "Needs Triage" label, and I can't see any way to add the label myself.
Is there anyone here who can add labels to issues?
PowerShell/PowerShell#12047
Is there anyone here who can add labels to issues?
PowerShell/PowerShell#12047
Weird. On Windows 11 Pro, PowerShell 7.2.4 thinks it's running on Windows 10.0.22000.
If I'm expecting a
System.Guid, I don't want them passing 4. Plus, this way, I'm not converting objects to/and from string as much.
Crescendo needs a documentation site for the schema. It should provide details on each field and samples. For instance, a page should be present describing the
HandlerType and Handler members of a OutputHandler member. What do those values mean? A few random blog posts don't count. It would appear that HandlerType can only have one of several values. So list them and describe each. Then describe how that affects how Handler is interpreted.
1 reply
Doesn't look like it.
If I have a string with an unknown number of whitespace characters at the start, is there a handy way to determine how many?
Well, I wrote a class method:
hidden [int]GetIndentLevel()
{
$this.CurLine -match '^(?<Indent>\s*';
return $Matches.Indent -split '( |\t)';
}
Are PowerShell classes passed by reference? I'm looking for the equivilent of the C#
ref keyword so I can have a function I call make changes to a variable in my scope.
I see
[ref], but that's a type by itself and ruins my type safety. I'd rather declare the parameter as ref [int] name and pass the variable with ref valueVar like I would with C#.
The documentation for
[ref] also seems to suggest it's mainly for COM.
People still explicitly use COM?
So 1990s.
Well, based on this, that's a resounding no.
C:\Users\willp> function Test([string]$x){$x = '%'}
C:\Users\willp> $g = 'dgfd'
C:\Users\willp> Test($g)
C:\Users\willp> $g
dgfd
C:\Users\willp> function Test([ref]$x){$x = '%'}
C:\Users\willp> Test($g)
Test: Cannot process argument transformation on parameter 'x'. Reference type is expected in argument.
Neither option worked.
Well, I had the usage of
[ref] wrong, but I'm still missing something.C:\Users\willp> Test(([ref]$g))
C:\Users\willp> $g
dgfd
C:\Users\willp> function Test([string]$x){$x = '%'}
C:\Users\willp> Test(([ref]$g))
C:\Users\willp> $g
dgfd
I got it working, but I don't like the lack of type safety. I don't know why my C# PowerShell module won't load, but if I can figure it out, I'm scrapping this script and starting over in C#.
Probably would result in faster code.
Does PowerShell have problems with Module names that have periods,
., in them?
Also, does anyone have ideas on how to do a true native xcopy/xmove for PowerShell?
copy -recurse tends to flatten the structure.
Hi, anyone have any insight into why Invoke-RestMethod is behaving differently on my local PC vs on GitHub Actions?
$nugetServer = "https://api.nuget.org/v3-flatcontainer/PrettyPrompt/index.json"
$publishedversions = (Invoke-RestMethod -Method Get -Uri $nugetServer -Verbose).versionsOn my local machine, that call works (HTTP 200); but on GitHub Actions, nuget.org returns an HTTP 404. Is there some sort of environment difference that Invoke-RestMethod uses beyond what I specify at the command line? The only thing I can find is that Invoke-RestMethod respects proxy configuration via environment variables, but I don't think proxies are configured in GitHub Actions.
The failing job with more output is here: https://github.com/waf/PrettyPrompt/runs/7305443603?check_suite_focus=true
3 replies
Does PS 7 come with Powershell wrappers for
dotnet.exe?
Not sure, but I think you can add argument completion for the dotnet tool to your
$PROFILE:## Add argument completer for the dotnet CLI tool
$scriptblock = {
param($wordToComplete, $commandAst, $cursorPosition)
dotnet complete --position $cursorPosition $commandAst.ToString() |
ForEach-Object {
[System.Management.Automation.CompletionResult]::new($_, $_, 'ParameterValue', $_)
}
}
Register-ArgumentCompleter -Native -CommandName dotnet -ScriptBlock $scriptblock
Have not tried this for myself yet though, caveat emptor
Hello folks,
I'm new here, and am looking to make my first contribution to the repo.
I'm having trouble building master at the moment, and was wondering if anyone might be able to point me in the right direction here.
TIA.
I'm new here, and am looking to make my first contribution to the repo.
I'm having trouble building master at the moment, and was wondering if anyone might be able to point me in the right direction here.
TIA.
Also, it'd help if the
ArgumentCompletions attribute could take a collection of strings rather than requiring a comma delimited list.
In my case, I have a collection generated at runtime. Using
[ArgumentCompleter] instead looks like a pain. Something like [ArgumentCompletions($array)] makes more sense.
When I create a class with the member shown below, Visual Studio Code promptly breaks it trying to wrap the code to fit on one line.
hidden $mapCommonTimeZones =
@{
'UTC' = [TimeZoneInfo]::UTC;
'PST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Pacific Standard Time') | Where-Object { $_.DisplayName -match '\(US \& Canada\)'})[0];
'MST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Mountain Standard Time'))[0];
'CST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Central Standard Time') | Where-Object { $_.DisplayName -match '\(US \& Canada\)'})[0];
'EST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Mountain Standard Time'))[0];
};
It transforms that into:
hidden $mapCommonTimeZones =
@{
'UTC' = [TimeZoneInfo]::UTC;
'PST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Pacific Standard Time') | Where-Object
{ $_.DisplayName -match '\(US \& Canada\)'
})[0];
'MST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Mountain Standard Time'))[0];
'CST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Central Standard Time') | Where-Object
{ $_.DisplayName -match '\(US \& Canada\)'
})[0];
'EST' = ([TimeZoneInfo]::FindSystemTimeZoneById('Mountain Standard Time'))[0];
};
Seems the line breaks it adds between
where-object and the script block for that where-object are illegal.
It doesn't do that for a constant outside a class.
With
-match, how do you tell it you want a Multi-Line match? https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_regular_expressions?view=powershell-7.2#anchors doesn't describe that.
Instead, it just links to a general .NET discussion that assumes you're working directly with those types.
Will Pittenger you can use the general .NET options directly in -match https://learn.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference#miscellaneous-constructs
it's the .NET regex engine after all, so everything that's documented there should also apply to powershell
it's the .NET regex engine after all, so everything that's documented there should also apply to powershell
> 'asef
>> bsef
>> csef' -match 'asef$'
False
> 'asef
>> bsef
>> csef' -match '(?m)asef$'
True
>