Michel,

Unfortunately, deploying a .NET web application is not quite as simple as copying the appropriate files to a web directory. It sounds like this is the first .NET application that will be installed onto your client's IIS server, so you will have to do a lot of configuration of IIS to get it working.
The basic steps are:

1. Create a web site for your application manually. Don't use the deployment project for this - the options available from the deployment project are inadequate for installing onto a Win2k web server.

2. Configure the web application settings in your new web site by clicking the Create button under the Directory tab in the properties of your web site.

3. If your project will only be used on your client's Intranet, you can enable Impersonation (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconaspnetimpersonation.asp) and skip steps 4-9.

4. Create a domain user account that will run your ASP.NET application (YOURDOMAIN/ASPNET is what most people use). Assign a password to this account.

5. Grant Read & Execute rights to ASPNET in your web root folder (usually Inetpub/wwwroot).

6. Grant Full Access rights to ASPNET in the WINNT\Temp and WINNT\Microsoft.NET folders.

7. Open the machine.config file under the .NET Framework folder on the web server. You may have two .NET Framework folders if you have both 1.0 and 1.1 installed on the server. If this is the case, perform the next steps on both files.

8. Locate the tag in machine.config and find the username and password attributes. Change the entries from "machine" and "Autogenerate" to "DOMAIN\ASPNET" and the password you assigned to the account.

9. Stop and Restart IIS on the web server to pick up the changes to machine.config.

10. Use the copy project wizard in VS.NET to copy the files from your development web site to the client's web site.

11. Set the default page for you web site in the IIS control panel applet.

Some extra info:

Never run the IIS lockdown tool on your IIS server after installing the .NET Framework. It will take days to undo the mess that the IIS lockdown tool creates.

You can use FrontPage Extensions 2000 & 2002 on your web site without affecting the .NET installation.

If you are using SQL Server databases in your application, make sure the ASPNET account has permissions in SQL Server - they are separate from Win2k permissions. Also, you will want to keep the Connection Strings for your SqlConnection in your application's web.config file. Check http://www.dotnetjohn.com/articles/articleid3.aspx for a nice example on how to do this.

Some parts of an ASP.NET application will not run correctly if the Application Protection (in your IIS web site properties) is set to Medium or High. I would not recommend changing the setting to Low unless you have confirmed that your ASP.NET application needs this setting.

I hope this helps. I know how frustrating deploying a ASP.NET application can be.

>Hi Jacci,
>
>Thanks for answer,
>Problem is too complex. My application use Crystal Reports for reporting and to make this work we need the same CR components on deployment machine(server). I don't know how to install these components manualy, then I use a setup project.
>If I can set all from IIS would be great but how...
>MM
>
>>Hi Michel,
>>
>>From what I understand, and I'm still really new at .NET, is you copy the application and all associated files to a folder on the server, then setup IIS. Or maybe the other way around. I've only had a class and haven't deployed a .NET web app yet.
>>
>>The nice thing with .NET is we no longer have to create "installations".
>>
>>HTH,
>>
>>Jacci
>>
>>>I have an application web coded in C#. I want to install this application on a client server. The problem is: the client server has several site with different IPs. The project setup made with VS.NET don't give any possibility to set the site or the IP.
>>>If anybody have some clue please share your knowledge...
>>>Thank you.