So just to make sure I get it -- if you include them in the ClickOnce deployment, it doesn't work. If you just copy t hem over there, it does, right?

I have an idea you can try.

Zip up the dll's and add the zip file to your project. Deploiy the zip file but not the original dll's as separate files.

Have your application unzip the zip file "in place" before it does anything else.

That would accomplish getting the files there, and remove the dependency in the manifest on the specific dll's.

RobinDotNet

You get it.

I have added the dlls to a folder called dll_Resouces that is included in the build.
At application startup I am copying the files to the same folder as the exe. Everything works correctly. LOL.

Clickonce is not really ready for primetime, even in its third iteration.

This will work for now. But there must be a way through some logging findout why it is really failing.

Stewart

Hi stewart,

> on vista if i look at the installation folder many folders are created my unmanaged dlls are not in the same folder as the exe.

I would like to know what kind of folders does it created for you. Could you please tell me these folders�names? Are these C assemblies located in the same folder? Are these folders the subfolder of your EXE folder?

And I think Robin’s guide is correct. You can try to do it in Visual Studio and tell us if you meet any problem.

Sincerely,

Kira Qian

Do you just have a bunch of ClickOnce applications, or is that not the top folder under the two obfuscated folder names in the ClickOnce cache?

Sort it in descending order by date and find the one for your application, probably something like xxx....tion_

When you find that folder, double-click on the exe. Does the application run? Are all of the dll's there?

When you added them to the project, did you set the build action and copy options correctly? Did you go into the application files dialog and make sure they were all marked as Include or Include(Required) ?

RobinDotNet

Ok I have tried to run the application directly from the folder in the apps path. The application behaves the same way that it does when launched via clickonce.
If I rename the exe.manifest file to something else and launch the application from this folder it works as expected.
It looks like some kind of security problem.

The application is set for full trust in the security page.

I have included the begining of manifest file below.

Any Ideas?

<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:co.v1="urn:schemas-microsoft-com:clickonce.v1">
<asmv1:assemblyIdentity name="StageSoft.AudioMan.exe" version="2.1.3223.7463" publicKeyToken="a91906aada3060a1" language="neutral" processorArchitecture="msil" type="win32" /><description asmv2:iconFile="AudioMan.ico" xmlns="urn:schemas-microsoft-com:asm.v1" />
<application />
<entryPoint>
<assemblyIdentity name="StageSoft.AudioMan" version="1.4.2223.7464" publicKeyToken="A91906AADA3060A1" language="neutral" processorArchitecture="msil" />
<commandLine file="StageSoft.AudioMan.exe" parameters="" />
</entryPoint>
<trustInfo>
<security>
<applicationRequestMinimum>
<PermissionSet Unrestricted="true" ID="Custom" SameSite="site" />
<defaultAssemblyRequest permissionSetReference="Custom" />
</applicationRequestMinimum>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<!--
UAC Manifest Options
If you want to change the Windows User Account Control level replace the
requestedExecutionLevel node with one of the following.

<requestedExecutionLevel level="asInvoker" uiAccess="false" />
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />

If you want to utilize File and Registry Virtualization for backward
compatibility then delete the requestedExecutionLevel node.
-->
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>


Thanks


Stewart

Hi Stewart,

Thank you for posting me the detail information.

> It looks like some kind of security problem.

When your application needs to call unmanaged code (C or Win32 APIs), it does need more permissions than “Zone Default� But the “full trust�is enough to run the app. When I tested it on my computer, calling Win32 APIs return security limitation message. But I can overcome it under full trust condition. So the issue cannot be reproduced at my side.

Do you have any special reason to use ClickOnce? If not, what about thinking of other deployment technology?

Another idea is you can try to deployment your application via MSI. When using MSI, you can let your user decide where they want to install. MSI won’t create that long name folder and place your C assembly into other folder. I think that can avoid the problem. But MSI doesn’t have auto update feature as ClickOnce. So you may take that into consideration.

Reference

Walkthrough: Deploying a Windows-based Application

http://msdn.microsoft.com/en-us/library/k3bb4tfd%28VS.80%29.aspx

Sincerely,

Kira Qian

Kira,

Can he elevate permissions in a ClickOnce application? I thought ClickOnce apps wouldn't do that, because they are install-able with not admin privileges. Does having admin privileges mean they CAN elevate permissions even in a CLickOnce application? Isn't that what it looks like his manifest is trying to do?

Thx,
RobinDotNet

So just to make sure I get it -- if you include them in the ClickOnce deployment, it doesn't work. If you just copy t hem over there, it does, right?

I have an idea you can try.

Zip up the dll's and add the zip file to your project. Deploiy the zip file but not the original dll's as separate files.

Have your application unzip the zip file "in place" before it does anything else.

That would accomplish getting the files there, and remove the dependency in the manifest on the specific dll's.

RobinDotNet

You get it.

I have added the dlls to a folder called dll_Resouces that is included in the build.
At application startup I am copying the files to the same folder as the exe. Everything works correctly. LOL.

Clickonce is not really ready for primetime, even in its third iteration.

This will work for now. But there must be a way through some logging findout why it is really failing.

Stewart