Problem Description
------------------
If you are using the `using module` statement, it will load the module without any issues. However, if you make a change to the module and run the `using module` statement again without restarting your PowerShell session, it will not load the new modified module into memory, and instead will continue to use the old existing module that was loaded. This makes doing development with `using module` statements very tedious as you must continually reload your PowerShell session whenever you make changes to the module.

Ideally we would just use `Import-Module -Name [module name] -Force` to avoid this issue, but that does not work for importing `class`es, so the `using module` statement **must** be used.

Steps to reproduce
------------------
Create the following module and script files:

In `TestModule.psm1`:
```powershell
class TestClass
{
[string] $ClassPropertyText = "Initial text"
}

function Get-ModuleFunctionText()
{
return "Initial text"
}

Export-ModuleMember -Function Get-ModuleFunctionText
```

In `Test.ps1`:
```powershell
using module '.\TestModule.psm1'

$instance = [TestClass]::new()
$instance.ClassPropertyText

Get-ModuleFunctionText
```

Run `Test.ps1` and it will output:
```
Initial text
Initial text
```

Then modify `TestModule.psm1` to:
```powershell
class TestClass
{
[string] $ClassPropertyText = "Updated text"
}

function Get-ModuleFunctionText()
{
return "Updated text"
}

Export-ModuleMember -Function Get-ModuleFunctionText
```

Run `Test.ps1` again and it will still output:
```
Initial text
Initial text
```

Expected behavior
-----------------
When running `Test.ps1` the 2nd time, it should output:
```none
Updated text
Updated text
```

Environment data
----------------

<!-- provide the output of $PSVersionTable -->

```powershell
> $PSVersionTable
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 Info
----------------
The problem can be somewhat reduced by using _both_ the `using module` statement and `Import-Module -Force` statement, like this:
```powershell
using module '.\TestModule.psm1'
Import-Module -Name '.\TestModule.psm1' -Force

$instance = [TestClass]::new()
$instance.ClassPropertyText

