When i try dotnet run, i got this error:
Unable to generate deps.json, it may have been already generated. You can specify the "-d" option before the tool name for diagnostic output (for example, "dotnet -d <toolname>": C:\Program Files\dotnet\sdk\3.0.100-preview-010184\Sdks\Microsoft.NET.Sdk\targets\GenerateDeps\GenerateDeps.proj
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hey -
Check the known issues here: https://blogs.msdn.microsoft.com/webdev/2019/02/05/blazor-0-8-0-experimental-release-now-available/
My workaround was to run dotnet new console -n test
(in a directory other than the Blazor proj). I then went back to the Blazor project and ran dotnet run
and Bob's your uncle.
Thanks @ericbyrd ... yes, it's listed there as ...
"Unable to generate deps.json, it may have been already generated.": You may see this error when running a standalone Blazor app and you haven't yet restored packages for any .NET Core apps. To workaround this issue create any .NET Core app (ex dotnet new console) and then rerun the Blazor app.
Thank you @ericbyrd .It's amazing that Google couldn't find that article.
Let's ask about both of those ...
@danroth27 Would you like to cover these two temporary known issues?
Known issues
There are a couple of known issues with this release that you may run into:
"It was not possible to find any compatible framework version. The specified framework 'Microsoft.NETCore.App', version '2.0.0' was not found.": You may see this error when building a Blazor app because the IL linker currently requires .NET Core 2.x to run. To work around this issue, either install .NET Core 2.2 or disable IL linking by setting the
false property in your project file."Unable to generate deps.json, it may have been already generated.": You may see this error when running a standalone Blazor app and you haven't yet restored packages for any .NET Core apps. To workaround this issue create any .NET Core app (ex dotnet new console) and then rerun the Blazor app.
@guardrex Not in the docs. We have them covered in the announcement blog post and now also in the release notes
Most helpful comment
Hey -
Check the known issues here: https://blogs.msdn.microsoft.com/webdev/2019/02/05/blazor-0-8-0-experimental-release-now-available/
My workaround was to run
dotnet new console -n test
(in a directory other than the Blazor proj). I then went back to the Blazor project and randotnet run
and Bob's your uncle.