I've always heard that using the include directive outside of classic ASP is a bad idea, I have coded believing that statement, however in a recent arguement, I mean discussion, I had to admit defeat because I couldn't find any supporting documentation for why it's a bad idea. I found a couple places where microsoft said 'generally you should use user controls...' but nothing concrete and specific, and more disappointingly I found some articles that said there is no performance differance, and even one that said it increases performance to use an #include directive.
If this is the case then why are so many of us creating inherited pages for templates rather than using includes, or so many other things we do with user/server controls that we could use includes for? Blind ignorance? I personally like OO programming rather than typing html include files at the top of every page, changes are very easy...change the base class!, but not everyone works that deeply.
I know a few of you out there, if there is documentation, you have it... and I really hope today you have it.... thanks!
If this is the case then why are so many of us creating inherited pages for templates rather than using includes, or so many other things we do with user/server controls that we could use includes for? Blind ignorance? I personally like OO programming rather than typing html include files at the top of every page, changes are very easy...change the base class!, but not everyone works that deeply.
I know a few of you out there, if there is documentation, you have it... and I really hope today you have it.... thanks!