ClickOnce Install still requires interop assembly to be in GAC

Nov 26, 2014 at 10:18 AM
Hi, I created a VS2013 C# forms application. At first i used early binding to Outlook which worked fine on my machine. I created a clickonce installation and tried to install this on a machine running an older version of office. Ofcourse i got the error message that my version was not in the GAC of that machine. Hence, i needed NetOffice and so migrated my solution to use NetOffice and removed all references to the Microsoft interop office and outlook. All code and references are clean of any microsoft interop reference.
After rebuilding and deploying, i still receive the version conflict message while trying to install. Does NetOffice requires some kind of reconfigure?

Thanks in advance!
Nov 26, 2014 at 12:36 PM
hey men,

the problem is i have no experience with clickonce (because visual studio freeze on all my systems while compiling with clickonce. [i guess vs are not ready to handle missing network permissions)

What i believe for the moment is as follows: The NO assemblies use the PrimaryInteropAssembly attribute to fool the compiler because otherwise the compiler try to register the NO assemblies for COM in addin projects. (the compiler want do this for all COMVisible dependencies if used) It looks like ClickOnce thinks now an Primary Interop Assembly for Office is in use.

Sugessions for now:
1: Make sure in the reference settings for each NO assembly to set 'Embed Interop Types' to false(now the compiler suspend any registration but no idea about cklickonce)
2: Please send me a sample solution to public.sebastian[at] (remove private code but keep the NO assemblies) May i can find a solution to make NO finaly ClickOnce Ready.