We\'re building a CMS. The site will be built and managed by the users in aspx pages, but we would like to create a static site of HTML\'s. The way we\'re doing it now is w
You could use wget (a command line tool) to recursively query each page and save them to html files. It would update all necessary links in the resulting html to reference .html files instead of .aspx. This way, you can code all your site as if you were using server-generated pages (easier to test), and then convert it to static pages.
If you need static HTML for performance reasons only, my preference would be to use ASP.Net output caching.