Peter J. Boettcher — Mon, 15 Oct 2001 15:26:30 +0000

Check out this link, it provides some great data: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnile/html/docu2kbench.asp

detox — Mon, 15 Oct 2001 01:57:46 +0000

Thanks for the help guys. If that is right about IIS5 then I don;t think I will worry. The main issue I was wondering about was scalability with regards to this.....

Peter J. Boettcher — Sat, 13 Oct 2001 23:35:31 +0000

Ahh, the age old debate, well not that old I guess...

Anyway, it really depends on what you're doing, and the platform. In IIS4 using COM produces much better performance over doing the same thing in ASP. With the release of IIS5, Microsoft really improved the ASP engine, and believe it or not it's actually faster to keep it in ASP than doing the same thing in COM.

Here's the BUT!

If you're going to be doing something more than calling a stored procedure or running a query or 2 then you should probably go with COM, it's hell to debug, but if written properly it will save you time down the road (since it's properties and methods can be used by another application)

Just remember that doing it in COM will add considerable time to the project.

Have fun!

VB and COM for web site

mycoolross — Sat, 13 Oct 2001 23:09:12 +0000

I am guessing this info will be stored in a database.
If this is the case you will be using a COM object and calling it from an ASP page then accessing the database.

Will the COM object use ADO?

If so you have an ASP page calling an object (Visual Basic)
this object will call another object (ADO).

This seems counter productive to me. You can just call ADO
from your ASP page. This creates one object as opposed to two. I think this would be more efficient.

Good Luck!

- Mike

Mark Hensler — Sat, 13 Oct 2001 17:11:51 +0000

Compiled VB would be faster than ASP. But I can't tell ya much more than that. I never really played much with compiling VB for web.