I'm an experienced C/C++ programmer moving into ASP.Net website design.

Note: its the design issues more than the prog issues that I need help 
most with.

I have the ff questions:

1). WYSIWIG design
When designing forms via the WYSIWYG designer, how can you be sure that 
it will display correctly on (almost) all screen types (i.e. different 
screen heights/widths etc)?

I would like to use the Designer if it means I wont have to learn CSS 
(bcos designer is quicker, and I need to get a proj up and running ASAP).

2). How may I 'retrofit' CSS to a website - i.e. I have a website that 
was developed by an ASP.net programmer. he was a good programmer but he 
has NO eye for design. I would like to get a traditional website 
designer to redesign the website using CSS. Is it possible to take a 
copy of the static website (i.e. a snapshot of the gernrated pages) and 
give that to a website DESIGNER, along with "excel mockups" of what the 
the pages should look like, so he can he can write the required CSS 
fuiles to position everything correctly on the pages, I will then take 
the CSS files and 'link' them back into my dynamic pages - will this 
work ? has anyone done this before ?


3). The MS ASP.Net site has several sample website toolkits. I notice 
thoug, that the sample websites contain db schema (and possibly queries 
etc) under the 'App_Data' folder. The tables are obviously generated 
when the website is viewed in the browser (I am guessing that this is 
the case - because the apps throw an exception when the SQL Server 
engine is not running). However, it is not clear to me where the 
generated tables are stored - what database are the tables stored in? 
(no database name is specified in the SQL schema - AND I cant seem to 
locate tables anywhere [using the table names in SQL statements]).
Are these temporary tables that are deleted after the website is no 
longer being displayed in the browser?)


4). Is it possible to prevent the ".aspx" extension being displayed in 
the web browser? (e.g. show http:/mywebsite.com/default INSTEAD of 
http://mywebsite.com/default.aspx)

5). Is it possible to NOT show the IIS directory structure in the URl 
(e.g. show http:/mywebsite.com/thepage.aspx INSTEAD of 
http://mywebsite.com/dir1/dontlookhere/thepage.aspx)  Or better still:
http:/mywebsite.com/thepage (no extension)

6).
Is there a way of showing a generic page for unhandled exceptions - and 
DEFINITELY not showing the stack trace (default) - this is a "gift" to 
hackers if they can see a stack trace and worse still the code snippet 
that threw the exception - I need a way to prevent that from ever being 
available to the viewing public at large.