Best way to build an internet application?

[(2b|!2b)==?]

I have a (3-tier) desktop application that I developed entirely in C++,
comprising mostly of Win32 Dlss as well as some ATL COM objects.

I want to "port the application to the internet", so that it can be run
over the internet - I'm sure there is more than one way to do this. BUT
- can anyone (preferably, someone with experience of doing something
like this) recommend what is the best way of doing this (or the way to
do this most succesfully/securely).?

Lastly, security is a very big factor, in that the application needst o
be secure - (imagine a banking aplication). Can anyone make
suggestions/recommendations regarding security?

 

[Cor Ligthert[MVP]]

Lastly, security is a very big factor, in that the application needst o be

secure - (imagine a banking aplication). Can anyone make
suggestions/recommendations regarding security?

Yea first find out what you mean with "Run over the Internet". Alone those 5
words can have 1000000 meanings, with a multiple of security riscs.

 

[(2b|!2b)==?]

Yea first find out what you mean with "Run over the Internet". Alone
those 5 words can have 1000000 meanings, with a multiple of security riscs.

By "run over the internet", I mean that the user does not need to have
any files locally (i.e. does not need to install the application on
their local machine), but can simply login to the application over the
internet, using a common browser (the application requires the user to
log in first), and then be able to access the various screens via menus
etc on the browser.

Technically, I want to replace the presentation layer (currently MFC
etc), with HTML pages.

 

[Morten Wennevik [C# MVP]]

Well, you might want to repost your question under a different title as you
are basically asking for the best way to build a web application, which as
Cor pointed out has 10000 correct answers as well.

If you can live with some (dll)files being stored locally you can take a
look at hosting WinForms inside internet explorer, or ClickOnce deployment.
You will then be able to have rich clients available through web. There is
also Silverlight (Microsoft's version of Flash) and regular web applications.
All of these supports storing files remotely although some work better in an
intranet environment rather than internet.

As for "the best way to convert a MFC application to web application", I
don't know, but as long as you have a clear separation of the GUI and
business logic, you should have plenty of options to chose from.

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

By "run over the internet", I mean that the user does not need to have any
files locally (i.e. does not need to install the application on their
local machine), but can simply login to the application over the internet,
using a common browser (the application requires the user to log in
first), and then be able to access the various screens via menus etc on
the browser.

Then you need a web app. Most possible you will have to rewrite your entire
app though.
Otherwise you will have to do a lot of interop calls.