Don,

>If you are using Strataframe, you are locked in VB .Net.

I'm not sure what you mean here? The framework classes are developed in VB.Net so my code consumes them. My application code is developed in C#. This is one of the delivered promises of the .NET framework - you can consume components/classes/objects developed in any language that compiles to IL. I can't actually see the restriction you refer to?

>User interfaces are easier to build in VB .Net than C#, but it lacks some of the features of C#.

It has some extra features that I would like to see in C# - overall, whilst I dislike VB.NET, after going through the StrataFrame source code, it accomplishes all it needs to in VB.NET.

>Watch out, because rumor has it that MS's long range plan is to make VB the next legacy platform.

I am not married to StrataFrame, it is my current tool of choice. I can accomplish many comparable things using "out of the box" .NET. I would be more worried about the ramifications of using a legacy platform if I was only able to deliver applications in VFP.

>Yes, 3 months is not enough to become an efficient coder. It is enough to see what can be done, and where you can go with C#. It is enough time to realize that we cannot pour the salary base into a C# application that would be required. I can produce a VFP product sooner, with less cost, and with the same functionality as a C# application. I can use the same backend as does C#. By analogy, you will have to sell your "hammer" to your customer for $25 bucks, I can deliver my hammer for $15. They both will drive the same nail with equal grace.

That may be your reality and I respect that. However, I have been asked to quote for an application that is for the same business space in which I delivered another very similar application in VFP a few years ago. Whilst I could use either tool (VFP or .NET), I wouldn't actually dream of using VFP. Notwithstanding my personal preference, this proposed new application will replace one that was originally written in Clipper and migrated into Xbase++ (when they wanted to get into Windows from DOS). The client has insisted that I develop this application in .NET/SQL server. Their reason for this explicit instruction is not technology based. It is based on their experience of the difficulty recruiting Clipper and then Xbase++ developers. They want to use perceived industry standard technologies where there are a wealth of developers available from a large talent pool. This analogy equally applies to VFP - one of the reasons that my current job is based on C#/.NET is because the business found it extremely hard to recruit VFP developers.

So, I guess from your client's perspective, your $15.00 hammer could prove more expensive in the long run if you become subsequently unavailable to maintain their application in the future and they have to start all over again with another new system redeveloped using a different technology. I assume that you are able to secure more than $15.00 per hour - if not, this may prove be a self-fulfilling prophecy :) Obviously, I sincerely hope not.

Best,