VFPConversion - VFP and/or .NET?

After the Community GetTogether at CeBIT fair I'd like to talk a little bit about VFPConversion. VFPConversion? Never heard of? Well, fine. VFPConversion is a corporation of several companies that share high experiences in Visual FoxPro as well as .NET programming skills. There are a lot of well-known developers onboard.

There are several training events all over the globe - okay mainly U.S.A. and Europe - that explain the principals of the .NET Framework as well as programming concepts in C# and VB to VFP developers. I think the whole stuff is more than worth to attend because it's a vey good chance to talk to .NET developers as well as VFP developers and share experiences.

Personally, I work with VFP since version 6.0 Service Pack 5 back in early 1999, and since 2003 with C# and the classes of the .NET Framework. Currently, my language of choice is still FoxPro but with every new version of C# it's getting closer to my requirements. And therefore even more attractive than VFP. But thats mainly a matter of the huge class library and possibilities the framework itself provides.

Talking about Sedna CTP, I'm actually disappointed. Especially while playing around with the COM proxies. Hell, it's quite easy to program a COM class in .NET and to provide those functionalities to VFP. But the RegEx sample is quite annoying. I already wrote a similar COM proxy in late 2005 with the same interface as the VBScript.RegExp COM server. This way, you don't need to change any line of code but the CreateObject() statement to get a reference to the COM object. Okay, it's just a CTP but it's really disappointing. Hopefully, future releases of Sedna might bring a lot more useful functionality.

Sincerely, JoKi