VFP to C#, frankly don't bother...

[GriffMG]

I have been working on a project to convert an app to c# for far,far too long.

It is so horrible I cannot bear to tell you.

c# should be c(pooh)

The simplest things, arrgh. If you have a three line clipper or vfp app, go ahead, it's easy, but if you have
a really serious vfp project, DO NOT GO THERE.

Let me give you one really painful experience.

In c# with winforms, you can have menus with sub menu items - even sub menus.

Imagine a language where you can disable a menu, and thus its items - sounds normal.

In c# you can do that, but if you have another menu item which is not disabled, which has sub menu items,
then your sub menu will be ENABLED should the users cursor drift across the enabled one.

How pooh is that .

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Mike Lewis]

The thing I hated most when I was doing C# was the hoops you had to jump through to create your own classes. It was a real pain after VFP.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[GriffMG]

Are you not doing c# now Mike?

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Mike Lewis]

Not really. It's still in my repertoire. I last used it a couple of years ago to write some command-line utilities for a client, and I might use it again one day. But I haven't kept up to date with it, nor do I feel a need to do so.

To be honest, it's hard to focus on new tools and languages when we've got the whole of VFP to fall back on.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[GriffMG]

Exactly.

As long as it keeps running, I would prefer to run with it - keep the Fox!

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Olaf Doschke]

What's seldom advised and thought about: If something running on Windows eclusively is enough for you, if it's offering main aspects of VFP like being centered on data with royalty free data storage, capable of Office integration, having own reporting options, able to connect to remote databases, eg MS SQL Server, able to make use of Windows API functions or other DLLs and able to be extended with ActiveX controls, then - even if it makes you shudder - you may also switch to MS Access.

You are not bound to .NET or Lightswitch. You may be a little unfamiliar with it, but VBA is closer to the VFP language than VB.NET and if you don't need OOP, VBA could be sufficient for you. Data handling is then better done with ADO and SQL is more important, true, but that's just your inconvenience coming from VFP. Access is addressed to the type of developer you describe, not wanting to dive into all you need to know for enterprise application development.

Also see what Mike wrote in the other thread184-1719827

Everything is said already.

Bye, Olaf.

 

[craigber]

If it's easy in VFP, it's hard in C#. If it's hard in VFP, it's easy in C#" - Kevin McNeish

If you have a business need to rewrite your VFP app in something else, I say do it, but just because VFP isn't getting updated any longer may not be a good reason.

Craig Berntson
MCSD, Visual C# MVP,

http://www.craigberntson.com/blog