Or perhaps something in here?:
<InstallExecuteSequence>
<Custom Action="DIRCA_CheckFX" Sequence="1" />
<Custom Action="ERRCA_CANCELNEWERVERSION"
Sequence="201">NEWERPRODUCTFOUND AND NOT Installed</Custom>
<Custom Action="VSDCA_VsdLaunchConditions" Sequence="399">NOT
Installed</Custom>
<Custom Action="DIRCA_TARGETDIR"
Sequence="750">TARGETDIR=""</Custom>
<LaunchConditions Sequence="400">NOT
Installed</LaunchConditions>
<FindRelatedProducts Sequence="200" />
<AppSearch Sequence="100" />
<CCPSearch Sequence="500">NOT Installed</CCPSearch>
<RMCCPSearch Sequence="600">NOT Installed</RMCCPSearch>
<ValidateProductID Sequence="700" />
<CostInitialize Sequence="800" />
<FileCost Sequence="900" />
<IsolateComponents
Sequence="950">RedirectedDllSupport</IsolateComponents>
<CostFinalize Sequence="1000" />
<SetODBCFolders Sequence="1100">NOT Installed</SetODBCFolders>
<InstallValidate Sequence="1400" />
<InstallInitialize Sequence="1500" />
<AllocateRegistrySpace Sequence="1550">NOT
Installed</AllocateRegistrySpace>
<ProcessComponents Sequence="1600" />
<UnpublishComponents Sequence="1700" />
<UnpublishFeatures Sequence="1800" />
<StopServices Sequence="1900">VersionNT</StopServices>
<DeleteServices Sequence="2000">VersionNT</DeleteServices>
<UnregisterComPlus Sequence="2100" />
<SelfUnregModules Sequence="2200" />
<UnregisterTypeLibraries Sequence="2300" />
<RemoveODBC Sequence="2400" />
<UnregisterFonts Sequence="2500" />
<RemoveRegistryValues Sequence="2600" />
<UnregisterClassInfo Sequence="2700" />
<UnregisterExtensionInfo Sequence="2800" />
<UnregisterProgIdInfo Sequence="2900" />
<UnregisterMIMEInfo Sequence="3000" />
<RemoveIniValues Sequence="3100" />
<RemoveShortcuts Sequence="3200" />
<RemoveEnvironmentStrings Sequence="3300" />
<RemoveDuplicateFiles Sequence="3400" />
<RemoveFiles Sequence="3500" />
<RemoveFolders Sequence="3600" />
<CreateFolders Sequence="3700" />
<MoveFiles Sequence="3800" />
<InstallFiles Sequence="4000" />
<DuplicateFiles Sequence="4210" />
<PatchFiles Sequence="4090" />
<BindImage Sequence="4300" />
<CreateShortcuts Sequence="4500" />
<RegisterClassInfo Sequence="4600" />
<RegisterExtensionInfo Sequence="4700" />
<RegisterProgIdInfo Sequence="4800" />
<RegisterMIMEInfo Sequence="4900" />
<WriteRegistryValues Sequence="5000" />
<WriteIniValues Sequence="5100" />
<WriteEnvironmentStrings Sequence="5200" />
<RegisterFonts Sequence="5300" />
<InstallODBC Sequence="5400" />
<RegisterTypeLibraries Sequence="5500" />
<SelfRegModules Sequence="5600" />
<RegisterComPlus Sequence="5700" />
<InstallServices Sequence="5800">VersionNT</InstallServices>
<StartServices Sequence="5900">VersionNT</StartServices>
<RegisterUser Sequence="6000" />
<RegisterProduct Sequence="6100" />
<PublishComponents Sequence="6200" />
<PublishFeatures Sequence="6300" />
<PublishProduct Sequence="6400" />
<InstallFinalize Sequence="6600" />
<RemoveExistingProducts Sequence="6550" />
<InstallExecute Sequence="6500" />
<MsiPublishAssemblies Sequence="6250" />
<MsiUnpublishAssemblies Sequence="1650" />
</InstallExecuteSequence>
-----Original Message-----
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 30 April 2012 01:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Protect installed msi files
Self-healing is a feature of the Windows Installer. There are several ways
to get it to kick in. The most common is through Advertised entry points.
You might decompile your old VS setup/deployment project and see if it has
things Advertised or otherwise organized differently.
You could also get a verbose log file from the repair operations and see
what was used in the past to kick off the self-healing.
On Sun, Apr 29, 2012 at 2:01 PM, Kristjan Laane
<kristjan.la...@gmail.com>wrote:
>
> Hello again
>
> When I used to create my msis through Visual Studio Setup and
> Deployment projects then these installers protected the files that got
installed i.e.
> if I installed the application and then manually deleted a file (such
> as an included image content file) then when the next time the main
> executable was run this deleted file got restored i.e. the msi was
> found in the Windows store and it repaired my installation.
>
> With Wix this protection is not present any more. I think that is
> better for some of the (optional) files that are installed, but I
> would like to protect some of my dll's as before - do you know how I
> could do that in Wix?
>
> Atb,
> Kristjan
>
> P.S. My msi's were always per machine, but now are per user, so this
> may be the difference that is actually causing the lack of protection?
> If that is the case, is it still possible to protect certain File /
> Component / Feature elements when deploying per user msi's ?
>
>
>
>
>
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
virtually, Rob Mensching - http://RobMensching.com LLC
----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
