Add the ability to make SOAP calls which originally was done using New-WebServiceProxy.

SOAP services are still common in both small companies and large enterprise where some products only have this method of integration. Many legacy systems both purchased and built in house use SOAP and will continue to for a significant time as the cost of upgrading is either too great, does not make commercial sense or simply impossible.

I have only just started to look at PowerShell 6 and this is a complete road block for using it at this time. If there are alternative options without having to use HttpClient and build the full messages which can be very complex, please let me know.

When attempting to add a TXT DNS record via the "Add-DnsServerResourceRecord" command, the DescriptiveText property only accepts strings up to 254 characters but should support up to 255 characters. Ideally the command should accept an array for the DescriptiveText so that multiple lines of up to 255 characters can be passed through. Currently it requires using `r`n to insert a line break but over all must still be under 254 characters. This is an issue as we are trying to implement automation around TXT records and DKIM records tend to be well over this 254 character limit and require multiple lines.

PS > type .\error.ps1
[Cmdletbinding()]
param()

"hello"
"world"

1/0

PS > .\error.ps1
hello
world
Attempted to divide by zero.
At D:\junk\error.ps1:10 char:5
+ 1/0
+ ~~~
+ CategoryInfo : NotSpecified: (:) [], RuntimeException
+ FullyQualifiedErrorId : RuntimeException

PS > $ErrorActionPreference = "Stop"
PS > .\error.ps1
hello
world
D:\junk\error.ps1 : Attempted to divide by zero.
At line:1 char:1
+ .\error.ps1
+ ~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [error.ps1], RuntimeException
+ FullyQualifiedErrorId : RuntimeException,error.ps1

Note incorrect line number being reported on second invocation when ErrorActionPreference equals "Stop"

This can also be reproduced by putting "$ErrorActionPreference = "Stop" at line 3 of the script.

I always set ErrorActionPreference to Stop at the start of my scripts, and also have ErrorActionPreference set to "Stop" always in my environment for improved robustness as I write scripts, As a result this issue is very problematic. The correct line number can be obtained by digging into $Error but that is a pain.

This started happening somewhere around the v5 release. Prior to that the correct line number was always reported. This can also be reproduced by using -ErrorAction Stop at a particular invocation, although that is a less compelling scenario.

PSVersion 5.1.18272.1000

Sorry if this is the wrong place, I created an issue https://github.com/chef/chef/issues/7765 but I am not sure its an issue with Chef.
I have also created an issue https://github.com/PowerShell/PowerShell/issues/8148 .
I am not very familiar with Powershell sorry, so I am unable to replicate without Chef (If I knew how it would be handy to try and replicate with pure WinRM).

Steps to reproduce
------------------
In Chef
```powershell
cd C:/Test
Add-AppxPackage Example_1.0.0.0_x64.appx -DependencyPath "Dependencies\\x64\\A.appx","Dependencies\\x64\\B.appx","Dependencies\\x64\\C.appx"
```
This is trying to install an appx for a standard user. I believe Chef uses WinRM to run the commands.

Expected behavior
-----------------
```
App installs. Testing the command when physically logging in as the standard user and running powershell, it does work (appx installs).
```
```powershell
get-appxpackage -allusers -name *example*
(result is empty)
```

Actual behavior
---------------
```
Win32 internal error "Access is denied" 0x5 occurred while reading the console output buffer. Contact Microsoft Customer Support Services.
```

Environment data
----------------
```powershell
Name Value
---- -----
PSVersion 5.1.17134.228
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17134.228
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
```

Additional Notes
----------------
I have tried everything I can think of, the only thing that works is starting another powershell script as the user (see the ticket on Chef). Please see https://github.com/chef/chef/issues/7765 for more details.

Hi All,

I've searched for this, but I don't believe it's currently possible:

I'd like the ability to mark a line or lines of code for review later on and an ability to filter my script to show only marked lines and an ability to quick jump to marked lines.

To give a scenario: We have a number of PS scripts in the 1000+ line region for configuration of various Applications. As we move from one version of said application to another, we review the PS script - modifying it to meet current business requirements or changing work-around scripts to vendor-supported solutions provided in the latest release.

In this scenario, it would be nice to mark all the lines where either our business requirements have changed or where the vendor has deprecated a feature or added a new way of doing things so that these keen easily be identified after the review has occurred and fixed.

Thanks

> dismount-vhd -disknumber X

This command is only observed to work on my machine if the path to the vhd does not have a space in it.

For example:
> mount-vhd -path C:\User\No\Spaces\In\Path\win10.vhd
> # do stuff, check diskpart which shows mount index is 1
> dismount-vhd -disknumber 1
> # Success!
> mount-vhd -path "C:\Bad User\Who Likes\Spaces\Win 10.vhd"
> # do stuff, check diskpart which shows mount index is 1
> dismount-vhd -disknumber 1
> # AG! NO!! Fails...
> "Windows cannot find a mounted virtual hard disk with the specified disk number"
> # Also, diskpart still shows vhd mounted at index 1...

Note: you CAN use dismount-vhd -path "path" in this situation and it does work, so rest assured you aren't completely screwed. But this did take about 2 hours of my day working through a script that had been great in the past but was proving rather difficult with this afternoon's invocation of said script.

Issue:
In order to obtain the Exit Code from a Process we are executing the Start-Process cmdlet with the following parameters:
-PassThru -Wait -WindowStyle Hidden
or
-PassThru -Wait -NoNewWindow

In rare cases, this leads to the following exception:
System.Management.Automation.CmdletInvocationException: Cannot process request because the process (<ProcessIdHere>) has exited. ---> System.InvalidOperationException: Cannot process request because the process (<ProcessIdHere>) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle(Int32 access)
at System.Diagnostics.Process.get_Handle()

After the Exception occurred, the returned Object does not contain a Handle nor Exit Code but the executable itself executed without issue.

We also tried to remove the “-Wait” Parameter and use the $process.WaitForExit() Method without success (as proposed here: https://stackoverflow.com/questions/44057728/start-process-system-diagnostics-process-exitcode-is-null-with-nonewwindow and https://stackoverflow.com/questions/10262231/obtaining-exitcode-using-start-process-and-waitforexit-instead-of-wait).

This happens on Windows 7 and Windows 10 Clients.
When the issue occurs, it is mostly when running small and low footprint executables like reg.exe.

Possible Cause:
This error is probably caused by the fact, that the process which was opened by Start-Process has already finished (and thereby is already killed) when Start-Process tries to get the handle.

Example:
$process = Start-Process -PassThru -Wait -NoNewWindow -FilePath “C:\Windows\System32\reg.exe” -ArgumentList “import C:\temp\dummy.reg”

1. Start-Process executes “reg.exe”
2. “reg.exe” terminates, before Start-Process is able to get the handle (get_Handle Method)
3. Start-Process throws a System.InvalidOperationException Exception

PowerShell Environment:
PSVersion 5.1.16299.666

Is it possible to fix the behavior of Start-Process in order to get consistent results?