I suggest you ...

Open links in an actual browser

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/351021/open-links-in-an-actual-browser.html
Please take the Web Browser out of the Visual Studio, open links in the default web browser (and please my own default, not Internet Explorer). Visual Studio is not good as a web browser and it uses Internet Explorer inside to make it worse.

1,407 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Michel Pavan Macedo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

36 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • BR commented  ·   ·  Flag as inappropriate

    Why is VS having just about everything imaginable built into it?
    It should have little besides
    - Solution/Proiject management - add/remove projects, add remove files, add directory, move file from directory to another
    - Code edtor
    - output window, find window, locals widnows quick watch,
    - debugger
    - edit project settings
    - Create new solution

    -There's dozens of UI screens in VS which do not fit into those categories and must add 50% bloat to VS and make it unmaintainable.

    E.g., designer tools for winforms should be moved out to winforms designer separate executable

  • HFC commented  ·   ·  Flag as inappropriate

    An interesting note; I'm using Visual Studio 6 (Win XP SP3) and it opens its links in my default browser. So this used to be the default behaviour.

  • RTIBobV commented  ·   ·  Flag as inappropriate

    GitHub is stating "Please note that GitHub will stop supporting Internet Explorer as of July 2018" every time that the internal browser is activated.

  • Michael T. commented  ·   ·  Flag as inappropriate

    The behavior of Visual Studio 2017's internal browser is quite different than a stand-alone version of Edge or IE 11. The differences are subtle in some cases, but glaring in others (e.g. how the internal VS browser handles background images).

    For this reason, I can never trust the internal browser and I would rather have the behavior be for it to open in a separate, stand-alone browser.

  • Yann commented  ·   ·  Flag as inappropriate

    Allison, I definitely would NOT like to see the internal browser capability taken out of Visual Studio! However I do think there absolutely should be a choice to open links internally or externally (in the user's default browser).

    I actually rely on the internal browser capability a LOT. Mostly for VSTS and GitHub pages, but essentially so I don't have to change contexts to view related information. I work in Visual Studio, and I want to be able to view certain pages IN the context of Visual Studio. I'm certainly not saying that I want to do ALL of my browsing in Visual STudio though, just information related to what I'm working on.

    That said, the internal browser needs to be updated, as both VSTS and GitHub complain that they don't support the current internal browser, and that we should consider upgrading to a more modern browser. It would be fantastic if the internal browser windows could open pages internally using the user's default browser. The best of both worlds.

    It's paramount however that users have the CHOICE to do what they need. For example I wouldn't want my request to overshadow what Michel is asking for, any more that I want his desire to remove the internal web browser capability to overshadow my needs.

  • Eli Arbel commented  ·   ·  Flag as inappropriate

    It would be great if this works for URLs opened by project templates as well (during project creation). Opening that browser tabs often causes delays.

  • Zev Spitz commented  ·   ·  Flag as inappropriate

    Even if you implement this, there is still a place for an embedded browser -- when VS is in full screen mode, and you want to have a browser open next to the code. That said, the embedded browser should still use something more up-to-date, like the Edge engine.

  • Karlan commented  ·   ·  Flag as inappropriate

    Oh my god please do this. Every time I click a link and it opens in VS's ****** browser I die a little inside.

  • Matthew Bonner commented  ·   ·  Flag as inappropriate

    It is even worse when you call dte.ItemOperations.Navigate(theUrl); only to find the Visual Studio debug browser settings, which someone has gone out their way to configure, are ignored! We don't want a new tab to open inside the IDE instead! Bonkers.

  • Adam J. Sycz commented  ·   ·  Flag as inappropriate

    Couldn't agree more. This is an unnecessary clutter let alone being forced to deal with the worst web browser known to man. I have a web browser of choice installed as my default one, please respect my wishes.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Sometimes the VS browser will say that a website is unavailable (e.g. nuget.org) but you can browse to that url just fine in another web browser.

    Removing the browser would hopefully fix the connection issues that sometimes happen with nuget.org or other extensions.

  • James Hood commented  ·   ·  Flag as inappropriate

    "We are currently evaluating whether we will be able to include this into the product." No, no, you need to exclude this from the product.

  • Edward Brey commented  ·   ·  Flag as inappropriate

    Hopefully the embarrassment factor is kicking in. If you create a new .NET Core web app, you get a bundleconfig.json file with this header:

    > More info at https://go.microsoft.com/fwlink/?LinkId=808241

    It takes you to a GitHub page that shows this banner: "Please note that GitHub no longer supports old versions of Internet Explorer. We recommend upgrading to the latest Internet Explorer, Google Chrome, or Firefox."

← Previous 1

Feedback and Knowledge Base