Community Call for Feb 20th, 2020

[SteveL-MSFT]

Please pre-populate topics/questions here. We'll also use this for the live chat.

Agenda:

• PowerShell 7 release update
• Secrets Management update
• PowerShellGet v3 update
• PSEditorServices/VSCode-Extension update
• Jupyter notebook support update
• PSReadLine 2.0 GA
• ForEach-Object -Parallel change for 7.1 (we won't cover this and will be discussed in an issue)

[ThomasNieto]

New RFC for formatting and type extension DSL to remove the need to use XML. #241

[Ayanmullick]

• Is the cmdlet auto-generation tool, Jeffrey was talking about, publicly accessible?
• Can it be used to auto-generate cmdlets from REST API's of other software vendors?
• Is there a video tutorial?

[Ayanmullick]

Could we see SQLCLI-like intellisense dropdowns for PowerShell in the Microsoft Terminal?
@DHowett-MSFT , from the Terminal PG, said it needs to be enabled by the PowerShell team like for SQLCLI ...

[iSazonov]

@Ayanmullick Please open issue in PowerShell repo to discuss SQLCLI-like intellisense

[iSazonov]

It would be nice to get new meta issue with Plan to next milestone. (Then link issues and projects with the plan). (It's okay if this public plan changes over time.)
Perhaps we could have Roadmap.md document also.
It'd help to consolidate community and MSFT team efforts.

My personal preferences:

• New file enumerator (for dir -Recurse). Will pull in March middle after vocation.
• Migrate Json cmdlets to new .Net Core 5 API
• Annotate nullable. We fix very often NREs.
• Since OmniSharp supports analyzers we could fix a lot of analyzer warnings. The analyzers were written to help validate the correctness and performance of .NET code.

[MaximoTrinidad]

First, I love the .NET Interactive/.NET PowerShell Notebook!!

Good Job!!

Here's my list:

1. Bug in 7.0.0-rc.2: Register-ScheduledJob ScriptBlock parameter doesn't work #11687(Bug in 7.0.0-rc.2: Register-ScheduledJob ScriptBlock parameter doesn't work PowerShell#11687)

What's the story about the PSScheduledJob module in PowerShell 7? Is it going to be fixed?

2. JEA - for Windows OS Only -> PowerShell 7 version.

3. Linux issue with pasting If-Else block into the terminal: Right-click paste should work mostly like Ctrl+v paste #579 (Right click paste should work mostly like Ctrl+v paste PSReadLine#579)

:)

[DarwinJS]

Just a quick question. GitLab.com now has Windows Shared Runners (https://about.gitlab.com/blog/2020/01/21/windows-shared-runner-beta/) the preinstalls include Chocolatey (https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/gcp/windows-containers/blob/master/cookbooks/preinstalled-software/README.md)

I am assuming the community would like to see PowerShell 6 / 7 on there as well? If so I can open an issue and advocate for the community.

[MaximoTrinidad]

Just an FYI.

I update my .NET Interactive to use PowerShell 7 RC 2 instead ot RC1 using:

dotnet tool update -g --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json" Microsoft.dotnet-interactive

It did works in Jupyter PowerShell Notebook showing RC2. But, when using Windows Terminal, it didn't update the entry to use RC 1.

:(

[ThomasNieto]

We talked in the December community call #238 (comment) being unable to update from prerelease binary modules to stable. Anyone who has PSReadline 2.0 prerelease will not be able to update to stable.

[essentialexch]

We talked in the December community call #238 (comment) being unable to update from prerelease binary modules to stable. Anyone who has PSReadline 2.0 prerelease will not be able to update to stable.

It took extra steps, but I was able to update. There was a thread with Steve on Twitter where we went through it.

[ThomasNieto]

We talked in the December community call #238 (comment) being unable to update from prerelease binary modules to stable. Anyone who has PSReadline 2.0 prerelease will not be able to update to stable.

It took extra steps, but I was able to update. There was a thread with Steve on Twitter where we went through it.

Do you have the link?

The extra steps could be avoided if they release a small bug fix release 2.0.1.

[ili101]

Lest week I worked with a colleague that is used to ISE, I convinced him to use the VSCode preview extension.
I needed to explain to him that the text in the terminal is being written on top of other text is a known bug.
And not to trash the terminal because VSCode will crash because of a known bug.
And that F8 sometimes not working is a known bug.
And that the intelligence sometimes get stuck and that weird stuff like terminal line disappearing and console color changes unexpectedly is not uncommon.
And that the last version causes your code to run slowly (Don't know if was reported by someone already, if not I will open an issue)

In short he was not impressed by the experience...

[SteveL-MSFT]

@Ayanmullick see https://github.com/Azure/AutoRest for cmdlet generation

[rkeithhill]

Nice work on the cmdlet/module history. It would be nice to have a similar page for language changes (operator additions). Ditto for having PSSA detect these as well.

[vexx32]

@ili101 would love to chat in detail about what you're seeing; might be a good idea to catch myself or one of the folks working with the VS Code extension on the PowerShell Slack/Discord #vscode channel 🙂

[daxian-dbw]

@Ayanmullick Please open issue in PowerShell repo to discuss SQLCLI-like intellisense

@Ayanmullick Can you please open the issue in the PSReadLine repo instead? Thanks!

[ThomasNieto]

On the formatting and type extension DSL. I have a working prototype with the formatting keywords. I hope to release it publicly after getting some more feedback.

[essentialexch]

We talked in the December community call #238 (comment) being unable to update from prerelease binary modules to stable. Anyone who has PSReadline 2.0 prerelease will not be able to update to stable.

It took extra steps, but I was able to update. There was a thread with Steve on Twitter where we went through it.

Do you have the link?

The extra steps could be avoided if they release a small bug fix release 2.0.1.

https://twitter.com/Steve_MSFT/status/1217142622411603970

[rjmholt]

Migrate Json cmdlets to new .Net Core 5 API

I think there's concern that changing the underlying JSON library for those cmdlets may change some behavioural cases for JSON, and given the importance of those cmdlets in web contexts, creating a list of small differences that we can't fix easily (because it occurs in code that isn't ours) is risky.

But, I think there's a good case to use the JSON library in .NET for things like the configuration JSON and other in-engine JSON functions.

[MaximoTrinidad]

You all Rule guys!!

BTW including the Graph feature in .NET Notebook could be a winner.

Yes!! Plotting.
:)

[Ayanmullick]

@Ayanmullick Please open issue in PowerShell repo to discuss SQLCLI-like intellisense

@Ayanmullick Can you please open the issue in the PSReadLine repo instead? Thanks!

@daxian-dbw , @iSazonov , Submitted PowerShell/PSReadLine#1362

[iSazonov]

I think there's concern that changing the underlying JSON library for those cmdlets may change some behavioural cases for JSON, and given the importance of those cmdlets in web contexts

@rjmholt I expect that with .Net Core 5.0 many web services and applications (including Azure!) will migrate from NewtonSoft API to new API and in any case we will catch compatibility issues and we will have to think how resolve this. .Net Core 5.0 have a compatibility mode for this (auto switch to NewtonSoft API). Today I don't know that is best way for PowerShell but I an sure that we must start as soon as possible in order to get feedback early.

[jzabroski]

Just looking through these old notes... I'm not sure I understand something. I thought dotnet-try was a C# thing. What does it got to do with PowerShell? Also, what is the Graph feature of Jupyter PowerShell notebooks? Thanks!