>Frank,
>
>Tim has given you the best advice for setting this up, but I will attempt to just re-word it here. Basically, you need to create the web site in IIS. When you do that, at some point you will need to say where the files for the web site (or more appropriately web app) will be located. When you choose the 'Publish Web Site' option in VS, this will package all your web app files into this target directory you specify. You would then FTP that directory to the directory on the server you specified where your web app files exist.
>
>Therefore, creating a setup program is not necessary, however, you might want to use it as it gives you an ability to 'Install' your web appication on the web server using an install program. What is useful with this approach is that if you want to control what assemblies need to be included and installed in the GAC. If you use this install method, then I believe you might have to uninstall and then re-install every time you make an application change.
>
>I believe Tim likes to include all needed assemblies in the publish directory (in bin) therefore alleviating your need to create a setup program. This approach would seem easier especially if you web app will experience many changes.
>

Thanks Bob,

that's helped to clarify things. Just to understand the new terminology, an assembly is a DLL?

What I noticed when I published is that all the aspx files got copied to the specified folder. I had thought only my DLLs would get copied, but I guess my thought was wrong.