How to generate HTML pages

I suggest a Windows app. It will not necessarily be faster, but is just a better choice for this sort of thing. Generating XML and using XSL is certainly an option, but you'd need to be sure your target browsers will support it. Below is a snippet that could potentially be used to do this. You could have a table or XML config file of all of the URLs that you wanted to get and save as HTML and then loop through them. It needs to be made more robust, but may be a good starting point. Cheers, Dave ------------------------------------------------ // Initialize the WebRequest. WebRequest myRequest = WebRequest.Create("http://localhost/test/test2.aspx"); // Return the response. WebResponse myResponse = myRequest.GetResponse(); // Get response stream (the HTML of the requested page) Stream responseStream = myResponse.GetResponseStream(); // Set encoding Encoding encode = System.Text.Encoding.GetEncoding("utf-8"); // Pipe the stream to a higher level stream reader with the required encoding format. StreamReader readStream = new StreamReader(responseStream, encode); string htmlResult = readStream.ReadToEnd(); string savePath = @"C:\temp" + myRequest.RequestUri.AbsolutePath; DirectoryInfo di = new DirectoryInfo(Path.GetDirectoryName(savePath)); if (!di.Exists) { di.Create(); } FileStream fs = new FileStream(savePath, FileMode.Create); StreamWriter sw = new StreamWriter(fs, Encoding.UTF8); sw.Write(htmlResult); sw.Flush(); myResponse.Close(); fs.Close();

offtopic: If I were you - I'd use Perl, and not C#... For generating a lot of pages from database data - I always use Perl scripts... 1. they are always cross-platform, 2. they are usually faster, and need less resources...

In global.ascx, there's an event you can use - OnRequestEnd - that fires right before the response is sent to the client (HTML). You should be able to take the Response object and dump off a copy of the stream to your database. If it doesn't work from global.ascx as expected, check into using an HttpModule to setup a filter that fires on the same event, but it would be handled by a .dll that you would write.

Thanks for the suggestion. My only problem with that is that I will be generating about 3000 pages so you can imagine how long it would take to do each one individually. I really need something that is a bit more automated that means I can leave my PC creating and saving the pages while I do something else. Nick