We have a website that uses '#include file' command to roll info into some web pages. The authors can access the text files to update things like the occasional class or contact information for the department.
My question is this, I don't see anyone using this method and wonder if it is a good idea to keep using it. If not, what method should I transition to instead?
If you are using ASP.NET then you could bundle that code into a nice little UserControl that will display all of the important information.
Other platforms should allow you to bundle the logic into a class object, and display it using that.
It really depends on the platform that you are using to deploy the application in. The include file could be your best solution if you are deploying in a more limited platform.
RZachary, It is a very limited deployment. It is very bare-bones (i.e. one file per page sort of web 1.0 site).
@Keng Then using the #include file may be your best bet, particularly because it will allow you to encapsulate the logic of that rolled information, so that you won't have to go into the main page to add additional information to the contact info. You can just go into the .shtml page that is being used for the display and make changes.
Hope this helps.
I don't think there is anything wrong with it, and I've done some similar things with PHP. If the people that make the changes are comfortable with how they do it and they can do what they need to, I think you should stick with it. There could be some retraining involved and/or a fair amount of work involved for changing the system.
To Patrick, Thanks for the explanation. I was afraid it was going to do some odd code thing till I saw the c# tag. You're right it did mean to use 'include' ;0)
I just typed my note in the "Edit Summary:" text box. Do you not have that when you edit someone else's post (I obviously don't have that ability yet)?
Thanks!