Is there any way that I can get visual studio (2010 or other) to decide what browser to launch depending on the type of project I am working on? I prefer to use IE when I am developing Silverlight projects, and Chrome / Firefox / anything but IE when I am working on ASP.NET projects. Of course manually setting my default browser is always an option depending on what I am doing, but I feel like VS2010 should be smart enough to handle this for me. Any ideas?
You could use the WoVS Default Browser Switcher. Whilst it won't automatically detect the project type, it allows you to set the default browser in one click.
use this extension
It's pretty good.
Related
Switching from Visual Studio 2015 to 2017 I find that launching a Web API project now starts a clean, separate Chrome window. For the most part I like that, and I certainly like the idea, however: this also means extensions are missing in Chrome.
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Or, failing that, could I revert back to the old behavior where my project is opened as a fresh tab in my existing Chrome window?
I've tried Googling but found nothing. I checked the dropdown in Visual Studio with browsers (and checked the "Browse With..." dialog) but found no solution there either.
All you need to do is to sign-in to the instance of Chrome that VS2017 launches as the user you have all your usual extensions installed under (i.e. sign-in as the same user you usually sign-in as).
This sign-in "sticks", so extensions will load in the current - and all subsequent - debugging sessions.
You can revert back to the old behavior by
Debug > Options > Debugging > General > (uncheck) Enable JavaScript debugging for ASP.Net (Chrome and IE).
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Yes, but it works for one project only, mean you need to re-install extensions when you launch a brand new project. I tried Sync in Chrome (not work).
In my opinion, there are something to do with Chrome remote debugging protocol profile. I hope someone knows about Chrome can give a final solution for this.
you can study more here: remote debugging protocol
There is a way that you no need to change anything. But it annoying.
Because Visual Studio 2017 use an instance of Chrome for debug mode when you hit F5, so you can leave that debug mode instance with remote debugging protocol open, and use your default Chrome instance with full extensions. Just copy and paste the link into your favorite Chrome instance.
Cheer! hope it help.
I have a really weird problem, be interested in some pointers
We have a website that we have coded from Visual Studio 2003 -> Visual Studio 2010. We are now looking at moving to 2013.
The website is in IIS, when I navigate to it using IE it works. When VS2013 is -open-, not running, but has the project open we get a weird effect where the contents of the website gets duplicated by 3, its as if there are 3 iframes on the page, all with a copy of the same web site.
I close VS2013 and it goes back to normal
So, just to be clear, we don't even have to run the web site from within VS2013, just the project being open is enough to cause the weird effect
We use subversion as as far as I can tell no files have been modified when VS2013 is open
Any suggestions?
Thanks
It's Browser Link that's doing it! If you switch off Browser Link it works.
The source shows some extra script entries before the final tag but other than that the whole source is duplicated.
We don't need Browser Link and I don't have reflection capabilities on Asp.Net source so as to why that's for some one else to determine, I noticed a few people complaining when I searched on it so it may be something that just gets fixed in a future version
Can we now debug websites / services and set break points while using Google Chrome as the browser ? Or is this still only supportable in IE ?
I know before setting breakpoints (F9) and then debugging in IE worked without problems but using chrome was never supported.
I have tried to use google to find the answer to this but I am still unable to confirm it, I can't believe that debugging on services / sites are still not support in VS via another browser apart from IE.
I know the VS 2013 is upcoming, maybe this will address the problem?
EDIT
Sorry i should have made it clear, i am talking about client side debugging directly in VS using a NON IE Browser
You are misunderstanding client and server-side.
Client-side:
We don't care if the website is developed in .Net, with Visual Studio, PHP or whatever you want, the browser gives you some tools for debugging websites so the problem is from the browser not Visual Studio. Even if you upgrade to VS 2013 that won't change your problem, Visual Studio has no way to know the state of the JavaScript for a page opened by a client for example.
You may have heard about SignalR used in VS 2013 (Browser link feature) and that may have confused you, if so SignalR is only for refreshing client-side pages when you edit the view for example, but not for debugging.
Server-side:
Add your breakpoint in Visual Studio and then attach the debugger (Tools > Attach to process). In that way you will be able to debug server-side code (e.g. C# code) in Visual Studio. Note that the browser has no way to know the code server-side.
Suddenly today Visual Web Developer does not allow me to debug Silverlight applications.
This happens in 2008 and 2010 versions.
It gives no error message, just ignores all break points.
It can still debug ASP.NET applications.
Is anyone else experiencing this?
Added:
Interesting: debugging works in Internet Explorer but not in Firefox. Also on a new installation on a second computer it debugs in both IE and FF. Just noticed that that FF browser is still version 3.6.3.
I cleared everything in Firefox (3.6.4) but it still doesn't debug in that browser (on two computers):
alt text http://www.deviantsart.com/upload/l46lcc.png
While uninstalling the Silverlight plugin I saw this:
alt text http://www.deviantsart.com/upload/1i7j8ao.png
Check this link:
http://forums.silverlight.net/forums/t/188434.aspx
The solution seems to be:
Regarding the debugging: I think it
would be possible to write a VS plugin
or similar to attach to the
plugin-container.exe process
automatically, however there's a
simpler solution. You can disable the
new isolation feature in Firefox:
Type "about:config" into FF's address
bar Accept the warning (if applicable)
Search for the entry
"dom.ipc.plugins.enabled.npctrl.dll"
Change its value from "true" to
"false" (double-click) Restart the
browser
Mine seems to work fine in both VS2008 and 2010...
Would like to know if there is a setting anywhere which causes debugging to automatically stop when IE closes, and also if there is a way for this to work the other way around and IE to close if debugging stops.
I know that this works when the project type I'm working on is a 'Web Application', I'd like to know if the same functionality exists when working on a 'Web Site'
Thanks all.
This should be the default behavior of visual studio. i.e. , if you create a default asp.net website, and F5, then after you quit IE, VS automaticallly stops debugging. it doesn't work for aother browsers since these browsers don't have corresponding interface with VS.