In this question the OP implies that he wants to base the blog system he is developing on automatic creation of .aspx files, one for each new blog entry. In my answer to his question (which is related to something else), I told him that I would discourage him from using such an approach, but without giving any real reasons. He is now wanting reasons why it is not a good idea, and I'm using this question to see if the community can come up with a compelling enough list of reasons for him to use another approach, such as one using a dbms, code-reuse, url-rewriting, MVC, and what not.
There are two broad kinds of CMS publishing platform:
- Those who generate the content statically. Some publishing platform generate the content statically. In this case the generated files are not dynamic and should be HTML files. The system must have the ability to regenerate everything, for instance, if a template changed. There was a time when this solution had some advantages:
- security: security is managed at the file system level
- search: fulltext search was easy because everything was file-based
- performance: uses less CPU.
- interactivity: not possible
- content dissemination: the only reason now to build or choose such platform is if content need to be disseminated through other channel than the web, e.g. CD, downloadable journal, etc.
.
- Those who render the content dynamically. For web site, the easiest way is to render the page dynamically.
- security: security can be checked using complex scheme, etc.
- search: search system have evolves and integrate nicely with heterogeneous sources now: can be full text in database, files, etc.
- performance: this is no more an issue.
- interactivity: this is a lot more flexible: content can be adapted to the visiting user, people can rate the page, add comment, etc.
- content dissemination: needs to be online, of course
A hybrid system were you generate statically file that will be rendered dynamically (.aspx) is to me a non-sense -- it has the disadvantages of both.