They are product description pages. I've been working with an SEO consultant who advised me that it is much stronger (for SEO indexing) to have actual physical pages vs one page that is dynamically changed based on a database entry. So, I have code that grabs the database info about each product and loops through a 'for each' method and writes pages using StringWriter. The pages all come out fine as I create the directives and properly formatted aspx pages and also create the codebehind pages. I just don't like the fact that I have to do this in the development environment everytime the database changes. I would greatly prefer to have the web application write out another page but don't see how I can then compile it outside of my IDE. Does that help clarify?
On Sep 21, 9:32 am, Cerebrus <[email protected]> wrote: > Why would you create physical pages (files) via code? I cannot get > past this assertion, let alone the rest of the question.
