PowerShell | Collection of useful PowerShell functions scripts | Command Line Interface library

I'm trying to create a Windows form via Powershell and I need to capture the file path and store it in a variable. After the user clicks the 'Select' button and chooses the file, I would like to store the file path in a variable. Can someone please help me with this? The part of the code that shows the file path is the $selectButton.Add_Click() method.

I am attempting to run a cURL command in PowerShell using the Invoke-RestMethod cmdlet but it will not work properly.

It connects to the server and the API key is accepted. However, the credentials are not being passed correctly and I am receiving a response of

I wish to suggest (perhaps enforce, but I am not firm on the semantics yet) a particular format for the output of a PowerShell function.

about_Format.ps1xml (versioned for PowerShell 7.1) says this: 'Beginning in PowerShell 6, the default views are defined in PowerShell source code. The Format.ps1xml files from PowerShell 5.1 and earlier versions don't exist in PowerShell 6 and later versions.'. The article then goes on to explain how Format.ps1xml files can be used to change the display of objects, etc etc. This is not very explicit: 'don't exist' -ne 'cannot exist'...

This begs several questions:

1. Although they 'don't exist', can Format.ps1xml files be created/used in versions of PowerShell greater than 5.1?
2. Whether they can or not, is there some better practice for suggesting to PowerShell how a certain function should format returned data? Note that inherent in 'suggest' is that the pipeline nature of PowerShell's output must be preserved: the user must still be able to pipe the output of the function to Format-List or ForEach-Object etc..

For example, the Get-ADUser cmdlet returns objects formatted by Format-List. If I write a function called Search-ADUser that calls Get-ADUser internally and returns some of those objects, the output will also be formatted as a list. Piping the output to Format-Table before returning it does not satisfy my requirements, because the output will then not be treated as separate objects in a pipeline.

Example code:

I created an empty asp.net core web application (dotnet new web -n ) and went to the github for IdentityServer4.Quickstart.UI and was followed the instructions to add the quickstart UI. I first did the powershell cmd iex ((New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/IdentityServer/IdentityServer4.Quickstart.UI/main/getmain.ps1')) to download the files and run the application but it keeps telling me Index not found but the file is inside of the Views folder. So I then deleted all those files it downloaded from the project and installed it using its templates by running the cmds dotnet new -i identityserver4.templates then dotnet new is4ui --force which downloaded those files again onto my project. However, it keeps telling me the same message.

I noticed that under the Quickstart folder, contains a folder named Home which has the HomeController.cs and the namespace is as IdentityServerHost.Quickstart.UI... do I need to change that namespace to match my solution i.e. ids.Quickstart.Home?

What is causing this to display that error when infact there is the Index.cshtml file inside of the Views folder?**

This is my startup.cs file:

I wanted to get started with posh and oh-my-posh so I installed them according to this article. Microsoft docs. I got the theme but the edges didn't had that arrow(that coolness).

I then downloaded the windows terminal and edited the setting.json there with

This question is related to Azure MSIX Build and Package task only has Release and Debug configurations

We have a WinForms project that has an MSIX installer. Manually, we can successfully create

1. An MSIXBUNDLE and deploy it to Kudu
2. An MSIX and deploy it to an Azure VM through a VHDX. We have manually convert the MSIX to a VHDX first

We are now trying to automate the build and release process to create the VHDX. However, we are getting a blank screen when the VHDX is mounted using a process that we have already validated. The only thing different is the build method (i.e., MSBuild versus VS Publish).

How do we create a working VHDX in Azure CI Build Pipeline?

Below is the YAML.

I have the below powershell script:

I couldn't find this information on Microsoft's Docs for the Sort-Object cmdlet.

I am using Powershell's Sort-Object to sort objects based on a property, i.e.: $foo | Sort-Object -Property x in an Azure RunBook, what would be time complexity of this?

I want to read the output of below powershell script and split the output using space like this:

PowerShell script is here: