Build option gone and starting debug issues.

AlexO

The build option recently disappeared from my context menu on my project. I would use the build command to run custom scripts but it is suddenly gone. Also, when I try and debug now it tries to build the app like a compiled program and throws and error about a missing Microsoft SDK. My development process is very effected by this. Can you please advise what the issue may be?

Windows 10
PHP Tools: 1.66.15733.2019
VS: 16.11.9

JakubMisek

Hi @AlexO, looking into it.

JakubMisek

This looks very different from what it should look like. May I ask to see the Project File? (Edit Project File)

Thank you,
Jakub

It should be basically something like this:

<Project Sdk="Devsense.Php.Sdk">
  <PropertyGroup>
    <RuntimeVersion>8.1</RuntimeVersion>
  </PropertyGroup>
</Project>

JakubMisek

Edit (2):

.NET SDK (version 5 or 6) for Visual Studio 2019 is needed. It is usually installed together with Visual Studio, but sometimes it can get corrupted by Visual Studio updates. For a quick workaround, I would recommend installing SDK from https://dotnet.microsoft.com/en-us/download/dotnet/5.0 or check the Visual Studio Installer app if there is up-to-date .NET SDK installed.

JakubMisek

We're updating the preview installer to handle this automatically.

AlexO

Thanks Jakub. Installing the SDK fixed the issue. I suppose it got corrupted like you said.

I am now having issues with debugging and hitting breakpoints. I can only hit breakpoints on the entrance script to my application. Anything beyond that the breakpoints won't hit and I have step into to get to them. Any advice on that or anything I can provide to help find the issue.

Here is my project file you asked for in the first post.

Thanks

<Project Sdk="Devsense.Php.Sdk">
  <PropertyGroup Label="Globals">
    <ProjectGuid>93fa99aa-43ec-456c-a0be-a8a4fe9a7cd7</ProjectGuid>
  </PropertyGroup>
  <PropertyGroup>
    <EnvName>Custom</EnvName>
    <RootNamespace>PushX_PIR</RootNamespace>
    <WebRoot />
    <RuntimeVersion>7.4</RuntimeVersion>
    <SaveServerSettingsInUserFile>false</SaveServerSettingsInUserFile>
    <PHPDevHostName>localhost</PHPDevHostName>
    <PHPDevAutoPort>true</PHPDevAutoPort>
    <PHPDevRouting />
    <CustomServerUrl>http://pir.pushxdev</CustomServerUrl>
    <CustomXdebugPort>9000</CustomXdebugPort>
    <DebugMappingMethod>Automatic</DebugMappingMethod>
    <DebugPathMapping />
    <DBGpProxyEnabled>false</DBGpProxyEnabled>
    <DBGpProxyHost />
    <DBGpProxyPort>9001</DBGpProxyPort>
  </PropertyGroup>
  <ItemGroup>
    <Content Remove="composer.lock" />
  </ItemGroup>
</Project>

JakubMisek

Thanks. Good it fixed the issue; we've updated the installer as well, so .NET SDK should get installed automatically.

Breakpoints are in .php files, within a PHP code or JavaScript code? Are they in some kind of unusual folder?

AlexO

JakubMisek The breakpoints are in .php files that I usually have no trouble hitting. I have debugged and hit breakpoints in these files countless times but they are no longer working.

In my screenshot below, only the BLUE breakpoint and file will hit. The RED breakpoint will not hit. I have tried many different breakpoints and files. I double checked I am executing the correct files/urls. It will only land on the blue breakpoint (an entry point to my program). Breakpoints used to work as normal but this issue suddenly appeared. I had version 1.65.15697 when this started happening suddenly. I upgraded to the preview version 1.66.15736 to see if it would fix the issue but it did not.

EDIT: I posted wrong screenshot

MiloslavBeno

Hi Alex,

May I ask if you could provide us with Xdebug.log, it would get us more information to diagnose what might be happening?

You can turn it on in the php.ini file by adding xdebug.log = "SOME_PATH/xdebug.log"

Thank you!

AlexO

I believe I fixed the issue with debugging on my side. I believe it was related to a Windows Update and the PATH environment variables getting reset. I fixed my PATH variables and debugging is working again as expected. I can't explain why, but it is working now.

MiloslavBeno

Hi Alex,

Interesting. Anyway, I'm happy it works for you, but please feel free to let us know if this happens again.

Have a good one!