Skip to main content

Why xSharp might be the tool FoxPro developers have been waiting for

In the latest FoxShow episode, I interview Robert van der Hulst, one of the main leads on the xSharp project. Unlike many product team leads, Robert has a secret advantage - he actually USES the product. The interview answers a number of questions VFP developers may have about this initiative.






While he's been a direct team member of a variety of products in the xBase market (he hails from the Clipper and Visual Objects world), he has always looked at the product based on the idea of "how can I use this as a business?", an idea many business line developers think about.



XSharp uses the open source Microsoft Rosyln compiler but translates the language constructs found in the xBase and VFP world so that developers can more easily port their application into the DotNet world. While DotNet was introduced almost 20 years ago, there are still a number of applications that use it for critical parts of their business. But what if you could take key pieces of your application (such as the COM component you built or years old business processing pieces) and use them in a full Visual Studio solution, generating a DotNet (and DotNet Core) compatible application?

As a manager, wouldn't it be great to use the knowledge and existing code in your legacy application in your brand new shiny .Net application so you don't have to push back your release while doing the knowledge transfer to the new developers who would rather code in Python or F#?

I won't spoil the entire interview but here are some key areas and jump points you may want to hear:

2:00 -- Who is Robert?
10:00 - the xSharp compiler and the concept of dialects
20:00 - Target market 
25:00 - Form design & event handling
30:00 - Status of xSharp as a released product
39:00 - Multi-threading, syntax issues and feature support
51:00 - Roadmap to the future
56:00 - Southwest Fox 2019

What about you? Are you still working in VFP but looking to move into the .Net world? XSharp may be your opportunity to leverage your skills. Listen and let me know if you think XSharp has a future in your life.

Comments

Unknown said…
Andrew this year I cannot make SWFox. If you cannot live stream this, please consider recording it so I can watch your presentation online later!

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...