I, too, have been playing around with ASP-Fusebox, and I am using
server.execute("file_to_include.asp") instead of <!--#include
virtual="file_to_include.asp" --> (available to IIS 5) This reduces the
amount of extraneous code that gets included in the program when you are
trying to use conditionals, like the "Select Case" statement in the
default.asp.
I am also using Jeff's FormURL2Attributes.asp to convert my request vars. I
have noticed, however, that you can shortcut to an ASP request variable by
writing "request('variable')", which accesses either
request.form("variable") OR request.querystring("variable"). Any reason to
use the attributes scope? I'm running into the same issue with PHP, where I
can't CF_Module to a fuse app anyway, so there doesn't SEEM to be much point
in using the attributes scope. Any arguments the other way? I'd love to
hear what others have to say.
Thanks,
David Huyck
[EMAIL PROTECTED]
> Hi John. I read a little of the white paper you adapted from Steve Nelson
> for ASP. What do you do about rescoping variables to the attributes scope?
I
> ended up using the dictionary object to create an attributes collection.
It
> may have been someone on this list that suggested it. I can't remember. I
> created a FormURL2Attributes.asp that converts all the Request.Form and
> Request.QueryString variables to the attributes scope. I call
> FormURL2Attributes.asp from app_globals.asp.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
