Hi!
I did a very simple experiment.
Create a Basic MSI project
It only installs one file adodb.dll to GAC.
The first time install, adodb.dll was successfully installed
to GAC.
When I run a major upgrade, it didn't install adodb.dll
any more.
Look at the log, it says
MSI © (48:40): skipping installation of assembly component: {B204FE63-0786-402E-B9B9-619DCA4667D9} since the assembly already exists.
adodb.dll is from Microsoft. The project is very easy to create.
If you like, I can send you the project. Almost all of it
is by default.
As a matter of fact, it is not only adodb.dll. Every .net assembly
going to GAC can be used to see this problem.
Why?
Thanks.
David
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
GAC and major upgrade
Started by
tester12
, Jan 28 2004 19:39
6 replies to this topic
Posted 29 January 2004 - 08:26
Apologies if I mixed something up but my understanding of Assemblies is:
Assemblies in the GAC need to be strong named.
If you build a new version of an assembly you need to assing a new strong name.
Assemblies in the GAC need to be strong named.
If you build a new version of an assembly you need to assing a new strong name.
Stefan Krüger
InstallSite.org twitter facebook
Posted 29 January 2004 - 18:10
Why is it a problem that it's not being overwritten then?
Stefan Krüger
InstallSite.org twitter facebook
Posted 30 January 2004 - 16:39
Stefan,
I attached both the old and upgrade installs.
They were created by Installshield developer 8.
Please build and run, you will see the end result.
Thanks.
David
I attached both the old and upgrade installs.
They were created by Installshield developer 8.
Please build and run, you will see the end result.
Thanks.
David