Reply
Solved! Go to solution

IsolatedTaskProxy not working in ClickOnceDeployment

Hi,

i updated one of my tools to use the IsolatedTaskProxy from SolidEdge.Community extensions.

Everything works fine if i start the solution from Visual Studio.

When i install my tool from a ClickOnce deployment, the Backgroundworker doesn't work.

I checked running the app from the bin\Release folder and it works fine.

When i start the exe from the bin\Release\app.publish folder the same error occurs as with the ClickOnce published version.

I tested to set the option to "embed" the interop types for Interop.SolidEdge and SolidEdge.Community to TRUE in Visual Studio.

If i do so, Visual Studio marks the "Inherits" statement from my class.

 

How can i resolve that issue?

Greetings from Germany
Christian Kunkel
https://c-k-m.info
2 REPLIES

Re: IsolatedTaskProxy not working in ClickOnceDeployment

I changed something in the signing process. I will try later, if this has to do with the issue.

Greetings from Germany
Christian Kunkel
https://c-k-m.info
Solution
Solution
Accepted by topic author ckunkel72
‎03-14-2017 04:21 AM

Re: IsolatedTaskProxy not working in ClickOnceDeployment

[ Edited ]

Hello,

everything works fine again. Normally sign the ClickOnce deployment with my comodo codesigning certificate, but the smart screen filter still throws a warnig. I've read somewhere that this could be stopped if you sign the assembly too.

I tried to sign the assembly with a new keypair (my certificate can't be used for that), and i think this was the reason why the references get lost while deployment.

Now i only sign the ClickOnce deployment and it works like a charme.

Greetings from Germany
Christian Kunkel
https://c-k-m.info