Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You may want to rethink your requirements here. The WinForms model is quite different from the ExtJS model or traditional HTML forms, so converting your application to a web application on the fly will be difficult at best. It is some time since I looked at ExtJS myself, but does it have equivalents of all the standard WebForms controls? And how about user controls and other controls delivered by third parties? And owner-drawn controls? </p> <p>Instead of spending months on something that may not work properly after all, I would suggest that you look at properly layering your application. If you separate your data layer and expose it as web services of some sort then you can easily make them available for both a win forms application and your ExtJS web application. As long as you keep your business logic as well as your data layer inside the web services the user interface itself should be easy enough to make. Probably easy enough that the automatic generation of the web gui won't be worth spending time on. </p> <p>Anyway. If you really really want to go this way you could consider using a web service to describe your GUI and build both your WinForms gui and ExtJS gui on the fly. Both technologies support building forms in code so you could download a file that describes the gui and build it the first time the user loads your application. That would require you to write two sets of gui-building code but since it would be based on a format that you control it would probably be easier than to convert a WinForms application to ExtJS directly. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload