Every next version of Visual Studio is worse than the previous one

Drag the mole out of the MS building in Redmond already! Has he done not enough damage? It is likely measured in trillions of $$ already!

VS 2022 got a habit of freezing, which was not a thing with any previous version. It also falls into a state in which it begins to open 2x instances of the same form's designer, in 2x separate tabs spread across the tab bar. One of them cannot be closed until the other one is. This bug is dangerous as it leads to the loss of work as changes made in one of those 2x copies are not saved when the other copy is closed.

MS developers in China do not test, and due to their infallible attitude they do not admit fault, so all bug reports are closed w/o action. This is a dead end of the 3d party software development for .NET, which MS likely covets as they want to monopolize 100% of it for their own gain.

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

We are even more fucked than I thought

Microsoft's modus operandi is:

1. Break something
2. Blabber some BS about 'working to fix it'
3. Ignore the user feedback that could help to fix the issue instantly
4. Lock the issue so as to get no further reminders or publicity

Enter this bug which is not fixed for 4 years, since 2022. They essentially shot down all customers who have .NET Framework WinForms projects to migrate to VS 2022 .NET, like ourselves. We have to wrap. MS cannot.

When will the fucking Satya be dragged out of the Redmond office and beaten with bricks? The whole world's economy is suffering multi-billion damage over that turd's creative sabotage, but everyone is silent. His goons are allowed to silence and ignore enterprise subscribers who collectively paid billions for the VS subscriptions but got a defective POS in return, but everyone is silent. People got whacked over much more trivial sums of money, so WTF?

Here's your publicity, fuckers!

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

We are fucked. Truly. Seriously.

Microsoft has become a multi-trillion $$$ terrorist organization, I kid you not.

Enter IPNetwork, their lame extension of the IPIaddress class. Day late and dollar short.

This System.net.IPnetwork cannot parse CIDRs. It fails on some that do not start with the 1st IP address that they expect. Genius is as genius does: always as a degenerate.

According to this ticket it was closed/fixed for .NET 9, but the issue still exists, in the best traditions of Chi-com Microsoft dev teams' sabotage.

They also seem to have Microsoft.AspNetCore.HttpOverrides.IPNetwork, which according to their own documentation should have its own Parse method, but it does not in real life: 'IPNetwork' does not contain a definition for 'Parse'

This is so fucked that this is scary!

And of course, in the best traditions of Chi-com Microsoft, only their own staff can create issues in their issue tracker. We reached a dead end.

If this is the quality that we should expect from the world's largest software vendor with multi-trillon $$$ capitalization, then we are fucked.

Posted by: LinuxLies at 11:29 AM | No Comments | Add Comment
Post contains 181 words, total size 1 kb.

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.