Get-ModuleFunctionText
```

This code would result in the following output:
```
Initial text
Updated text
```

So here the module code was updated, but the `class` code was not.

Proposed Solution
----------------
To fix this issue I propose adding a `-Force` flag to the `using module` statement that forces the module to be reloaded into memory; the same way that the `-Force` flag works for the `Import-Module` cmdlet. This will allow developing code that uses the `class` construct to work much smoother.

I also proposed this same change to PowerShell Core at: https://github.com/PowerShell/PowerShell/issues/7654

Example:

$Get-Process | select -First 5 | ft -au

Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
716 47 32832 43396 587 1764 AdminManagerClient
257 34 3432 9352 84 1128 AgentService
495 78 15700 28528 154 3744 AppVClient
244 35 60952 41796 692 0.56 5416 AppVStreamingUX
591 18 17280 22992 108 1,751.98 4672 audiodg

$Get-Process | select -First 5 | ft -markdown

|Handles|NPM(K)|PM(K)|WS(K)|VM(M)| CPU(s)| Id|ProcessName |
|-------|------|-----|-----|-----|--------|----|------------------|
| 716| 47|32832|43396| 587| |1764|AdminManagerClient|
| 257| 34| 3432| 9352| 84| |1128|AgentService |
| 495| 78|15700|28528| 154| |3744|AppVClient |
| 244| 35|60952|41796| 692| 0.56|5416|AppVStreamingUX |
| 591| 18|17280|22992| 108|1,751.98|4672|audiodg |

This could be pasted to a morkdown file and would be nicely rendered as a table.

The Other way to read tables from markdown woulb de nice to. It would require a syntax for naming tables and referencing them in markdown. It would allow very readable configuration files.

(Sorry here is no monospace font available)

Votes from Connect: 10

Original Date Submitted: 12/10/2011 12:21:15 AM

Description:
********Contact Information********
Handle: JoshGav
Site Name: PowerShell
Feedback ID: 712796
***************************************

Frequency: Always Happens
Regression: Yes, this happens in previous released versions

Problem Description:
The final delimiter in a here-string is defined as newline-quotemarks-atsign. This means that the "@ has to be at the beginning of the final line, with no whitespace preceding it. This ruins attempts at tab indentation in scripts and functions. Whitespace should be allowed as part of the ending pattern between the newline and quotemarks so that tab indentation can be cleanly utilized.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 712796 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=712796).

Repro Steps:
If a here-string is typed as follows:
$str = @"
a string
"@
it will not be evaluated properly.

Expected Results:
Allow the previously indicated string as a here-string, ignoring the extra whitespace between the final newline and ".

Internal BugId: 3186

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

Hi Team,

I am using powershell to trigger commands on remote machine (as this doesn't require anything additional package to install). Recently I am facing issues with running commands on remote machine.

$ComputerName = "***.***.***.***"

Function ExecuteCommand() {
Get-PSDrive
}

Set-Item WSMan:\localhost\Client\Trustedhosts -Value $ComputerName -Concatenate -Force

$Credentials = Import-Clixml $CredentialsFile

Invoke-Command -ComputerName $ComputerName -Credential $Credentials -ScriptBlock ${function:ExecuteCommand} -HideComputerName

I am storing the credentials in the file and using the above script to run commands on remote machine.

1. Get-PSDrive doesn't return mapped network drive details.
2. using net use command to map network path. Network path gets mapped successfully but the status of the mapped network path is unavailable. This was working properly around 1 and half month ago but not sure what changed in past 1 and half month.

I am using
OS: Windows Server 2012 r2
Powershell 4.0
PSRemotingProtocolVersion 2.2

Can someone please help here?

Thanks.

The following script demonstrates an issue I'm experiencing after moving from PowerShell v4 to v5.1. I make extensive use of Start-Process redirecting StandardError to a file, if this file contains data after execution I can read the file to see what the issue was.

However, with v5.1 when the launched PowerShell process starts, it makes use of progress output which is on the error stream, so this is redirected to the error file.

In previous versions of PowerShell this did not happen.

The output to the script below is as follows:

Powershell v4
------------------
WARNING: Standard Error
WARNING: Standard Out
hello world!

Powershell v5.1
---------------------
WARNING: Standard Error

SourceId Record
-------- ------
1 parent = -1 id = 0 act = Preparing modules for first use. stat = cur = pct = -1 sec = -1 type = Completed
hello world!

WARNING: Standard Out
hello world!

# ------------------------------------- Script Start

$outfile = [System.IO.Path]::GetTempFileName()
$errorfile = [System.IO.Path]::GetTempFileName()

$command = "write-host 'hello world!'"
$encodedCommand = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($command))
$argumentList = @(
"-NoLogo",
"-NonInteractive",
"-NoProfile",
"-EncodedCommand",
$encodedCommand
)

Start-Process powershell `
-argumentlist $argumentList `
-PassThru `
-wait `
-RedirectStandardOut $outfile `
-NoNewWindow `
-RedirectStandardError $errorfile | Out-Null

Write-Warning "Standard Error"
try {
Import-Clixml $errorfile | Out-Host
}
catch {
Get-Content $errorfile
}

Write-Warning "Standard Out"
Get-Content $outfile

$outfile, $errorfile | Remove-item

Three folders; d1, d2, d3, with files test.txt and test.mp3 in in d1 and d3.

'-Include *d1*' includes only content from d1. Would expect '-Exclude *d1*' to include the inverse, but it has no effect, it returns all data.

unless it's run after -Include.

So '-Include *d1* -Exclude *d1*' returns nothing, as expected.

Exclude only works as it applies to a file name, not a path.

So '-Exclude *.txt' will exclude all files '*.txt' as expected.

The syntax usage in the help file is identical for both parameters.

Please fix -Exclude parameter so that it works on the Path consistently, as the documentation states it should.