I am tasked with updating a web app written in ASP.NET with a SQL server backend. The app consists of a large set of informational pages which are more or less a "book". There is also a CD version for handout that is just the set of static informational pages.

I am finding that the app needs a LOT of fixes for bugs and new features as well, and that having to keep the CD version in mind is really tieing my hands as far as how I can put the thing together.

For example, I wanted to use a templating scheme for the (header and footer, etc.) pages, but can't because it won't work on the CD. I actually can't use any .aspx page on the CD...only the .html pages...

I am basically looking for design suggestions or ideas for best ways to produce both versions. At this point I think separating the projects into 2 distinct versions/projects is the best way to go...


-------------------------
Beware of programmers with screwdrivers...

__________________
-------------------------
Beware of programmers with screwdrivers...

How about creating the dynamic, web server based .aspx version for the web, and then use a rip tool to generate the static, .html based version for the CD??

There are many tools available, like the old Teleport Pro and others. You probably need to strip some dynamic stuff(e.g. forms, search capabilities etc), but you'd get a decent start from "ripping" the site....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thanks that sounds like a great tool...I'll check it out!

-------------------------
Beware of programmers with screwdrivers...

You can get it here: http://www.tenmax.com/teleport/pro/home.htm

It's quite old, but it may work for you.

Also, take a look at Web Whacker: http://www.bluesquirrel.com/products/webwhacker/

I am sure there are many others; Googling a bit should bring up many other off-line browsing tools...

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.