admin wrote: ↑16 Aug 2020 18:50
... I cannot afford to sit down endlessly fumbling around with a useless tool (my impression is that .NET is a failed language). ...
It is a bit amusing to me how perspective is everything, as I find myself cursing at established technologies on a regular basis. From a bit more rational perspective, one could argue that VB is a failed language, since it is pretty much dead since 1998 and only lived ~7 years, while .NET/C# being conceived in the year 2000 still going strong after two decades. But like I said, I fully understand your frustration with tech, as I am encountering it too on a regular basis, especially when trying to figure out how to get rid of legacy stuff. (Trying to replace C++/CLI stuff with pure C# to make it crossplat... *argh* where is my punching bag...)
On a more constructive note:
Have you thought about reevaluating your approach? From what I understand the goal was to throw everything in a language converter and then try to clean up whatever it spits out in one go.
Another approach would be to find a usable interop to another language and convert it part by part.
An example of this approach could be this article
https://www.codeproject.com/Articles/18 ... 0-Tutorial
Maybe even reevaluate if going for C#/VB.NET is the right way to go. From a rough bit of googling I found several statements saying just because VB.NET and VB6 have both "Visual Basic" in the name doesn't mean they are the same thing and it would be easy to convert between them. Maybe another language like C++ with
MFC which also makes WinAPI more accessible than from .NET would also make sense. If cross platform is a thing to be desired maybe Qt could be an option.