If you enable https within Visual Studio for your asp.net site (for example to test oauth logins) browser link's script injection injects a script line using the http protocol.
This causes mixed content warnings in secured browsers and won't run.
Browserlink should listen on https (borrowing the IIS Express cert for localhost), detecting the protocol on the request, and using https as appropriate.
If you enable https within Visual Studio for your asp.net site (for example to test oauth logins) browser link's script injection injects a script line using the http protocol.
This causes mixed content warnings in secured browsers and won't run.
Browserlink should listen on https (borrowing the IIS Express cert for localhost), detecting the protocol on the request, and using https as appropriate.