Any file that ends with .as## (.asax, .aspx, .asmx, .ascx), the .config file
and any .dll files. You may also have to move .disco, .js (custom), .css, if
you use them. You do not have to move source files, and it is unwise to do
so.
The easiest way to transfer is the Copy Project in Visual Studio .NET, as it
gives you the option to only move files that are necessary to run the
project. The app will have to already be set up on the production machine to
run. The copy can be through a file share (if you have proper NTFS perms) or
through FrontPage extensions (if installed and you are an author on the
machine). You can also create an installer, but I do not advise this
methodology as it kills xcopy deploy of web apps.
Not sure what you mean by the Directory option. If you have a web app set up
on the production machine, you are rolling after moving files. The app does
need scripting execution rights, and in Win 2k3, you also have to allow
ASP.NET to run. Whether it is anon access (default) or further restricted
does not affect the app running, except that only authorized users will be
able to use. If this does not hit what you need to know for IIS settings,
please rephrase the question and I will give more info.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
**********************************************************************
Think Outside the Box!
**********************************************************************