ASP: Use VB or VBScript???
Thanks much for the reply and info!
I thought as much, 'til I saw the following book title:
Visual Basic Developer's Guide to Asp and IIS
I have not looked at the book, so perhaps it just deals with writing COM
components in VB for use with ASP (though I thought any COM components
could be "used" within the ASP framework so why the specification in the
book title?) <shrug>
Also, I had considered the ActivePerl approach, but it's been my experience
that when playing in the MS sandbox, better to use the stuff *they* like. ;-)
Plus, all of the Perl/CGI that I have to port is all-about sys-admin, so unless
I use something like the MKS Toolkit (with it's NT-ported shell commands), none
of *that* would port.
Thanks again Randy!
>Sean C. Murphy says:
>>I am in the rudimentary stages of "porting" (yeah, right!) a set of
>>functionality currently implemented in Perl/CGI for Apache, to an
>>The little bit of ASP (cookbook stuff) that I'd done in the past was implemented
>>using VBScript. Is there a stock argument (or set of arguments) for using one or
>>the other to implement ASP functionality? Is there any compelling argument to be
>>made for employing VB proper over the Scripting Edition in implementing an ASP
>There is no way to use Visual Basic as a language for ASP.
>ASP uses the Microsoft scripting engine, which supports VBScript and
>JScript. Other scripting languages can be added, including Perl, so
>you may want to explore the idea of simply installing ActivePerl
>(available from www.activestate.com) and using PerlScript as your
>scripting language in ASP. That would make porting the code a hassle
>MCP+I / MCSE
>www.wshscripting.com for WSH scripts
>www.serverscripting.com for server scripts