that.
On Mon, Aug 1, 2011 at 3:00 PM, Paul Brook wrote:
> I checked the InstallExecuteSequence table and located the
> ScheduleStartRecorder action with this condition, which is correct:
> VersionNT<600 AND (NOT REMOVE~="ALL" OR UPGRADINGPRODUCTCODE)
>
I checked the InstallExecuteSequence table and located the
ScheduleStartRecorder action with this condition, which is correct:
VersionNT<600 AND (NOT REMOVE~="ALL" OR UPGRADINGPRODUCTCODE)
Here's the property:
Property(S): ScheduleStartRecorder = "C:\WINDOWS\system32\SCHTASKS.EXE"
/CREATE /F /TN "
s.
On Thu, Jul 28, 2011 at 2:53 PM, Hoover, Jacob
wrote:
>
> Paul,
> Just a guess here but is it valid to mix and match CData sections?
> IE, you could try changing:
>
> AND (NOT REMOVE~="ALL"
> OR UPGRADINGPRODUCTCODE)
>
> to
>
>
>
>
>
I have several deferred Custom Actions that are conditioned to run only on
XP or W7
All are using a variation on the same condition either
for W7 or Vista
or
for XP
Just to ward off any comments about Win 2000 and older this installer is
targeted for
hardware that our company makes and distribute
onents="True" OutputPath="$(OutputPath)" Path="C:\Program
> Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\" />
>
> Additionally an additional folder is created and the prerequisite is
> not included into the setup.exe
>
>
> Regards
> T
f
> product.xml and package.xml)
> C:\Program Files (x86)\Microsoft
> SDKs\Windows\v7.0A\Bootstrapper\Packages\YourPackage
> against
> C:\Program Files (x86)\Microsoft
> SDKs\Windows\v7.0A\Bootstrapper\Packages\SQL Server Compact Edition
>
>
> Regards,
> Tobias
>
Hi all,
I am attempting to build a bootstrapper for my wix installer in order
install another program our customer wants deployed along with ours. I've
been given the .msi file.
Here's the error / warning I'm getting:
warning MSB3155: Item 'Network.Configurator' could not be located in
'C:\Progra
nstalled).
The only way that happens is by making the component guids match. And the
best way to do that is to not autogenerate them, or if you must autogenerate
them, use "*" as the component guid values so that the binder will produce
the component guid values in a stable way.
-O
I am building a WIX installer that will have to upgrade a Visual Studio
deployment project .msi. When I run the major upgrade installer it replaces
the entry in the Program and Features list OK but none of the files are left
after the RemoveExistingProducts Before="InstallFinalize" (tried both Befo
9 matches
Mail list logo
