ASP vs ASP.NET

  • Thread starter Thread starter Petr Komarek
  • Start date Start date
P

Petr Komarek

All,

we are developing ASP pages using middle tier COMs written in VB and using
ADO. It is quite huge application and we are considering development of new
functionality in .NET. It means that the existing code (using COM and ADO)
will be executed side by side with new ".NET" code (using ADO.NET). New code
will reuse some of the existing COM components and it means that I need to
make sure there are no known "fatal" limitations related to combining
(passing data from ADO to ADO.NET ) ADO and ADO.NET.

I from MS that there should not be any problems with that but I would
appreciate any experience or if you know any useful article.

We are using MSMQ as well. Is there any known limitation or migration
problems related to the .NET ?

Thanks

Petr
 
I can't say for sure that there won't be any problems, but I can tell you
this....ASP.NET is much much easier to use and you can probably rewrite it
in a fraction of the code that you had originally. I rewrote an ASP app a
few months ago and reduce roughly 5,000 lines of code to just under 1,000
and got much better performance to boot. I was speaking with a guy at a
conference recently that said he rewrote an app of around 12,000 lines with
just over 1,200.

I've used MSMQ quite a bit in .NET and found it much easier to use. To
date, I've had no problem whatsoever and if I am faced with that choice
again in the future, I'd have no hesitation about switching to ASP.NET.

With that said, DataAccess is profoundly different with ADO.NET and you'll
probably want to rewrite your logic b/c ADO.NET is so different from old
ADO. You can definitely P/Invoke/ use Interop and wrap existing unmanaged
components... I've done this on the desktop, the web and Pocket PC and
haven't had any issues so far.

Since it's a large app, you are wise to proceed with caution but from my
experience, it's defintely worth doing.

HTH,

Bill
 
Back
Top