You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My dotnet sdk is extremely slow on creating new projects, so I dug a little on this abnormal behavior, and then I found that dotnet is making a lot of network requests. I use Wireshark captured those activities:
This set of hosts looks like dotnet new checking for template updates, rather than telemetry. #10564
Maybe you can set DOTNET_NEW_LOCAL_SEARCH_FILE_ONLY=1 and try again to try to rule that out? I found it in dotnet/templating#2093, which tracks improvements around the slowdown.
My dotnet sdk is extremely slow on creating new projects, so I dug a little on this abnormal behavior, and then I found that dotnet is making a lot of network requests. I use Wireshark captured those activities:
.NET core sdk sends requests to
when "dotnet new" runs.
Dotnet sdk won't return to the shell before those requests finished, and that's why it hangs after "Restore succeeded." message
Not a new thing: #6145
But I already set DOTNET_CLI_TELEMETRY_OPTOUT=1 on my machine
The text was updated successfully, but these errors were encountered: