Has anyone taken a VB6 application and rewritten it using ASP.NET? Would it run more efficiently as a "group" of web pages rather than a large executable? I don't know anything about ASP, so I am just wondering.
Printable View
Has anyone taken a VB6 application and rewritten it using ASP.NET? Would it run more efficiently as a "group" of web pages rather than a large executable? I don't know anything about ASP, so I am just wondering.
Well, it depends on type of application. As you know Windows based (or desktop if you will) apps are much more flexible in terms of gui design so if you have complex gui then it's not a good idea to migrate to browser based application.
If gui are not complex then it may make some sense if you need to do some major upgrade so it could be simpler to re-write the entire thing from scratch. But again, you will have to decide what's better for your business - borwser based app or windows based.
In my opinion there is no absolute YES or NO in this case - you have to do lots of analisys and testing to see which approach is best under sircumstances.
I was thinking in terms of:
1. Not every user uses every part of the app.
2. Only load up small "sub" apps rather than a 10mb exe file (of which not all is used).
3. A GUI that people have grown used to.
I couldn't have, and no one else could have, said it better.Quote:
Originally Posted by RhinoBull
Perhaps whipping up a prototype would be beneficial before starting any hard core coding.
10MB is nothing these nove days really. :) But you may give it the try by splitting you app into some smaller logical units first. The you may try prototyping to see how looks, navigates, performs (this one is more important then the others) vs the old destop app.
ps, I think this thread "belongs" to a General Dev forum rather...
Great minds think alike. :DQuote:
Originally Posted by RhinoBull
Moved.
It probably belongs elsewhere. However, since its root is in VB6, I thought this learned group may have "toyed" with the idea before.
If you are only worried about the memory usage, then the best thing to do is split parts of your Exe into DLL's/OCX's, and only load those parts as needed.
True enough, I guess.