Of course, here it is:
<Directory Id="TARGETDIR" Name="SourceDir">
<Directory Id="INSTALLDIR" Name="project">
<Directory Id="binaries" Name="bin">
<Component Id="MainExecutable"
Guid="XXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX">
....
<File Id="Fileocx" Name="File.ocx" LongName="SomeFile.ocx"
DiskId="1" Source="bin\\SomeFile.ocx" Vital="yes"/>
......
It is an update from installer version x.y.1 to x.y.2, ocx file has same
internal file version, but has internally minimal changed (uuid),
and is not updated. 'File'-Entry is the same for both installer versions.
Regards,
Michael Musenbrock
Sebastian Brand schrieb:
> Can you post the relevant code from your .wxs file please?
>
> Best regards,
> Sebastian Brand
>
> Instyler Software - http://www.instyler.com
>
>
> On Apr 8, 2008, at 10:27 , Michael Musenbrock wrote:
>> Hi there!
>>
>> Msi do not update my binaries from Visual Studio.
>> (Especially one ocx and one exe file)
>> Even if the file has changed in the update, but the internal
>> version number of this file hasn't been updated, it is ignored,
>> is there a way to preserve this and get msi to updated my files?
>> If the internal version from the executable has been changed,
>> it works lika a charm.
>>
>> The package from wich it should be upgraded, has special
>> parameters in its 'File'-Section. (no checksum, or so).
>>
>> Hopefully someone can give me good news and a hint for that.
>>
>> Michael
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
