I'm using Visual Studio 2015 and Browser Link doesn't work with Firefox. IE and Chrome work perfectly with Browser Link.
- SpreadsheetGear 2010 for Windows. SpreadsheetGear 2010 is the leading Microsoft Excel compatible spreadsheet component for the Microsoft.NET Framework. Bit and 64 bit Windows 2000. Import Visual Studio / Visual Basic project files.
- Change Visual Studio 2010 Web Browser View to Firefox. I tried it out and it works as described. However, the new window is not dockable in Visual Studio as all other windows, which is what I am looking for. Please clean up your answer from the old text and i will give it a +1. Browse other questions tagged visual-studio-2010 firefox.
Keep your photos safe in the cloud with the best online photo storage for 2019 Stay private and protected with the best Firefox security extensions Clean out junk files in Windows 7, 8.1, and 10.
Just got a new machine, but that didn't help either.
I tried the prerequisites mentioned in the browserlink dashboard (for static files, enable debugging) and I use IIS express, so .NET 4.0 is there.
Are there any more settings needed in Firefox?
In the network view, I just don't receive a response from the server, 0 bytes transferred.
Network trace:
Erik OppedijkErik Oppedijk1 Answer
Found it, the main website was running on 44300, browserlink seems to run on 44399 (although that port isn't visible in IIS express)
Browse to https://localhost:44399 gave me the Firefox 'This Connection is Untrusted' screen, where I needed to trust('confirm security exception') the self signed IIS certificate (just like what I had done on the https://localhost:44300 site)
So it seems Firefox remembers trusted certificates per port number, not per DNS/IP/Name like IE and Chrome seem to do.
Now the browserlink is working and downloading the files.
Erik OppedijkErik OppedijkNot the answer you're looking for? Browse other questions tagged visual-studiofirefoxweb-essentials or ask your own question.
I have Visual Studio 2013 (tested with Update 1, 2 and 3) installed on two completely seperate machines, one is Windows 7 SP1 and one is Windows 8.1. Both are running the latest version of Firefox and Firefox is set to be the default browser. The Firefox setting 'Open tab instead of new window' is checked.
Almost every time I want to open the API help pages on MSDN by pressing F1 in the code, a new Firefox window is opened. This happens on both machines. But it only happens with Firefox, when IE is the default browser it correctly opens a new tab. And this is a new problem in Visual Studio 2013, I didn't have this problem with Visual Studio 2010.
Interestingly, this is not 100% consistent. Rarely, I'd say about 5% of the time, it correctly opens a new tab instead of a new window. And I have found one command that always correctly opens a tab, that is the Help - View Help command in the main menu bar (not very helpful).
Searching the internet revealed this Microsoft Connect issue entry which says that it was also a problem in Visual Studio 2012, but was apparently fixed in the latest build in May 2013. While I've never used Visual Studio 2012 myself, this date was before Visual Studio 2013 was released, and was far before Update 1 for it was released. Did they really forget to merge the fix to Visual Studio 2013?
Visual Studio 6.0 Windows 7
Anyway, my question is if everyone experiences this problem and if not, if anyone knows a way to fix it.
Update with workaround
I've no idea how or why this works, but I've found a workaround. As long as the .NET Reflector (I'm using version 8.3.3.115) is running, the F1 key works correctly. This is 100% reproduceable and works on Windows 7 and Windows 8.1.
Can someone please explain that to me?
Install Visual Studio 2010 On Windows 10
I'll leave this question open until a real answer is found.
Update 2
Visual Studio 2015 shows the same problem.
Visual Studios For Windows 7
2 Answers
The problem is that Visual Studio launches Firefox with incorrect parameters. The correct settings can be found in the registry (HKEY_CLASSES_ROOTFirefoxURLshellopencommand
). Now, to fix this, simply add Firefox as a web browser (with the correct startup parameters: -osint -url '%1'
) and assign it to the default.
I don't know when this was fixed, but it doesn't happen with Visual Studio 2017 on Windows 10.
cremorcremor