A @Giles Evans has posted a couple opinions in the <https://xojo.com/issue/28733>
[quote=@Michel Bujardet]Main visible advantage of .Net is no flicker.
Dont confuse VB.Net and Xojo.[/quote]
[quote=@Giles Evans]@Tim Jones
It’s the comments left by others that leaves me to question the advantage of .NET to those who would want XOJO to support it. I am relatively new to XOJO, but from a C++ and Assembly I’ll always opt to call the Win32 API directly over .NET 98% of the time. .NET let’s you get started faster if you’re learning, especially for building your form with a visual interface. That’s very appealing for a while, but in my experience you end up finding some very hard limitations.
If I wanted a “Flicker Free” app I would definately avoid .NET at least from C++. Microsoft added the optimizations of double buffering and others to .NET because that was, and still is, a serious bottleneck of the .NET framework. I suspect this “flicker” is more of an issue with the XOJO framework itself needing work on optimizations and will more likely only get worse in a switch to the .NET framework.
Most of .NET is nothing more than an C++ (Object Oriented) Wrapper around the Win32 API and is intended to hide the tedious details of the Win32 API. It succeeds at that in some respects, but fails in others. If most of what you write fits well with what MS tries to support, it can succeed quite well. If you depart into “virgin territory” like direct hardware communications, you can lose the advantage entirely, and even cause a great deal of extra work compared to native code using Win32 directly.
And since XOJO’s own framework already hides the tedious details of the Win 32 API then what would be the advantage of moving to the .NET Framework? Rather than change XOJO itself would it not be better to add .NET, WPF or any of the other select proprietary Microsoft frameworks as add-ons for those who would like them. Since 90% of my programming work still needs to target WindowsXP machines WPF, or a “Modern User Interface”, or recounting the DLL hell of Visual Basic 6 with a more modern .NET versioning twist, would not benefit me personally.[/quote]
[quote=@Michel Bujardet]Giles Evans,
May I respectfully point out that this is a bug report and feature request tool, not a forum. If you want to voice opinions, they will be most welcome in http://forum.xojo.com
I have replied to your last post in forum at Why not implement .Net ? - Windows - Xojo Programming Forum
Please continue the conversation there where it has much more its place than in a feature request where you rebuttal appears like an effort to derail a long file feature request.
You are perfectly free to file your own feature request to ask that Xojo never implements .Net.
This is your opinion, after how many weeks or months of using Xojo ? Don’t you think people like me who have been using Xojo since 2002 have the right to see their voice heard ? I resent that sudden charge on a feature request that has been posted as early as 2013.
Once again, Xojo is NOT VB. Net and there is no reason if and when it ever supports .Net that it may lose the ability to address hardware directly. Precisely, Xojo has always demonstrated the ability to support framework changes transparently, especially on Mac where since 2002 it has seen change in processor, change in system, and change in framework. Code from 2002 can still be compiled in 2017R2 with little to no changes.
At any rate, your opinion is most welcome and valuable in this forum, where it has much more it’s place than in the Feedback system.