After the Latest Update Not able to Debug the Azure Function

[Sudheesh-TalentzQ]

Until 11-11-2024 i was able to debug my Azure Function with VS Code but From 12-11-2024 I'm not able to Debug
it will throw Unable to detect project file.
Tried Deleting the .vscode folder and again Intializing and setting the default project even with the property group in .csproj file but still keep on getting this error

[abhishekRamalli]

yes i am also facing the same isssue
@Sudheesh-TalentzQ have you checked downgrading

[abhishekRamalli]

@Sudheesh-TalentzQ it is issue with new release only
downgrade it will work fine

[Greg-BW]

I have the same problem. Downgrading to the previouse version fixed it for now.
When trying to run func start manually it says that it found two .csproj files but expected one, even so only one is present in that directory

[Sudheesh-TalentzQ]

Downgrading Does fix the issue .... Should i Close this Issue or should i wait until they give another way to fix it without Downgrading.... What if the issue continued to other versions as well.

[sboulema]

Ran into the same problem. I would keep this issue open since downgrading is only a temporary workaround.

[ChristianAgren]

Downgrading solved the issue. For anyone looking how you can install a specific version of an extension in VSCode:

[nturinski]

Downgrading Does fix the issue .... Should i Close this Issue or should i wait until they give another way to fix it without Downgrading.... What if the issue continued to other versions as well.

Thanks for reporting this issue. Please do not close it-- we are investigating what in the new release is breaking the debugging scenario. Sorry about this bug ☹

[nturinski]

I was able to pinpoint the error-- the extension is doing an additional check and does not like it when there are 2 .csproj files in the root of the workspace. I'll be working on a fix, but I was curious what is a usual scenario where a project has two different .csproj files? I'm not a .NET power user, so I'm a little ignorant when it comes to these topics 😅

And in these cases, would it be better for us to auto-detect the "right" .csproj file or allow the user to select which .csproj file that they would like to use for this Functions project?

[nturinski]

It would be very appreciated if anyone could try this alpha vsix to see if it fixes the issue (without causing any new ones 😓)

1. Download the Artifact from here.
2. Extract the Artifacts.zip to extract vscode-azurefunctions-1.16.1-alpha.0.vsix
3. In VS Code, press F1 to open the cmd pallette
4. Search for Extensions: Install from VSIX
5. Navigate to where the vsix was extracted and install it

Many thanks! And again, I apologize for this issue.

[RossRichardson]

Hey @nturinski , I'm receiving this error while having 3 .csproj files about 2 levels down in sub paths from the root.

I have one file for my api, one for tests and one for the db. we'll often have multiple project files under one solution file.

May I suggest using the existing azureFunctions.projectSubpath param in the settings.json when there are multiple project files? No need to autodetect anything then.

[iambeanie]

@nturinski Installing that artifact you linked worked a treat, able to debug my function apps again!

Similar to RossRichardson, our solutions all have multiple projects in sub folders (domain, function app, tests etc...) with the sln in the root.

[MicroFish91]

Should be fixed by: #4333

This will be included in release v1.16.1. If anyone runs into this issue again on the new release, please feel free to reopen it.

[nturinski]

Just letting everyone know that v1.16.1 has been released. Thanks for your patience in dealing with this bug!