support.DEVSENSE.com

Hi,

Could you please tell me more about your VS instances?

I was trying to replicate at:
VS Enteprise 15.8.7 with just PHP Tools.

I've tried all types of projects, with or without Git source control.

Does it happen to you on empty project? Or it requires certain files/packages to be included in the project?

Thanks,

Hi guys,

We think we've fixed the issue. Could you please try the latest preview and let us know? https://www.devsense.com/en/download

Thank you

Could you please tell me more about your VS instances?

I'm running VS Professional 15.8.7. I was running the previous version when this problem occurred and so updated VS to this version.

I've tried all types of projects, with or without Git source control.

I'm running Git. And I think this is where the trouble started. I did a git rebase in Team Explorer with some merges. They all went smoothly until I swapped from taking target to taking source. It then reported an exception had occurred. After that the Continue button was greyed out, but on clicking Changes it continued but with the same exception. So I closed VS down and aborted the rebase. When I went back into VS it just hung and could only be shut down with Task Manager. I also pulled the solution to make sure the project was up to date - and it was.

I tried VS 2015 and it actually loaded the solution although one of the projects was incompatible. That's when I checked the PHP Tools version and I saw 2015 was on 1.29.10925 and 2017 on 1.29.10958.2017. Even after opening it in 2015 and making a change, it still hung in 2017.

So I looked on the forum and followed the advice to rollback the PHP Tools version, which worked.

Does it happen to you on empty project? Or it requires certain files/packages to be included in the project?

No it does not, and I could load other solutions.

Miloslav Beno wrote:Hi guys,

We think we've fixed the issue. Could you please try the latest preview and let us know? https://www.devsense.com/en/download

Thank you

I can confirm it was fixed!!!

Thanks, I tested this error has been fixed in Build-11007

Great! Thank you for confirming and all your cooperation. This was tough one