-
Notifications
You must be signed in to change notification settings - Fork 56
Support in-tool notification for version upgrade #396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| if (result != null && result.Count > 0) | ||
| { | ||
| output.AddRange(result); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check $LASTEXITCODE before adding result to output, here is an example.
src/Common/IFrequencyService.cs
Outdated
| /// Adds the specified feature to the service's per-PSsession registry. | ||
| /// </summary> | ||
| /// <param name="featureName">The name of the feature to add.</param> | ||
| void AddSession(string featureName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Add maybe more clear. Also I'm curious whether if we want to support other frequency such as every 30 execution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not in the scope for now. But it could be added later.
This PR will prompt a warning message to the user if local Azure PowerShell module versions are not the latest.
Refer to the design spec for details.
It'll work together with Azure/azure-powershell#22338.
The warning message examples:

