ClickOnce and GAC

[Alhambra Eidos Development]

Hi all,

I have WinForms application .net 3.5. I deploy it using clickonce in
intranet with several client machines. I publish application in intranet web
server (http://desbiz/CarwinClickOnce).

In developer environment (my PC), my application uses GAC assemblies, like
Fk.Security.Common.dll v.1.0.0.0.

In tab Publish -> Application files in Properties of WinForms application
csproj, I set value Include for Fk.Security.Common.dll reference.


Now,

some client machines have Fk.Security.Common.dll v.1.0.0.0 reference in GAC

others client have NOT Fk.Security.Common.dll v.1.0.0.0 reference in GAC


If the client installs the winform application using ClickOnce there are
this issues:

1.) If Fk.Security.Common.dll v.1.0.0.0 reference is in GAC, the
Fk.Security.Common.dll v.1.0.0.0 reference included in ClickOnce not apply.

Problem: perhaps compilde code in Fk.Security.Common.dll v.1.0.0.0 reference
included in ClickOnce is more update than code in Fk.Security.Common.dll
v.1.0.0.0 reference is in GAC

Solution: uninstall Fk.Security.Common.dll v.1.0.0.0 reference in GAC, and
install in GAC the Fk.Security.Common.dll v.1.0.0.0 reference included in
ClickOnce Publish...

(how can I uninstall/install assemblies in GAC using ClickoNce????)

2.) If Fk.Security.Common.dll reference NOT is in GAC, the
Fk.Security.Common.dll v.1.0.0.0 reference included in ClickOnce apply. No
problem.

Any solution about this issues ??

Thanks in advanced.

 

[Andy O'Neill]

"Alhambra Eidos Development"

Has a versioning problem with GAC

My solution would be to avoid using the GAC.
Every client I have worked at where they tried to stick dll in the GAC it
resulted in a versioning nightmare.

If you have a rock-stable dll which will never ever change or some third
party software then yes,
If you might ever change your dll then no.

Sorry if that isn't what you wanted but that's my experience.