Message "You are running the legacy version of PnP PowerShell"

[Tom-CK]

I am using legacy version of SharePoint PNP Online in many scripts, which I write for customers (none IT).
Since a while whenever I run the command "Connect-PNPOnline" there is a message "You are running the legacy version of PnP PowerShell". I know that I am using the legacy version !

Is there a way to avoid that message ? I get many tickets from customers because of this message .....

[erwinvanhunen]

We understand it's annoying, but we wanted to make it really clear that we like people to move over to the new version. We will do one more release (in a few days from now) of the legacy edition which will allow you to turn off this message by setting an environment variable. We realize we should have given that option from day one, but unfortunately it didn't make it into the release. Apologies for that.

[Tom-CK]

Okay, great !

Please make sure to do so in the new PnP.PowerShell-Module also.
Same problem there: Get-PnPConnection always throws an exception - no chance to swallow it ...

Do you have an idea of when the new release will be available ?

[ToddKlindt]

It's out. Version 3.29.2101.0 supports this. I just tested this and it worked.

[Tom-CK]

You guys are great, thank you !

I've just tested this, there is no more message "You are running ..." when running Get-PnPConnection.
But there is still an Error when no connection was establisehd, even when storing the result into a variable and when using -ErrorAction Silently continue.

When scripting, I do not want to use Connect-PnpOnline in every function call again. I us $con = Get-PnPConnection and then only call Connect-PnPOnline when $con is null. Now I get an error when doing this.
How can I test if a Connection is already established ?

[AndersRask]

As a general recommendation, I suggest replacing all Write-Host with Write-Warning/Write-Output depending on severity. Writing to host is something I would only consider doing in a one-off script or similar, but in a framework this should be avoided IMO

[AndersRask]

http://www.jsnover.com/blog/2013/12/07/write-host-considered-harmful/