@Michel B Before 2000, I used Visual Basic, quite naturally coming from QuickBasic.
Then I switched to Real Basic in 2001. When I went to the Mac App Store in 2013, I fetched a project from 2002 in Xojo, and was able to load it unchanged.
VB sources from the same period are absolutely impossible to use. That is a HUGE problem I don't have with Xojo.
With VS, source folders are a cumbersome and overblown mess where a mother cat would not be able find her kitten. In Xojo, even in XML, I can find things easily.
It is amazing how regularly in this forum, there are people coming from other environments who cannot seem to accept the Xojo philosophy, and want to make it something else.
I prefer Xojo for many reasons, and would not appreciate it becoming a satellite of VS.
BTW, Xojo is cross platform, and why did not the OP look into XCode instead ?
Quite simply, while the Xojo framework is not bad, the Xojo IDE is an embarrassment, particularly on the Windows platform. I use it for cross-platform and web application development but spend 70% of my time in VS (Windows is my main platform) and I can say with confidence that the VS IDE is worlds better in terms of stability, ease of use and functionality. i don’t think the OP was saying that the Xojo philosophy should be changed to that of VS, just that the VS IDE would make a great Xojo editor and I completely agree.
To take it a step further, I would not be offended at all if Xojo didn’t “eat their own dog food” and were to create the IDE for Windows in .NET, one for Mac in Xcode and one for Linux in QT. Heck, it wouldn’t even bother me if they used native controls for each platform requiring me to keep different code bases for each like B4X does. As it is, I have to use so many #Target statements just to make the layout acceptable for each platform for which I compile because if I don’t what looks good on Mac looks off on Windows and vice versa.
For an IDE that has been around since the 90’s I cannot believe how bad the current 2018r1 version is. It seems that with every release Xojo takes three steps forward and two steps back in terms of usability and stability. When you look at the number of bugs (Feedback reports) that have gone unfixed for years or the number of regressions that appear in each new release it makes one wonder why Xojo doesn’t stop adding features until the get the current framework and IDE stabilized. It’s a good concept and a great philosophy but the implementation needs a lot of work. I like it, I use it and will continue to renew my license but it definitely needs an overhaul.
TL;DR: Improve useability by allowing VS (Code) to be used as an editor for Xojo code until the current IDE is fixed and (mostly) bug free or remake the editor in each platform’s native languages to take advantage of the native libraries available to each.