3 ms·
The tool to port to .Net wasn't as bad as the article claims. I ported a pretty big messy WinForms application which was somebody else's years of work and today
by lopmotr 7y ago
The tool to port to .Net wasn't as bad as the article claims. I ported a pretty big messy WinForms application which was somebody else's years of work and today it's even more successful than ever. It took maybe a week or two to work through the many 100s of errors, but none were that difficult. I had already learned not to rely on proprietary binary libraries that were popular back then because you knew they wouldn't be supported in the future when you'd need them.
I'm very grateful for VB.Net. It's much cleaner and safer than VB6. My biggest wish now is for a way to port to C# piecemeal instead of doing the whole project in one shot.
- holri 7y agoI never tried to porting tool. Because porting to another proprietary platform did not make any sense to me after I experienced first hand what non-freedom means. I learned my lesson the hard way.