![]() |
|
#1
|
|||
|
|||
|
When I create a new Basic MSI project, add a .NET 2.0 assembly, set it's location to the GAC, build a release, install and unstall: the assembly is not removed from the GAC.
When I open the MSI-file in InstallShield and look at the MsiAssemblyName table there are rows with 'Name', 'Version', 'PublicKeyToken', 'Culture' and 'FileVersion'. .NET 2.0 requires that a row with the 'ProcessorArchitecture' is supplied. That why uninstall fails. Manually adding a 'ProcessorArchitecture' row solves the problem. Is there a way to let Installshield add a row 'ProcessorArchitecture' automatically'? IS 11.5 supports .NET 2.0 so it should be possible. Thanks |
|
#2
|
||||
|
||||
|
We definitely want to track this down and fix it. I just performed an inconclusive test with Microsoft.Build.Framework.dll, as we didn't include the processorArchitecture but Lutz Roeder's .NET Reflector doesn't show it either. However http://msdn.microsoft.com/library/en...mbly_table.asp suggests all these values are available in the manifest; which I would have hoped we were implicitly referencing. Do you have the processorArchitecture value set in your assembly's manifest?
__________________
Michael Urman - Senior Software Engineer - Flexera Software: InstallShield Team |
|
#3
|
|||
|
|||
|
No it is not set:
// Assembly Ascon.Common, Version 1.0.2137.22546 Location: F:\Ascon\Common\Ascon.Common\bin\Release\Ascon.Common.dll Name: Ascon.Common, Version=1.0.2137.22546, Culture=neutral, PublicKeyToken=2088aa7ba8a49089 I don't know whether/how I can set it manually, but I shouldn't, should I? |
|
#4
|
|||
|
|||
|
Another problem:
Upgrading/patching doesn't remove the old assembly from the GAC. Anyone? |
|
#5
|
|||
|
|||
|
I have this problem too.
My MsiAssemblyName table is empty. Do I have to manually populate this table? And the table doesn't have a PublicKey column. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|