There's nothing wrong with no longer wanting to distribute a 25 year old application that you no longer support development tools for. However your comment is c

There's nothing wrong with no longer wanting to distribute a 25 year old application that you no longer support development tools for. However your comment is completely disingenuous. One of the first links I ran into was a massive support article from Microsoft about how they will still allow VB6 applications to run on Windows and gave detailed instructions/tools on upgrading a Visual Basic project so you can continue development and don't lose all the work. > While the Visual Basic 6.0 IDE is no longer supported, Microsoft's goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. The resources available from this page should help you as you maintain existing applications, and as you migrate your functionality to .NET.[0] This is much better support than other companies provide for discontinued platforms. Do you personally want to be on the hook for a version of your software you wrote/released 25 years ago? Especially if you've released what you consider to be improved upgrades of the software? Would you even be willing to help users upgrade from your 25 year old software? If the answer to any of those is no, then you're providing a very skewed perspective on what reasonable support for a product looks like. And once again, Microsoft is still writing articles 20 years after the initial release to help users upgrade. For all the bad crap Microsoft does, completely abandoning widely used frameworks is not one of them. [0]: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6.0-documentation https://learn.microsoft.com/en-us/previous-versions/visualst...