madskristensen / browserlinkinspector2019 Goto Github PK

Installed product versions

• Visual Studio: 2019 (with comparative tests on VS2017)
• This extension: 0.5.3

Description

I've mentioned this issue on the 2017 version after the 2019 version came out, but the post went stale.

This tool that you've created is remarkable and INVALUABLE when it works (as it did perfectly in VS2017). However, V2019 is still having its problems. I thought that it was more appropriate to post the continuing issues on the current release issues page in great detail.

It's taken me many hours to figure out and document what I think is happening, so I hope that helps in quickly finding what might be wrong. I've examined my code in great detail in this process and find nothing that, given some of the parallel tests that follow, might be causing these issues.

In short, I maintain that there is still some kind of bug that exists in Browser Link Inspector 2019 (BLI) that results in the failure to highlight and synchronize the location of the code. This is NOT the situation in BLI 2017. It seems to me (NON-technically here) that BLI is somehow tripping over the synchronization when a domain changes (as in tests 1 and 2) or a simple directory change (as in test 3).

From my experience, BLI will only look and attempt to synchronize links on the level of the Project Url, which is totally understandable. BLI2017 does this perfectly; BLI2019 isn’t totally there yet.

The 2 projects tested and compared are MVC 5 .NET Framework 4.8. The same 2 projects tested results from VS2019/BLI2019 vs previous results from VS2017/BLI2017.

I sincerely hope that we can get a quick fix to this. I only wish I could be of more help in finding the problem in your code, but it may be a bit over my head. This has taken me a lot of time to try to track things down and I hope that it is helpful.

CURRENT vs PREVIOUS behavior tests

Test 1 – VS2019 RESULT: FAILURE

Steps:

1. VS2019 Professional, Project A. Project Url: https://m.example.com
2. Refresh page
3. Wait for BrowserLink Dashboard to clear 2nd Chrome Connection
4. Click Inspect Mode
5. Notice the page darkens with "+" crosshair ready to select element
6. Cursor moves around but does not "frame" element
7. Upon click on anywhere on the page, page lightens, crosshair cursor disappears and nothing happens
8. Repeat steps 5 through 8
9. RESULT: FAILURE

Test 2 – VS2017 Result: SUCCESS

Steps:

1. VS2017 Professional, Project A, Project Url: https://m.example.com
2. Refresh page
3. Wait for BrowserLink Dashboard to clear 2nd Chrome Connection
4. Click Inspect Mode
5. Notice the page darkens with "+" crosshair ready to select element
6. Cursor moves around, appropriately highlighting "frames" elements and finds corresponding in editor
7. Result: SUCCESS

Test 3 – VS2019 Result: Only Partial Success

Exhibit 3a: Success

Exhibit 3b: Success

Exhibit 3c: FAILED

Steps:

1. VS2019 Professional, Project B, Project Url: https://localhost:44350/
2. Exhibit 3a works as expected
3. Exhibit 3b works as expected
4. Exhibit 3c FAILS

Test 4 - VS2017 Result: Success

Exhibit 4: SUCCESS

Steps:

1. VS2019 Professional, Project B, Project Url: https://localhost:44350/
2. Similar to exhibit 3a, it worked as expected
3. Similar to exhibit 3a, it worked as expected
4. Exhibit 4 WORKS AS EXPECTED