H
hansiman
I use Application_Start in global.asax to set some physical folder
paths ie.:
Application("pdf") = "c:\www\<site>\pdf\"
global.asax uses code behind.
When I move the project from the dev to the production server the
global.asax code behind is compiled into the project.dll (i guess).
This renders the physical paths unusable (naturally). Coming from
classic asp I thought I could just have a dev. and a production
global.asax.
Can I make the global.asax "not code behind"? Or should I use
web.config to store the paths instead? (a question of best practise, I
guess).
/morten
paths ie.:
Application("pdf") = "c:\www\<site>\pdf\"
global.asax uses code behind.
When I move the project from the dev to the production server the
global.asax code behind is compiled into the project.dll (i guess).
This renders the physical paths unusable (naturally). Coming from
classic asp I thought I could just have a dev. and a production
global.asax.
Can I make the global.asax "not code behind"? Or should I use
web.config to store the paths instead? (a question of best practise, I
guess).
/morten