Skip to content
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

How can I export a 'Browser Launch Target' to show up in the list of browsers to use for web app debugging #329

Open
aodl opened this issue Oct 1, 2019 · 2 comments

Comments

@aodl
Copy link

aodl commented Oct 1, 2019

Basically I would like to be able to programmatically add another browser to Visual Studio as an option for debugging a web app. Is this currently possible?

I'm not sure if 'Browser Launch Target' is the correct term, but I took a peek at Microsoft.WebTools.ProjectSystem.Debugger.WebDebugTargetsProvider decompiled source and they appeared to be referred to as browserLaunchTargets.

Ideally I would like to be able to bundle a simple console application 'browser' within a VSIX extension and use this as the default browser when debugging a web app. The purpose is so that I can automatically send an initial request to kick start an asp.net core application (sitting behind IIS) without the browser window appearing. I just want the web application to appear to start silently in the background (maybe there's a better way of accomplishing this).

@vbisbest
Copy link

Did you ever find a solution to this? I am looking for the same functionality. Thanks.

@aodl
Copy link
Author

aodl commented Mar 23, 2020

Hi @vbisbest , unfortunately not. I ended up putting this aspect of what I was doing on hold for now - although I'll be coming back to it soon. If exporting a custom browser option isn't feasible (it seems like it may not be an option), I may consider using the VS internal web browser option (and see if I can manipulate it programmatically from a VSIX).

I'll try and remember to update this ticket with what I find. I'm hoping there'll be some definitive feedback on this issue before then though :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants