"Ben" <bensemo@hotmail.com> wrote in message
news:epSt8G%23zEHA.2540@TK2MSFTNGP09.phx.gbl...
> Hello
> I have a problem when I am trying to istall a MSI upgrde file.
> When I install this file when its not an upgrade it works just fine.
> The problem takes plcae when a previous version of my application is
> installed and I am trying
> to instal an Upgrade.
> In the Middle of the Upgrade installation i get this exception :
> System.IO.FileLoadException : strong name validation failed for assembly
> <filename.dll>
> when filename is the name of one of my dll's that holds some Custom code
> (install,uninstall,rollback,commit) for one of my MSM's.
>
> maybe someone know what can be the problem ???
>
> Thanks
>

"Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
news:usmF%231A0EHA.804@TK2MSFTNGP12.phx.gbl...
>I think this happens when you have custom actions that are running as your
>older version uninstalls, and the install is trying to call install custom
>actions in another copy of the same assembly. I'm not sure that the message
>is accurate, but it seems to be related to the install and uninstall both
>trying to load what is the "same" assembly into the same AppDomain to call
>custom actions. If the assembly naming attributes are identical in old and
>new versions, what happens if you change the assemblyversion in the new
>version of the product?
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]
> Definitive Guide to Windows Installer
> http://apress.com/book/bookDisplay.html?bID=280
>
> "Ben" <bensemo@hotmail.com> wrote in message
> news:epSt8G%23zEHA.2540@TK2MSFTNGP09.phx.gbl...
>> Hello
>> I have a problem when I am trying to istall a MSI upgrde file.
>> When I install this file when its not an upgrade it works just fine.
>> The problem takes plcae when a previous version of my application is
>> installed and I am trying
>> to instal an Upgrade.
>> In the Middle of the Upgrade installation i get this exception :
>> System.IO.FileLoadException : strong name validation failed for assembly
>> <filename.dll>
>> when filename is the name of one of my dll's that holds some Custom code
>> (install,uninstall,rollback,commit) for one of my MSM's.
>>
>> maybe someone know what can be the problem ???
>>
>> Thanks
>>
>
>