Assembly missing in GAC after Publish?

[Pieter]

Hi,

We're using ClickOnce alreaddy more than a year for a given applicaiton,
doing more than 50 publishes without any problem.

Yesterday we made a minor change to one of our components (let's say with
the name MyAssembly), and incremented it's version (AssemblyVersion: from
0.1.7.0 to 0.1.7.1). We did the Publish with ClickOnce, but when the users
know want to run the application they get this error:
"Unable to install or run the application. The application requires that
assembly MyAssembly Version 0.1.7.0
be installed in the Global Assembly Cache (GAC) first."
This is so weird, especially when knowing we had alreaddy inremented this
version number without any problems in the past.

Anybody has any idea? Your help will be really appreciated!
Thanks a lot in advance,
Pieter

[Pieter]

Aaargh never mind, I've found it:
What was actually happening was soem type of dll hell :-)
Another component in the project was referencing the same assembly, but did
it with a compiled version, not the source of the project. so when doing the
publish there was some conflict between the old one and the new one...

This conflict should be more visible in the output window when doing a build
:-)

"Pieter" <pi****************@hotmail.comwrote in message
news:%2******************@TK2MSFTNGP04.phx.gbl...

Hi,

We're using ClickOnce alreaddy more than a year for a given applicaiton,
doing more than 50 publishes without any problem.

Yesterday we made a minor change to one of our components (let's say with
the name MyAssembly), and incremented it's version (AssemblyVersion: from
0.1.7.0 to 0.1.7.1). We did the Publish with ClickOnce, but when the users
know want to run the application they get this error:
"Unable to install or run the application. The application requires that
assembly MyAssembly Version 0.1.7.0
be installed in the Global Assembly Cache (GAC) first."
This is so weird, especially when knowing we had alreaddy inremented this
version number without any problems in the past.

Anybody has any idea? Your help will be really appreciated!
Thanks a lot in advance,
Pieter

[kimiraikkonen]

On Jun 17, 12:15*pm, "Pieter" <[e-mail]:

Aaargh never mind, I've found it:
What was actually happening was soem type of dll hell :-)
Another component in the project was referencing the same assembly, but did
it with a compiled version, not the source of the project. so when doing the
publish there was some conflict between the old one and the new one...

This conflict should be more visible in the output window when doing a build
:-)

"Pieter" <[e-mail] in message

news:%2******************@TK2MSFTNGP04.phx.gbl...

Hi,

We're using ClickOnce alreaddy more than a year for a given applicaiton,
doing more than 50 publishes without any problem.

Yesterday we made a minor change to one of our components (let's say with
the name MyAssembly), and incremented it's version (AssemblyVersion: from
0.1.7.0 to 0.1.7.1). We did the Publish with ClickOnce, but when the users
know want to run the application they get this error:
"Unable to install or run the application. The application requires that
assembly MyAssembly Version 0.1.7.0
be installed in the Global Assembly Cache (GAC) first."

This is so weird, especially when knowing we had alreaddy inremented this
version number without any problems in the past.

Anybody has any idea? Your help will be really appreciated!

Thanks a lot in advance,

Pieter- Hide quoted text -

- Show quoted text -

Hi,
If you need to play with GAC manually, you can also refer to this
article:
http://support.microsoft.com/kb/315682

Thanks,

Onur Güzel

[Rich P]

Hi Pieter,

I have been using Click Once for nearly 3 years (since beta) without any
problems. When I make a change to an application and publish this
change - I increment the project in 3 places: in the Application tab of
Project properties I click on the Assemly Information button where I
increment the assembly version number and the file version number. Then
- in the Publish tab I increment the numbers that I have been tracking
(for me it has only been the revision number. So in all 3 locations all
the numbers match. This may not be the intended way, but I have not had
any problems doing it this way.

Another thing you can do is to go to the server to the directory where
all assemblies for your application get published and delete these
subdirectories and all their contents and then start the publishing
process all over again. The only thing is that you will have to
uninstall your application from all workstations using it first so that
they will get the new assembly.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[Nick]

Hi Rich,

Changing version numbers manually like that would definitely solve that
problem, but is much better being done automatically as it removes human
error from the equation, i.e. forgetting to update version numbers, it's a
gripe of mine.

I use automatic version numbers by using the wild card char...

Assembly Version,

[1] [0][*] [ ]

Then I only need to change major / minor as necessary, so it can be
ignored for quick changes. But then VS isn't so reliable with keeping
everything uptodate in my experience anyway :(

Nick.

"Rich P" <rp*****@aol.comwrote in message
news:eb**************@TK2MSFTNGP03.phx.gbl...

Hi Pieter,

I have been using Click Once for nearly 3 years (since beta) without any
problems. When I make a change to an application and publish this
change - I increment the project in 3 places: in the Application tab of
Project properties I click on the Assemly Information button where I
increment the assembly version number and the file version number. Then
- in the Publish tab I increment the numbers that I have been tracking
(for me it has only been the revision number. So in all 3 locations all
the numbers match. This may not be the intended way, but I have not had
any problems doing it this way.

Another thing you can do is to go to the server to the directory where
all assemblies for your application get published and delete these
subdirectories and all their contents and then start the publishing
process all over again. The only thing is that you will have to
uninstall your application from all workstations using it first so that
they will get the new assembly.

Rich

*** Sent via Developersdex http://www.developersdex.com ***