In January we have shared our list of "things to do" with our subscribers and asked them to help us prioritize the development.
We have analyzed the feedback and combined that with our own ideas and have come with the following plan for 2021.
But before we list the results, we would really like to thank our subscribers for the very positive feedback. The most requested feature was "that we stay in business". And that is exactly what we plan to do !
Finally the obvious disclaimer: these are our plans. They are not set in stone. We will adjust these plans whenever we see fit.
| When |
SubSystem |
Deliverables |
|
Q1
|
Compiler /
Language |
- New compiler based on C# 9 with support for Local Functions, USING statements and more. This also prepares the compiler for new features in .Net 5 and .Net Core.
|
| Runtime |
- Additional FoxPro runtime functions
- Improved FoxPro array support
- Beta version of VO GUI Classes based on Windows Forms and VO SQL classes based on Ado.Net
- ExecScript() support based on the Full Roslyn scripting engine
- Runtime Debugging support with windows built in the Runtime to show workareas/cursors, globals, privates and settings
|
| VS |
- Visual Studio performance enhancements and improvements in the code completion.
|
| Tools |
- FoxPro project to VS solution converter. This includes a first layer of UI classes that map the FoxPro UI to Windows Forms.
|
|
Q2
|
Compiler/
Language |
- New languages features, such as improved Tuples support
- Parsing of FoxPro embedded SQL
|
| Runtime |
- Beta version of SQL RDD that uses Ado.Net to fetch data.
- Implementation of FoxPro embedded SQL based on Advantage Database Server
- Additional FoxPro runtime functions
- Release of VO GUI Classes based on Windows Forms and VO SQL classes based on Ado.Net
- Speed improvements for Shared DBF access
|
VS / Build
System |
- Beta version of support for .Net 5 and .Net Core (the compiler already supports this)
|
| Tools |
- Improvements to the FoxPro project converter and support libraries
|
|
Later /
when it is ready
|
Compiler /
Language |
|
| Runtime |
- Adjust our runtime to work with .Net 5 and .Net Core
- The last missing FoxPro runtime functions
- Optimized version of the ExecScript() support
- FoxPro reporting (based on ReportPro)
|
| VS / Build System |
- Release version of support for .Net 5 and .Net Core in the build system and Visual Studio
- Debugger improvements
- Support for .Net 6
- Additional project templates for various platforms and problems.
|
| Tools |
- Adjust ReportPro 2 to use Windows Forms for its UI and support FoxPro reports
|
Wish you success, because it is mine too!
I read the blog on .NET 6 last night. I really wish, X# can target .NET Standard 2.0 too.
Regards, Andrej Terkaj
Wish you success, because it is mine too!
I read the blog on .NET 6 last night. I really wish, X# can target .NET Standard 2.0 too.[/quote]
Rene,
When we target .Net Core and .Net 5/6 then .Net Standard will come "for free".
Robert
Wish you success, because it is mine too!
I read the blog on .NET 6 last night. I really wish, X# can target .NET Standard 2.0 too.[/quote]
Rene,
When we target .Net Core and .Net 5/6 then .Net Standard will come "for free".
Robert[/quote]
Thanks. I really need this in 2021-H1. It forces me to have duplicating functional code on C# which could have stayed on X# as I need to work with both Xamarin Forms apps and Blazor.
that way a lot of functionality already in Advantage can be reused, which makes LOTS of sense, esp when I look at the enhancements already finished there.
Guessing that you need to hook ACE via ALS license installed in the system that raises for me the question if FoxPro embedded SQL can be called if running (in the future under .Net5 or .Net6) on ARM (iOS new Macs, iPads and iPhone) and/or Xamarin Android ? Those are explicit compile targets under Xamarin, but Advantage only installs on Linux and Windoze on intel86/AMD64 CPU architecture last time I checked (when Thread "A simple program - many errors!" was fresh topic and your call to SAP was imminent. /part1
Running on mobile without ORM on just a thin local cursor layer selected from backend data via cursoradapter to munge locally is the thing I cannot do in vfp - x# "just" as a newer optionally type safe desktop system is still interesting, but has to compete with VFPA compiling to C++ and with 32/64 bit options running already optimized vfp local data engine on dbf cursors. /part2
Offering vfp embedded SQL engine on mobile is close to "no contest" or "winning by default" at least for me, as that (and embedded/smaller stuff like RasPi) are growing much stronger than traditional PC.
Could you shed some light if/how you plan to offer FoxPro embedded SQL on ARM/iOS/Android and possibly WASM as compile targets ? Any news on the SAP phone call ?
thx in advance
thomas
[quote name="Thomas Ganss"]part3:
Offering vfp embedded SQL engine on mobile is close to "no contest" or "winning by default" at least for me, as that (and embedded/smaller stuff like RasPi) are growing much stronger than traditional PC.
Could you shed some light if/how you plan to offer FoxPro embedded SQL on ARM/iOS/Android and possibly WASM as compile targets ? Any news on the SAP phone call ?
[/quote]
Too many questions to answer properly in the comment feature on the website.
Why don't you join us in this weeks Online session. The presentation from Chris will start at 16:00 but we'll open the session around 15:30, so we can chat about things. This would be a perfect topic to chat about.
Robert
Too many questions to answer properly in the comment feature on the website.
Why don't you join us in this weeks Online session. The presentation from Chris will start at 16:00 but we'll open the session around 15:30, so we can chat about things. This would be a perfect topic to chat about.[/quote]
Last week marked 2 years of our weekly policy/troubleshoot session in the company I do stuff for, every Thursday 14:00 open end but seldom more than 4H. Nowadays mostly not in person, but still a routine in calendar week... I'll try to get our start moved to 12H and if nothing pressing shows up, gladly.
If this does not pan out, I'll open a forum thread in vfp forum and copy my blurb from above.
regards
thomas
BTW send was erroring out on msg loo long with "18 symbols left" shown below edit box?