Clickonce deployment summary.

1: The path where clickonce is deployed on the client cannot be modified.
In C: \ Documents ents and Settings \ XXX \ Local Settings \ apps \ 2.0, XXX is the current user name

2: if there is a third-party DLL, to deploy it to the client, on the release page [application file (I )... ], the [release status] is [including] And then published to ensure that the file will be in the application. the path of startuppath.

3: some files will be stored in the [application file (I )... ]. The solution is to include these files in your project, such as some configuration files *. XML ,*. INI, which cannot be found in the DEBUG directory and must be included in the project.
If the [application file (I )...] still cannot appear, just change the attribute "generate operation" of the file to "content", then you can [application file (I )...] appears. The [release status] is [including] And then published.

4: If Excel or word is used for programming, you need to set stdole. DLL [release status] is [included], otherwise the client will be prompted that the Assembly Cache cannot be found, or when you install Excel, advanced options, put. NET programming support installation, this online search will know, here do not do a lot of instructions.

5: path problem. The local directory bin \ debug \ report \ 1.txt bin \ debug \ xx.exe
Customer installation path: bin \ debug \ report \ 1.txt xx.exe