Microsoft intentionally broke 'nuget pack' command

How do I know that it is broken? Ha-ha!

How do I know that it is intentional? They refuse to fix it.

Google +nuget +pack "Method not found: 'System.ReadOnlySpan`1 Microsoft.IO.Path.GetFileName(System.ReadOnlySpan`1)'" and you will find the discussion on their decoy forum and their lament of how they detect .NET libs. Their own fucking libs, for crying out loud!

To add insult to injury, once you try to switch from 'nuget pack' to 'msbuild /t:pack', you will be hit with error MSB4018: System.InvalidOperationException: The assets file produced by restore does not exist. Try restoring the project again. The expected location of the assets file is....

They either can't find their ass with their both hands, which is absurd, or they are lying, which is plausible. Bottom line is that MS made it impossible for us to create .NET framework nuget packages in VS pre-2022, for which we have paid enterprise subscription fees.

No decency left in this world.

Posted by: LinuxLies at 07:04 AM | No Comments | Add Comment
Post contains 168 words, total size 1 kb.