Microsoft.Azure.Functions.Worker.Sdk 2.0.3 causes MSBuild to fail to load Functions project

[julealgon]

Description

When we migrated to Microsoft.Azure.Functions.Worker.Sdk version 2.0.3 earlier today, I started noticing that my project appeared completely broken: when navigating to Program.cs, it would show red squiggles all over the place, nothing was resolved properly. Yet, the project would actually build just fine, which is extremely unusual.

I then noticed an error in the Errors window, coming from the .targets that is part of the Microsoft.Azure.Functions.Worker.Sdk package:

The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form.

When clicking on the error, I'm directed to this line:

azure-functions-dotnet-worker/sdk/Sdk/Targets/Microsoft.Azure.Functions.Worker.Sdk.targets

Line 165 in d0024ba

<_FunctionsExtensionsOutputPath>$([System.IO.Path]::GetDirectoryName($(_WorkerExtensionsAssembly)))</_FunctionsExtensionsOutputPath>

I initially tried clearing caches, deleting bin/obj folders, closing Visual Studio and deleting the .vs folder, the usual. However, the same issue would always happen when I opened and built the solution.

Downgrading to version 2.0.2 avoids this error completely and the project looks clean again, so I'm suspecting it is a bug in the library side.

Steps to reproduce

Install version 2.0.3 of Microsoft.Azure.Functions.Worker.Sdk and build a Functions v4 project.

[dmytro-gokun]

Same

[henriquemoises2]

Same thing happening here after an upgrade to version 2.0.3.

[D168997]

Same thing happening here. I can also confirm that downgrading back to 2.0.2 avoids the error as described.

[cimka]

Same thing for me.

[kutscherMKW]

same

[kinetiq]

same

[jviau]

The fix is available in 2.0.4

[rfphill]

Unfortunately for me, it dredges up another error "The project file "obj\Debug\net8.0\WorkerExtensions\WorkerExtensions.csproj" was not found.", which is why I downgraded in the first place.

Nightmare.

[jviau]

@rfphill I have opened another PR for that issue. You can currently work around it by first building the project on the command line. #3081