Web enabled application development

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • JH

    Web enabled application development


    I am trying to convert a GUI based windows application
    developed in C++ into the same web enabled application.
    My questions are:

    1. .NET proveds VB and C# as default languages for web
    application in ASP. Am I right?

    2. What are the general steps involved in porting all the
    work done in the GUI based application?

    3. Can somebody suggest a faster and reliable way of
    handling such tasks ?

    I am really in need of an urgent help inorder to grasp
    the overview of such webifying process.
    Thanks
    John
  • Kevin Spencer

    #2
    Re: Web enabled application development

    Hi John,
    [color=blue]
    > 1. .NET proveds VB and C# as default languages for web
    > application in ASP. Am I right?[/color]

    Actually, VB.Net and C# ship with Visual Studio.Net. There are, in fact,
    quite a few languages now for .Net development Visual Studio.Net 2003, for
    example, also ships with J#.
    [color=blue]
    > 2. What are the general steps involved in porting all the
    > work done in the GUI based application?[/color]

    Not sure what you're asking here. It's not a matter of "porting" as you're
    not porting over an executable to a different platform. You're creating an
    entirely different sort of application from your executable. A web
    application is about as far from an executable as you can get. It uses HTML
    for its' interface, and the interface and back-end are completely
    disconnected from one another, to such an extent that you actually have to
    rebuild all your server objects with each PostBack from the client. This is
    due to the stateless nature of HTTP. In addition, there are quite a few
    limitations imposed by the nature of HTML, the browser interface, and HTTP.
    You may have to re-design your interface quite a bit.

    What you really need to do is to analyze your executable, figure out how to
    "map" (ore re-design) interface elements from it to the appropriate HTML,
    and, depending upon the structure of the internals of your executable,
    either re-write them in .Net, or possibly re-use them (you can use COM
    interop, for example, to avoid having to rewrite any COM components of your
    executable).

    HTH,

    Kevin Spencer
    Microsoft FrontPage MVP
    Internet Developer
    All hotels in Benidorm. The best selection of Benidorm hotels with reviews and maps. Book in advance and save.

    Big things are made up of
    lots of Little things.

    "JH" <yhcontact@yaho o.com> wrote in message
    news:0ba101c33c b8$d11f14f0$a40 1280a@phx.gbl.. .[color=blue]
    >
    > I am trying to convert a GUI based windows application
    > developed in C++ into the same web enabled application.
    > My questions are:
    >
    > 1. .NET proveds VB and C# as default languages for web
    > application in ASP. Am I right?
    >
    > 2. What are the general steps involved in porting all the
    > work done in the GUI based application?
    >
    > 3. Can somebody suggest a faster and reliable way of
    > handling such tasks ?
    >
    > I am really in need of an urgent help inorder to grasp
    > the overview of such webifying process.
    > Thanks
    > John[/color]


    Comment

    Working...