MSB4023 Cannot evaluate the item metadata "%(FullPath)". The item metadata "%(FullPath)" cannot be applied to the path ""

Narendra Jangir 0 Reputation points
2023-05-20T07:04:51.5866667+00:00

I started getting this error in the all .net6 apps build from last couple of days.

MSB4023 Cannot evaluate the item metadata "%(FullPath)". The item metadata "%(FullPath)" cannot be applied to the path "Endpoint=https://xyz.azconfig.io". The given path's format is not supported.

When I build the project I started getting 3 more errors- Severity Code Description Project File Line Suppression State

Error   MSB3030 Could not copy the file "Endpoint=https://xyz.azconfig.io" because it was not found.    ConsoleApp1 C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets    5215

Error   MSB3030 Could not copy the file "Id=uzRN-lo-s0:nfvf/KDPta7aI86ZLWe1" because it was not found.  ConsoleApp1 C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets    5215

Error   MSB3030 Could not copy the file "Secret=pjCrT0acZV8gobbW30MOtHeIK1S8Be8GNI0gKOnt0Ns=" because it was not found. ConsoleApp1 C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets    5215

I have tried below given ways with no luck-

  • Clean the solution and rebuild
  • Delete bin and obj folder and rebuild
  • Close the visual studio and reopen and build
  • Delete visual studio cache
  • Uninstall visual with all features and install back.

Any help would be really appreciated.

.NET
.NET
Microsoft Technologies based on the .NET software framework.
3,399 questions
Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,195 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Narendra Jangir 0 Reputation points
    2023-06-01T09:50:47.0666667+00:00

    Hi @Tianyu Sun-MSFT ,

    I have tried all these ways and it didn't work for me.

    I couldn't spend so many days on this stupid issue so I get my user account deleted and created again in the system with the help of IT team and that resolved the issue for me.

    Thanks,

    Narendra

    0 comments
  2. Sergey Taymanov 0 Reputation points
    2023-07-25T23:12:54.8366667+00:00

    I've just faced with the same problem.

    The reason was that an environment variable TargetName=MyProject:rebuild exists. I used it as a local variable in my cmd-file. Probably this variable conflicts with a MsBuild-property TargetName

    I solved it by renaming TargetName into TargName.

    Please check you environment variables. I think there will probably be variables with the same name as some MsBuild-property among them

    0 comments