>>Hi All,
>>
>>We have a huge VFP application that we want to webify piece by piece, module by module. We prefer to do a total rewrite in web responsive MVC solution with C# and VFP COM where neccesary.
>>We have developed a web portal for patients already using this methodology and it works fine. Clients are very enthousiastic.
>>
>>Even though we have a lot of functionality in there, our programmers hit a brick wall on when things become more complicated.
>>For example when a modal dialog is needed, complex grids, or alternatively a process of multiple steps have to be performed and data has to be passed though the process..
>>
>>As I'm not a Web developer and stayed away from that as I really do not have the time, I need some advice which way to go.
>>
>>On one side we need to stay productive, but we also are hesitant to jump onto another product that walks the dinosaur soon, or locks you in with expensive subscriptions and might not keep up with technology in the future.
>>Using MVC with C# and HTML5 seems very flexible and future proof to me, but when it comes to more complex data entry forms with grids, treeviews, processes with modal dialogs, it seems that we really need to get some 3rd party solutions to make things easier to develop and maintain.
>>
>>I'm not looking for the cheapest solutions, nor am I for some quick but less future proof solution. I'm looking to for a platform independed solution that is as future proof as possible with a popular technology that does not take very rare / expensive programmers
>>to build.
>>
>>Any advice is welcome,
>>
>>(And no, we're not opting for VFP web solutions like FoxInCloud, etc)
>>
>>Walter,
>
>For web I would go < g > for non-MS solutions like Go, Ruby, Python ... They are much more productive and cross platform and also open sourced. I have done and doing C# MVC projects but now leaning towards Go.
>OTOH you might have trouble in finding Go programmers and AFAIK they are more expensive. You might learn it yourself and would mean a better investment than learning C# (if you don't already know it).


We already have an investment in C# MVC, having one app down and 2 in the works. Not dismissing the validity of non-ms technologies, but despite the hic-ups I do not feel the grass is greener at the neighbours. Yes the availability of C# programmers is one reason for this choice.

As for open-source, while free. In general, (and I know there are exceptions), it does not mean its cheaper, more secure, of more quality or future proof.

Walter,