>>
>>Dmitry,
>>
>>The DLLs do not contain the HTML in the ASPX pages. It is necessary to copy the ASPX pages to the target web.
>>
>>Some other items:
>>
>>1. You have to make sure to flag the Virtual Directory as an application.
>>2. When you create the BIN folder, make sure that its security allows executable code.
>>3. You will probably want to copy the web.config file into the root of the target web.
>>
>>-------------
>>If you are working with VS.NET and use FrontPage extensions, it is really simple to do all of the deployment within the IDE.
>>
>>First, create a new Web Application on the target server. Then delete WebForm1.aspx. This takes care of creating the Virtual Directory and the BIN folder as well as configuring the web as an application and setting the IIS executable rights.
>>
>>Then, load up the source project and highlight the project in the Solution Explorer. Choose Copy Project from the Project menu. There is an option for copying only the files necessary for execution. VS.NET will prompt you to overwrite the files in the target web, choose Yes for all of the files.
>>
>>Viola! The files in the target web are all of the files that ASP.NET needs to run a web application.
>
>Keith,
>
>Thank you very much for the detailed instructions. I have already tested deployment on my pc today. And all works well.
>
>Now the big test is tomorrow when I will be deploying the app on the customer server. If you never see my name on the UT, it means they killed me <g>.

I hope your customer's server is already set up to run .NET applications. If not, there are a myriad of configuration and securuty issues in IIS and NTFS that you may have to set up before you can run your application.

I don't have my cheat sheet handy, but from memory you will have to:

1. Create a user account that the .NET process will run under.
2. Grant the user account read/write/create/delete rights to the C:\WINNT\Microsoft.NET folder & subfolders.
3. Grant the user account full control of the C:\WINNT\TEMP folder.
4. Set the machine.config processModel element to run under the user account.
5. Grant read & execute rights for the user account to the Web Site in IIS.

There are a couple more that I can't remember :( Perhaps someone else can post a link to the appropriate articles from MSDN or elsewhere.

Good Luck!