Hi Linda,

Yes, I followed the process you described and theproblem is not solved.

Would you provide a copy of test solution to me?
--
Kenneth Lemieux
Project Engineer
Whelen Engineering Co., Inc.


"Linda Liu[MSFT]" wrote:

> Hi Kenneth,
>
> Thank you for your response, but I may not understand what you mean exactly.
>
> Do you mean that you have followed the process I described but the problem
> is still not solved?
>
> I have performed a test on the steps I gave you in my previous reply and it
> works well on my side, i.e. the ClickOnce application can be installed
> properly without any error.
>
> In addition, I noticed that there're two errors when the exe.manifest file
> is validated in your scenario:
> + Application manifest is not semantically valid.
> + File association default icon "wecan32.ico" must be listed as a
> non-optional <file> element.
>
> Please make sure that in the Application Files dialog(Project
> Designer->Publish tab->Application Files button), the "Publish Status" of
> the file "wecan32.ico" is set to Include and the "Download Group" is set to
> "(Required)".
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
>

Hi Kenneth,

I have sent my test project to your email box.

If you have any question, please feel free to let me know.

Sincerely,
Linda Liu
Microsoft Online Community Support

Hi,

I have solved the problem with my manifest.

The manifest did include the icon file, it is shown below.
<file name="Properties\Resources\wecan32.ico" size="3262">
<hash>
<dsig:Transforms>
<dsig:Transform
Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity " />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>hKQC+HwduEy3n7PERz4GD3tPgME=</dsig:DigestValue>
</hash>
</file>

Now looking at my fileAssociation element from my original post:

(<fileAssociation xmlns="urn:schemas-microsoft-com:clickonce.v1"
extension=".wcn" description="WeCan Configuration"
progid="WeCan.Configuration" defaultIcon="wecan32.ico" />)

notice there is no path associated with the specified icon file. Therefore
no file element exists and the deployment failed.

By changing the defaultIcon attribute of the fileAssociation element to:
(defaultIcon="Properties\Resources\wecan32.ico") the icon property was able
to be resolved and installation compete.
--
Kenneth Lemieux
Project Engineer
Whelen Engineering Co., Inc.


"Linda Liu[MSFT]" wrote:

> Hi Kenneth,
>
> I have sent my test project to your email box.
>
> If you have any question, please feel free to let me know.
>
> Sincerely,
> Linda Liu
> Microsoft Online Community Support
>
>

Hi Kenneth,

Thank you for your update and sharing with us the solution to solve the
problem!

It will definitely benefit all of us!

Thank again for your contribution to this newsgroup!

Sincerely,
Linda Liu
Microsoft Online Community Support