When I load my site, I get a "connection refused" to the browserLink URL. I've done the following steps to figure out what's wrong:
- Same project works fine on other machines
- The site itself works (on a different port)
- vs:EnableBrowserLink is absent from web.config
- Browser LInk is enabled
- debug is set to true
- The
<!-- Visual Studio Browser Link -->
portion is rendered in the page, thus confirming (even more so) that the browser link is enabled. - Read every article on how to use Browser Link - none detail what happens if the connection to the script is refused
- Same exact problem on all browsers
- Same exact problem on all web projects (I've tried several, even fresh 'vanilla' one)
- Restarting VS, computer, doesn't fix
- Running VS as admin doesn't fix
- Running in Safe Mode doesn't fix
- Disabling (and even uninstalling) all VS extensions doesn't work
- Running 'repair' on VS also does not work
- The port that it's attempting to reach (in my example,
27244
) does not show up at any of the IP addresses innetstat -aon
- To me this means it fails to start
- Firewall (even the corp one) is not blocking any of these ports
- Procmon and Procexplorer reveal nothing I can understand to be as to why VS is not starting the SignalR process(es).
- A brand-new project w/ SignalR from NuGet works fine - there must be something different on how VS uses it interally
None of these work, or reveal any more information as to why browserLink doesn't work - it's very interesting that the port isn't even listed in the netstat command. That tells me that something isn't started, failed to start, or started but isn't running...
Again, the same project (from source control) works perfectly fine on another developer's computer -- what could be wrong with my Visual Stuido?