Un able to install from click once deployment.

[moondaddy]

I have a VS 2005 winforms project and am trying to get clickonce deployment
working correctly. I published the deployment to a test server on my
network. It created the publish.htm and from my dev machine I can pull up
publish.htm from the browser and it seems to run OK. However, from a test
machine the installation fails. From the test machine I can pull up
publish.htm with no problem. When I click on the install button I get the
normal prompts such as this cert. is unknown (or something like that), and
another window asking me if I want to run the exe. I make it past all that
OK, then in the midst of the install process I get a error msg titled
"System Update Required". The msg box says "Unable to install or run the
application. the application requires that assembly
Infragistics.Shared.v5.2 Version 5.2.20052.1039 be installed in the Global
Assembly Cache (GAC) first."

The Infragistics v5.2 assemblies are .net 1.1, but that shouldn't matter
here. the run fine in this 2.0 project on the dev machine. In VS 2005 from
the publish tab where I setup the click once deployment, in the Application
files area I set the publish status to Include and download group to
Required for all Infragistics DLLs. Why would they need to go to the GAC.
in the past I've been able to copy all DLLs to a given folder on the target
machine and run the app with out installing anything (a clean client).

What's the recommended solution here?

Thanks.

 

[Gary Chang[MSFT]]

Hi,

The msg box says "Unable to install or run the application.
the application requires that assembly
Infragistics.Shared.v5.2 Version 5.2.20052.1039 be installed
in the Global Assembly Cache (GAC) first."

It appears your click once application referenced that strong named
assembly(Infragistics.Shared.v5.2 Version 5.2.20052.1039), which is located
in the GAC of your dev machine.

In such a scenario, this behavior is as expected. If your project
references a strong named assembly in the GAC, its released application
also needs that strong named assembly in the target client machine's GAC.

If you do not want to install that strong named assembly in the client
machine's GAC, I suggest you try to change that assembly's reference path
of its project:

1. Remove the reference.
2. Copy that strong named assembly to your project's local directory,
3. Add reference with the assembly which in the project's directory to
your project(use Browse.. to locate it)
4. Rebuild your project.

Wish this helps!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================