[FEATURE] Check for Updates from behind a Proxy Server

[jamesrudolph]

Which component(s) does this affect?

• Desktop App
• CLI Tool
• SSMS Extension
• Plan Analysis Rules
• Documentation

Problem Statement

When attempting to "Check for Updates" when behind a proxy, the update fails with an error message:

Proposed Solution

1. Allow the user to enter proxy settings.
2. Wrap the text of the error message.
3. When the "Check for Updates" fails, open the user's browser to the current Release's page.

Use Case

I am too lazy to manually update the tool. This would allow me to remain lazy.

Alternatives Considered

Manually updating the tool :(

[erikdarlingdata]

Thanks for the report! Before building the proxy settings UI, I want to make sure I'm targeting the right thing for your setup. Two questions:

1. Is your proxy auto-discovered (WPAD/system) or do you have to configure it manually in apps?
If your browser "just works" without you typing in a proxy address, it's likely auto-discovered — in which case a small change (sending your Windows login credentials to the proxy automatically) would probably be enough on its own and would require no settings UI at all. This handles most AD-joined / NTLM / Negotiate corporate proxies.

2. If your proxy needs manual configuration, what does it require?

• Address and port only (no auth)?
• Address, port, username, password?
• Something else (PAC file URL, etc.)?

Asking because the cheapest fix solves a lot of corporate cases without a settings dialog, but if your proxy needs explicit credentials I'll build the full UI. Either way I'll also wrap the error text and add a "open releases page" fallback link, since those are useful regardless.