Nuget Package Manager VS announcements

- https://github.com/NuGet/Home/issues/8843

GitHub Issue

Similar issue here: https://github.com/dotnet/sdk/issues/28971. Following the breadcrumbs it looks like it may be a NuGet issue, reported here: https://github.com/NuGet/Home/issues/12227

Your issue appears to be related to not having the appropriate permissions to the Nuget folder (so says the error). There is an existing Bug/Ticket open on the Nuget github for this exact issue. There are a few solutions and/or workarounds listed through the conversation that you can try: https://github.com/NuGet/Home/issues/12162. Unfortunately I do not have a Mac to validate the solutions or the issue myself.

sounds like ur terminal has no internet connection here is a setup for configuring a proxy

The NuGet team is actively working on adding support for CPVM in .NET SDK 7.0.100/VS 17.4. There was a spec for the initial work that you can read at NuGet/Home, and they're looking to polish up and incorporate that work soon.

How do you currently feel about attaching the experience to install or when restoring packages? Various ecosystems do this and some get flak for it because of how many transitive dependencies and known vulnerabilities in comparison to others. I'm mostly curious because I'm working on a similar proposal here:

https://github.com/NuGet/Home/pull/11549

There's definitely a fine balance of noise, but how do you feel about it?

I don't think that works. That would alert you about the security alerts on the Security tab of the dotnet/announcements repo, which are empty, not about issues that contain information about .Net security issues.

.NET Core 2.0 Cryptography uses Apple Security Framework on macOS · Issue #21 · dotnet/announcements (github.com)

Yeah, it's a fun meme, but there have been a few nasty RCE vulnerabilities patched on .NET Core in the last couple years. Like this one: https://github.com/dotnet/announcements/issues/178

If you started receiving errors when pulling old versions of dotnet docker images (like the .NET 2.1), it's because Microsoft deleted them from Docker Hub on August 21st, 2021. That date is not a coincidence, the .NET Core 2.1 reached end of support in the same date. For more details take a look at the official dotnet announcement or also the dotnet blog. In my case, the error bellow was thrown in the stdout when pulling the microsoft/dotnet:2.2-aspnetcore-runtime image:

I'm not entirely sure what that means. We're done porting .NET Framework APIs to .NET Core / .NET 5. .NET Framework is what it is now, and .NET is moving forward with .NET 6+. If it is worth porting your code to .NET 6, it is. If not, then it isn't. Both can be good choices. .NET Core on Linux, however, is absolutely not preview.