4,816 questions
Problem is caused by the local NuGet packages cache, not sure why.
But cleaning it solved the issue.
dotnet nuget locals all --clear
Files from obj/Debug/net6.0 are being in deleted Blazor project
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 52%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPF%3C/text%3E%3C/svg%3E)
Priscila Fernanda Molina Reza
25
Reputation points
This issue has happened several times, I'm working on a Blazor project and suddenly it can't compile because the Client.dll file can't be found.
Usually the specified route contains this
But in my project this folder is empty, the DLL file is gone and all I did was adding a .razor file. I'm using Mudblazor, but i doubt it has anything to do.
Any hint on why is this happening? Or if there is any way of recovering my files?
Developer technologies | ASP.NET | ASP.NET Core
Developer technologies | .NET | Blazor
1,673 questions
Developer technologies | Visual Studio | Other
5,451 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2023-07-06T05:49:36.4333333+00:00 Hi,@Priscila Fernanda Molina Reza
The error message indicates the missing metadata file is in
../obj/Debug/net6.0/reffloder not../obj/Debug/net6.0,Also,have you tried right click on your project ,clean the project then build it ,check the output window for the detailed message
-
Priscila Fernanda Molina Reza 25 Reputation points
2023-07-06T16:33:47.44+00:00 I have tried clean/build but get the same output, i found the cause (although not very clear for me) it has something to do with the Nuget packages Cache and this command worked out:
dotnet nuget locals all --clear
Sign in to comment