Doubts in Design Level. Desktop -> Web-Based conveting using .NET

[Guest]

Hi all,

We have one product. It is client/server based application. We
have developed client application in VC++ 6.0. Our client is desktop based
application like dialog based application. Client application will connect to
server according to user requests. This is current scenario.

We would like to make this application as a web-based
application. I have core functionality in VC++ application in client
application. I can put this functionality in com dlls also.

To achieve this web-based approach, what technologies I have to
select? Can you please advise me? I am planning to select aspx pages for
web-page and com dll for core functionality in VC++. Is it correct approach?
I have to give compatibility for Microsoft Windows NT/ 2000, Professional 98
SE to Windows Vista and windows 2003 server.

I will implement everything in .NET if .NET is correct
technology for this web-based application. But, I need to reuse my client
code in web-based application.

Please suggest me.

Thanks in advance

 

[bruce barker]

asp.net is not particularly com friendly. it expects the com objects to
be be free threaded (not apartment). also its not good about releases.
you should manually release all com objects (Marshal.ReleaseComObject).
also you should avoid implicit com references (two dots) as they will
not be released except by the GC.

if your com objects contain most of the logic, then you can host them
with com+ or create a web service for the asp.net to talk to.

you will find converting a desktop to web based app difficult if you do
not redesign the presentation layer to be web friendly and stateless.


-- bruce (sqlwork.com)