Waiting for wife in car, i digested the first third. Nicely done. Apart from Roberts remark about Foxers which don't like/know VS. Expected a grin and the hint, that Chris wrote a wonderful IDE with X#. But nope, only more or less, "bad luck"... That i found really annoying, sorry.
No need to get wound up. I DID mention XIDE.
But since XIDE emulates the VO IDE I did not think it would make much sense to give it a very prominent place in a presentation to a group of FoxPro developers, who don't have a clue what the VO IDE looks like.
In fact, during the session from Eric Selje, we discovered that getting FoxPro users to use XIDE (at least at this moment) is not going to help them get started quickly, since there are no FoxPro templates, and also the terminology "project" and "application" is not helping them understand things. In FoxPro an "App" is called a "Project" (just like in Visual Studio).
well, sorry, but here you are. If i hadn't more "against" using VS, than "app" vs. "project", i would have stayed with Vo2.0. As any Fox guy probably would do with whatever he has, if this bothered him...
C'mon, "no templates", indeed. I shouldn't have to remind you that Xide started as CULE-Edit, migrated to VN and now to X#...
So, what's your suggestion to a Foxuser, who want's to venture in X# pastures - to learn VS first?
The idea of our presence at SW Fox was to introduce FoxPro developers to X#.
The FoxPro audience already knows VS. They have seen dozens of sessions on how to talk from FoxPro to C# for example.
By using and focusing on X# inside VS we were not introducing 2 new things to them, but only their Xbase language compiling and running in .Net and inside VS. That was the idea behind it. And I still think that was a valid decision.
As you know, I very much appreciate that you like XIDE a lot, I also like it a lot and prefer it to VS for my own programming tasks. But XIDE is written from a VO person's perspective and as I had suspected when designing it, it did appeal also to other VOers than me. But VFP is very different to VO, VFP programmers are in a lot of ways used to a different programming style than VOers and it is highly unlikely they will find XIDE appealing.
In case some VFP developers do try it and find they they like it, I will of course make adjustments to make it cover VFP needs much better, but I very much doubt any VFP user will ever want to do that. For now I have just implemented the very basic VFP compatibility needed so we can run also VFP compiler tests from within XIDE, because it is a lot straightforward doing it this way. Having said that, I suspect (x)Harbour users will actually do prefer working in XIDE, when X# has full support for this dialect as well. But VFP programmers, I am pretty sure they will not.
Obviously, I can't speak for Robert, but, I was at SWFox 2019 Conference myself, and I saw Robert in at least 2 other sessions related to VFP and .Net/C# integration (presented by Doug Hennig and Rick Strahl). I think Robert was able to see from the speaker's interactions with the session attendees that indeed, many FoxPro people *do* already have a good bit of familiarity with .Net, C#, and Visual Studio (myself included for over 10 years vs 25 years with FoxPro). Many VFP people there are like me (VFP + .Net). It is no big leap to learn .Net (any of them) or Visual Studio.
I like Chris, he is smart, but I do not want to take a dependency on his one-man-developer XIDE (no offense Chris). I want a full, robust, .Net focused IDE, and that is Visual Studio, hands down.
Sure, by all means XIDE is an impressive work, and indeed .Net focused (poor choice of words on my part).
I guess I was referring to things in Visual Studio like Nuget Package integration, and the (massive) Visual Studio Marketplace for distributing/installing Visual Studio add-ins and extensions, Database Integration, Azure Integration, etc.
Yes, it is a beast of an IDE, with more bells and whistles that any one developer would ever need. But, it's very widely known and supported, and that's what I like.
Regard, let's get back on the goodness of X#. That's the main thing I want to promote.
mainhatten wrote: "faster" is a great feature for this vfp user, as he is used to minimal compile time to p-code and almost instantenuous start up of vfp pcode-interpreter..I will certainly test foreign waters...
Sorry, I wasn't clear, with speed I meant the IDE functions themselves, for example the editor in XIDE is fast also in very old machines. But regarding compiling speed it is not making a difference, no matter if you use VS, XIDE or even command prompt to compile, the compiling speed will be almost identical, as the compiler is completely separate from the IDE(s).