September 16th 2021 Community Call
SteveL-MSFT opened this issue · 11 comments
Agenda:
- PowerShell 7.2 RC [Steve]
- PowerShellGet v3 demo [Anam]
- VSCode-PowerShell updates [Andy]
- PowerShell Standard Library [Jim]
- FileUtility demo [Steve]
- Team update
Please pre-populate questions and also indicate if you have a PowerShell community demo to show!
What is the state and future of the PowerShell Standard Library?
The documentation published for writing a binary class library or binary module all point at using this library: (top 2 results from Bing)
- https://docs.microsoft.com/en-us/powershell/scripting/dev-cross-plat/create-standard-library-binary-module
- https://devblogs.microsoft.com/scripting/weekend-scripter-run-c-code-from-within-powershell/
If this is no longer the preferred or recommended method, at most, mark that StandardLibrary repo as archived and point folks to the right library to use.
Will there PowerShell be supported in Github Codespaces?
As of last week before I went on vacation,the PowerShell extension for VS Code was in particularly bad shape and has been for about two months. Is there a timeline for a short-term stability fix? Is there any version of a module on our end that we should be on? Any that version we should avoid?
How is the overall rewrite going? Do you know when there will be a beta that we can test?
Thanks,
Chrissy
As of last week before I went on vacation,the PowerShell extension for VS Code was in particularly bad shape and has been for about two months. Is there a timeline for a short-term stability fix? Is there any version of a module on our end that we should be on? Any that version we should avoid?
Can you elaborate on "particularly bad state?" We've been fixing issues left and right. Please open an issue and we'll see how we can help.
A new preview went out yesterday, and I'm planning to roll it into stable tomorrow.
How is the overall rewrite going? Do you know when there will be a beta that we can test?
I believe you mean the editor services pipeline project, and it is underway. It should be available in preview soon.
- FileUtility demo [Steve]
What is a purpose of development of the module? It is very strange to see base shell operations in separate module.
I hope for a long time that we will fix a lot of bugs in FileProvider, make it many times faster with the new .Net API, and improve the globbing and make it modern. I'm even willing to work on that. It's really depressing that these basic operations are so bad.
Hopefully I will have my work emergencies sorted this time for a Pester Vscode test adapter demo, now with fancy and even speedier new PS-to-nodejs adapter!
- It seems Dashboard is not updated last month
- What explains the rapid increase activity on Windows in July?
If this is no longer the preferred or recommended method, at most, mark that StandardLibrary repo as archived and point folks to the right library to use.
Here are the relevant articles:
- https://docs.microsoft.com/powershell/scripting/dev-cross-plat/choosing-the-right-nuget-package
- https://docs.microsoft.com/powershell/scripting/dev-cross-plat/create-standard-library-binary-module
- https://docs.microsoft.com/powershell/scripting/dev-cross-plat/writing-portable-modules
We will look to see if these need updating.
PowerShellGet team mentioned https://github.com/PowerShell/PowerShellGet/issues/479#issuecomment-916332649 that PoweShell will be adding semantic versioning support (module system) PowerShell/PowerShell#2983. Do you have more details and a timeframe? Without semver in the module system it causes major issues with prerelease versions. Lastly, how will PS 5.1 be handled if PSGetv3 is relying on enhancements in PowerShell 7.3+ https://github.com/PowerShell/PowerShellGet/issues/484?
@iSazonov regarding the PowerBI dashboard, it looks like the creds used to connect to the db expired. I've updated them and the next refresh is scheduled for tomorrow. So hopefully it'll be working again by this weekend.
@SteveL-MSFT Dashboard works again. Thanks!