visual studio 2017 debug unable to start program Invalid pointer
Asked Answered
C

3

9

Debugging an ASP.NET MVC application with the default Chrome browser was working fine. I switched the debug over to start up IE instead to do some additional testing and the debugging worked fine. After I was done with IE I switched back to Chrome and now I get this error. If I switch back to IE I also get this error. I have closed and re-opened solution. I have closed and reopened VS. I have run VS with logging and I get no errors in the Activity Log. I can successfully debug if I turn off "Enable JavaScript debugging for ASP.NET" in the debugging options, but it was working fine with that option earlier. Any suggestions?

Cynical answered 22/3, 2017 at 21:58 Comment(5)
What`s the version of your Visual Studio 2017? Have you start Visual Studio 2017 as Administrator and try to create a new ASP.NET MVC application to verify this issue?Carcinomatosis
Version is 4.6.01586. I just created a new web project and attempted to debug and got the same error. Thanks for the help.Cynical
Thanks for you reply. We could not reproduce this issue, so it's hard to provide you an answer. Could you please try to repair or reinstall you VS? If it works fine?Carcinomatosis
Thank you for the suggestion. After the repair, browser link is working again in Chrome. I have not switched over to IE to try it yet.Cynical
@RichardWill.Net, maybe it was the VS setup issue, how about the result if you use the IE now? If it was resolved, you could post the comment as the answer. Have a nice day.Saidel
D
0

Unfortunately information on how the debugging emulator works is hard to come by. The only known solutions are...

  1. Reinstall Visual Studio
  2. Update Visual Studio if there is a patch/update available.

You can use a different browser or the internal browser.

Dorella answered 29/6, 2017 at 13:18 Comment(4)
Using Edge fixed it for me. Easy to test how it looks in others, once you get one browser up, just copy paste the url into other browsers.Marcellmarcella
@Marcellmarcella That is a workaround, not a fix. When you're nose is to the grindstone and you need to get the work done a workaround will do but it should really have a fix. Unfortunately reinstall/patch is currently the only known fix.Dorella
This is a workaround not a fix. Solution below by Ellix4u workedCineaste
@Cineaste This is not a workaround. The answer below is a workaround. You shouldn't have to disable a feature to get core functionality to work. Reinstalling is a pain but it was necessary in this case.Dorella
G
19

Go to Tools > Options > Debugging > General and turn off the setting for Enable JavaScript Debugging for ASP.NET (Chrome and IE).

Gheber answered 22/3, 2018 at 7:40 Comment(1)
@ElvinMammadov. share your error message here. Can i get the full screenshot/details of what you are try to do?Gheber
R
8

I have also encountered this issue on visual studio 2017 like below:

enter image description here

I have followed below step:

Go to Tools > Options > Debugging > General > Unchecked Enable JavaScript Debugging for ASP.NET (Chrome, Edge and IE).

enter image description here

Once I get rid of check box on Enable JavaScript Debugging for ASP.NET (Chrome, Edge and IE)

Then It works for me and Invalid Pointer error gone!

Romeu answered 16/12, 2019 at 14:29 Comment(0)
D
0

Unfortunately information on how the debugging emulator works is hard to come by. The only known solutions are...

  1. Reinstall Visual Studio
  2. Update Visual Studio if there is a patch/update available.

You can use a different browser or the internal browser.

Dorella answered 29/6, 2017 at 13:18 Comment(4)
Using Edge fixed it for me. Easy to test how it looks in others, once you get one browser up, just copy paste the url into other browsers.Marcellmarcella
@Marcellmarcella That is a workaround, not a fix. When you're nose is to the grindstone and you need to get the work done a workaround will do but it should really have a fix. Unfortunately reinstall/patch is currently the only known fix.Dorella
This is a workaround not a fix. Solution below by Ellix4u workedCineaste
@Cineaste This is not a workaround. The answer below is a workaround. You shouldn't have to disable a feature to get core functionality to work. Reinstalling is a pain but it was necessary in this case.Dorella

© 2022 - 2024 — McMap. All rights reserved.