You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can know PowerShell is great Scripting Language for Automation and Administration of system. and it is built by Microsoft, so I think it is very good for winget-cli to get compatible with PowerShell and make native PowerShell Cmdlet and make great integration with OneGet platform for provide a native and consistent user experience in Microsoft Ecosystem.
In this area we can see below command instead of Linux legacy CLI style like winget install foo
I think PowerShell has many guideline and documentation about writing and designing great Cmdlet and modules that winget-cli teams have to follow it for example
ITNOA
Description of the new feature/enhancement
As you can know PowerShell is great Scripting Language for Automation and Administration of system. and it is built by Microsoft, so I think it is very good for winget-cli to get compatible with PowerShell and make native PowerShell Cmdlet and make great integration with OneGet platform for provide a native and consistent user experience in Microsoft Ecosystem.
In this area we can see below command instead of Linux legacy CLI style like
winget install foo
Install-Package foo
Update-Package foo
Get-Package foo
And all of them is object and we can work with them in OOP area with modern and great and consistent experience in PowerShell World.
Proposed technical implementation details (optional)
I think PowerShell has many guideline and documentation about writing and designing great Cmdlet and modules that winget-cli teams have to follow it for example
Windows PowerShell Cmdlet Concepts
Writing a Windows PowerShell Module
PowerShell Script Module Design: Building Tools to Automate the Process
Powershell: DSL design patterns
The text was updated successfully, but these errors were encountered: