The only issue I had, and it was minor, was migrating an extension from WiX 3.5
to WiX 3.6. I have had no issues with migration from WiX 3.6 onwards.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates,
I either table drive the custom action (usually) or if that doesn't really make
sense, I reference the properties in the custom action indirectly (using
properties set to properties).
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification
Are you using GACUTIL or the attributes on the File element to GAC?
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
You need to use the remember pattern to persist the value of the property from
the initial install to repair, upgrade, and uninstall.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS
That's because Imports are evaluated at PreBuild. In VisualStudio, that only
occurs on Solution load.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Shouldn't this:
CustomAction Id=Install_Driver Execute=deferred
Directory=InstallDir ExeCommand=quot;[InstallDir]DPInst.exequot; /PATH
quot;[InstallDir] Return=ignore /
Read as:
CustomAction Id=Install_Driver Execute=deferred
Directory=InstallDir ExeCommand=quot;[InstallDir]DPInst.exequot;
You can do some state testing of immediate custom actions using Lux. If you
concentrate on having most of the logic in the immediate custom action, then
unit testing of the deferred custom actions can proceed much like ordinary C++
or C# code. Lux mutation can be used to explore immediate
Provide the UpgradeCode and suppress upgrades in the MajorUpgrade element.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
Items folders.
Ah, thank you. I had tried ShortName but that didn't work. I should have gone
further to just Name.
What exactly is the difference between Name, ShortName, and LongName?
Thank you,
Christoph
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent
Set the Name attribute to the name you want.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From:
Well, it is far from ideal, but you could condition the components of mutually
exclusive ServiceInstall elements--one with the ServiceDependency and one
without.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry
I think there is some confusion. 1) util:ProductSearch works with Burn/Bundle.
Whether it will do exactly what you want (as pointed out by Phil) is another
matter, but it does work. 2) the standard ProductSearch is desiged to work in
the WiX schema and is not suitable for Burn/Bundle. 3) As
WIXUI_INSTALLDIR expects a property. Generally, it is statically set in the
Property Table. Probably what you want is to update the value of the property
at [WIXUI_INSTALLDIR]. If it runs before InstallDirDlg, you should be able to
just update the value of that property with the path.
A
See util:ProductSearch.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci
From the documentation:
The folder must be specified in the Property attribute as the name of a
property that will have a value that resolves to the full path of the folder
before the CostInitialize action. Note that Directory ids cannot be used. For
more details, see the Remarks.
Before
That is what SetProperty is for.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: ronif
Look at Component@/NeverOverwrite and Component@/Permanent.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original
What's in the inner text of Condition/Condition? Note that, unless the
Component is marked Transitive, that Condition gets evaluated only once. It
looks like the Component was not selected, and that would point to the
Component-Condition.
--
John Merryweather Cooper
Senior Software Engineer
You'll need to escape it. It's not showing on this end.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
It can be done through C++
https://msdn.microsoft.com/en-us/library/aa374177(v=vs.85).aspx
or practically any language with a WMI interface. Nice feature request to
implement.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Continuing
Development
Jack
Logs don't show much, but I just figured it out. Actually had to do with the
Dialog scheduling. Under certain conditions, the wrong dialog was loading--and
it was disconnected from everything else.
Weird that it only showed itself on 2012 R2, but weird happens. Even weirder
is no one in QA
and
Windows Installer Service 5.0
Can you upload your fix snippet for inspection?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: April-14-15 4:06 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MSI Buttons become Unresponsive on Server
Is A' a major or minor upgrade of A?
Is the ProductCode the same or different for A' and A? What is the difference
in version numbers?
What does the bundle log say when it is selecting A for removal?
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group |
Which version of the BA? Signature verification for payloads used to be the
default. The default is now hash verification which is less troublesome.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Continuing
Development
Jack Henry Associates, Inc.® |
From the documentation for MsiPackage@SuppressSignatureVerfication:
SuppressSignatureVerification
YesNoType
By default, a Bundle will use the hash of a package to verify its contents. If
this attribute is explicitly set to no and the package is signed with an
Authenticode signature the
...@jackhenry.com
-Original Message-
From: John Cooper
Sent: Tuesday, April 7, 2015 8:28 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] WiX vs. Microsoft Platform Ready
RBF Files -- Rollback Files. These should be deleted after a successful
upgrade. This should take
RBF Files -- Rollback Files. These should be deleted after a successful
upgrade. This should take place automatically without any special authoring.
Are you running your certification tool while the installer is still active?
The temporary directory entries are for each custom action. Never
They've been stripped off. You'll need to put them up at a location accessible
by URL.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
find the log files
MSI4c6af.LOG
https://docs.google.com/file/d/0B-yxrdSpoNNQR0ZGZ2xXQWdXNjQ/edit?usp=drive_web
MSI63f67.LOG
https://docs.google.com/file/d/0B-yxrdSpoNNQYmF0MG0tdE1VRzA/edit?usp=drive_web
On Fri, Apr 3, 2015 at 6:17 PM, John Cooper jocoo...@jackhenry.com wrote:
They've
]i000: Creating BA thread to run asynchronously.
[0CA0:0E1C][2015-03-30T15:42:51]i000: Launching Installation Interface
Thanks!!
Robin Lutteke
Van: John Cooper jocoo...@jackhenry.com
Verzonden: vrijdag 27 maart 2015 17:54
Aan: General discussion about
It will run the 4.x that is installed. 4.6 will be a superset of 4.5.2 which
is a superset of 4.5.1 which is a superset of 4.5 which is a superset of 4.0.
When you have one of these installed, all the earlier versions are superseded
and replaced.
--
John Merryweather Cooper
Senior Software
You need to make sure that the path to the library is in the list of paths
searched for libraries, and you need to make sure the library filename is the
list of libraries to be linked. Based on the discussion in the stackoverflow
link, I suspect the actual file name (msi.lib) to link is what
I believe it uses an algorithm to generate the GUID based on the KeyPath, but
that's just from memory.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Bootstrapper Prerequisite does not equal Product Prerequisite. If you're using
a managed bootstrapper (such as the WiX installer), it has its own .NET
requirements. If you have a custom bootstrapper written to .NET 3.5, then it's
a bug that you hadn't modified the prerequisite of the
+1. I like this approach.
From a security point of view, I would prefer a Local Group instead of
Everyone. Use the local group string in place of Everyone, and then add
share users to the Local Group. The converse of adding is that is allows you
to also remove users (and access) very
You need to have code to remember the value of the property so it is available
in uninstall and repair. See
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group |
Yes. It's not very complicated. The specific steps in the innermost custom
action (there is another custom action that drives this one from a table) are:
1) load path to XML file from property;
2) load XPATH from property;
3) create an XmlDocument instance
4) use the TrySafeLoad method to see
Are you trying to set properties from a deferred custom action? It looks like
it. Only immediate custom actions can set properties. I have an immediate
custom action that reads an XML file and sets a bunch of properties. But a
deferred custom action isn't going to have access.
--
John
Well, which sequence is the custom action running? UI or Execute? If in the
execute sequence, only public secure properties (properties in all upper case
with a Secure=yes attribute) will be visible in the UI sequence. If in the
UI sequence, are you firing this from a button, or is it just
for it to be
deferred.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, February 26, 2015 2:26 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] using a custom action to read properties from a XML
file
Are you trying to set properties from
that field with the data read from the XML.
Control Type=MaskedEdit Id=MacID Width=270 Height=15 X=52
Y=184 Property=MAC_ID Text=[MACIDTemplate] /
Control Type=Text Id=MacIDLabel Width=36 Height=10 X=11
Y=188 Text=MAC ID /
-Original Message-
From: John Cooper [mailto:jocoo
Is the UpgradeCode the same for each bundle or different? I keep it the same
and I have no problems.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Which is why I based my bundle version on one of the MSI's which gets bumped
every build.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
Agreed. Laid out that way, INSTALLLEVEL and the rest of the machinery will
work correctly.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
What are the file versions of the previous version and the upgrade version for
the files that are missing?
Also, look in a verbose log--you will see entries where the WIS has decided not
to replace because the upgrade would result in a downgrade by version.
If you use an aggressive upgrade
Have you considered instead using a shared component?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From:
1) This would be much easier to execute using Custom Tables.
2) Your ReadServiceAccount details is probably going to result in a subsequent
custom action that modifies machine state somehow. By scheduling
ReadServiceAccount after InstallFinalize, you aren't going to be able to do
much since a
a mistake I was too close to see.
From: John Cooper jocoo...@jackhenry.com
Sent: 30 January 2015 13:41
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Custom Action not be called
It is essential that managed custom actions have
It is essential that managed custom actions have an [CustomAction] attribute
for each method call that will be used as a custom action. E.g.,
[CustomAction]
Public static ActionResult DoSomething(Session session)
{
// code here
}
By having the Return attribute set to ignore, the errors that
Generally, I put my service authoring in the same component as the File element
referencing the service binary. That way, the KeyPath is the service binary,
and I don't have these issues.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
I have one product that has both x86 and x64 versions. They can be installed
side by side. Hence, I have two upgrade codes--one for the x86 and one for the
x64. The x64 upgrade only upgrades the x64 side, and the x86 only upgrade the
x86. I've been advocating for a bundle-driven install,
Need more information. What is the authoring for the component installing the
file? What is the actual path to the file in both A and B cases? In the
authoring, is the file the KeyPath, or is another file or registry entry the
KeyPath?
--
John Merryweather Cooper
Senior Software Engineer |
For server OS's, there is a PowerShell interface which can be wrapped in a C#
DTF custom action. This would be far preferable to running DISM directly.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.®
Because PROPERTY implies the property exists but has no value, but with
the Windows Installer Service, the property will be removed if it is empty.
Hence, NOT PROPERTY is the test that should be used.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Yes. Dark can be used to extract the payload.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Tunney,
How are you passing it to the installer? If on the command line, the directory
path needs to be delimited.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
installation via the UI.
Also, the application installs correctly in C:\Program Files(x86)\protop3 or
c:\My Apps\protop3. Everything works as expected EXCEPT this additional
directory that is created.
Paul
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January 9
-Original Message-
From: John Cooper
Sent: Friday, January 9, 2015 12:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Extra Dir Created When Install Dir Has Spaces
If it's done right, it shouldn't make a difference whether it is command line
or UI driven.
How is it set
attribute on a
well-known folder.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, January 9, 2015 11:13 AM
To: General
This is also necessary when accessing x64 areas of the file system. I have
64-bit versions of some of my custom actions when this is necessary.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® |
Yes, using the Binary Table. That's how sql:SqlScript does it.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
Note that you are subject to PowerShell execution policy. Before Server 2012
R2, the default was Restricted which will block all PowerShell execution
outside of a PowerShell Concole or ISE. Many networks have GPO that will
detect changes to the ExecutionPolicy and revert it back.
With Server
.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: ssmcs...@gmail.com [mailto:ssmcs...@gmail.com]
Sent: Thursday, December 18, 2014 10:08 AM
To: John Cooper
Subject: Heat over 64 bit dll
Hi Sir,
Can heat harvest a dll file which is a 64 bit ? I am
From: John Cooper
Sent: Thursday, December 18, 2014 10:44 AM
To: sampat magi
Cc: WiX toolset developer mailing list (wix-d...@lists.sourceforge.net)
Subject: Re: [WiX-devs] Heat over 64 bit dll
I used to do something like that when I worked at Microsoft. You need to be
careful that ID’s can
architectures, so
massaging the 32-bit output a little should be all that's required.
---
Phil Wilson
On Thu, Dec 18, 2014 at 8:21 AM, John Cooper jocoo...@jackhenry.com wrote:
Well, the general problem is that COM registry entries are going to be in the
32-bit hive (traditionally, COM
:|jocoo...@jackhenry.com
From: sampat magi [mailto:ssmcs...@gmail.com]
Sent: Thursday, December 18, 2014 11:23 AM
To: John Cooper
Subject: Re: Heat over 64 bit dll
Ahh!! okay. Thanks for the extended information. Please have a look at my below
query if you have time.
Recently i was creating
You need to escape them. Replace '[' with '[\[]' and ']' with '[\]]'.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original
I believe you're running into a change in Windows Installer Service behavior
caused by a Windows Security Update associated with KB2918614.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS
Registry will definitely work. I have a bundle with two MSI's--one of which is
pure registry. No problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Check boxes are NOT set to 0 when unchecked. Effectively, the property is
set to string.Empty which undefines it. The property will be set ONLY if the
check box is checked. To check for the property being unset, use NOT
VS2012CHECKED.
--
John Merryweather Cooper
Senior Software Engineer |
If you're looking for a nested MSI, that had not been support by the Windows
Installer Service for a long time.
If you want a Feature Tree interface on a bootstrapper, you'll need a custom BA.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
on the installer side. Meanwhile
if I set my property via code it works fine. The problem is that after that I
can't modify the state of the control during install.
Any clue?
Thanks
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Monday, December 08, 2014 17:47
/
_
Short replies here. Complete answers over there:
http://www.firegiant.com/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Wednesday, December 3, 2014 10:31 AM
To: General discussion for Windows
I think it is more important to be consistent. If it is my intent to trigger a
rollback, then I trap and log the exception and return ActionResult.Failure.
Otherwise, I generally log and rethrow. Sometimes, I am only interested in
setting or clearing a property. In that case, I trap
I'm seeing a weird error on three products that all use the WixStdBa to install
a single MSI.
Install goes fine.
However, attempts to Repair, Uninstall, or Upgrade result in:
0x80070057 - the parameter is incorrect.
This has only cropped up in the past two days, and the bundle authoring has
You need to change your MajorUpgrade@Schedule attribute to something like
afterInstallInitialize. This will ensure that the previous version is removed
before the downgrade version is installed. A downgrade like this won't allow
you an overlapped upgrade.
--
John Merryweather Cooper
Senior
1) you'll need a custom boostrapper to support that functionality. The
standard bootstrappers have no idea what to do with a feature;
2) along those lines, you would suppress the MSI UI and have the bootstrapper
handle the feature selection;
3) features are a pain. For my own work, I am
Indeed it is a Microsoft Windows constraint. A 32-bit process is not permitted
to modify 64-bit resources.
For example, I want to set some ACLs in the C:\Windows\System32 tree. This is
a 64-bit location on a 64-bit OS. From a 32-bit custom action, the files in
that 64-bit are all but
What are the remaining ACL's to assign?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: ssmsam
They can be used in patch generation. Other than that, I haven't found them
very useful.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
Yes, but at a much lower level.
See util:PermissionEx
For users, some permissions are set in the util:User element.
I don't set or clear GPO during an install because: 1) they'll generally roll
right back in; and 2) removing a GPO doesn't necessarily remove the
restrictions it imposes.
--
Yes, with MSBuild.ExtensionPak (4.0.9.0 is current). It's also not hard to
write an MSBuild task that will do it easily.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext:
can't explain it simply, you don't understand it well enough. - Albert
Einstein
On Tue, Nov 18, 2014 at 9:02 AM, John Cooper jocoo...@jackhenry.com wrote:
Yes, with MSBuild.ExtensionPak (4.0.9.0 is current). It's also not
hard to write an MSBuild task that will do it easily.
--
John
Yes, you could do that. Or you could put them in wixlibs and link those in.
All of my custom actions live in two wixlibs.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext:
My suggestion is simple: don't use Heat for production work. It's great for
prototyping, but when it comes time to patch your product, you'll wish you
hadn't. It also tends to hide versioning errors that will come back to bite
you on upgrades.
--
John Merryweather Cooper
Senior Software
Pre- and Post-BuildEvents are for people that are afraid of XML. You have far
better control, and it will be ultimately much more reliable, if you use a
BeforeBuild target and just build it in to your csproj. The main thing you
have to be careful of is that the exact timing when two given
Hmmm. You shouldn't have to harvest file by file for heat. The usual practice
is to harvest part or all of a tree. You can use an XSLT transform passed to
Heat to add the assembly attribute if this is necessary.
That being said, it is very unusual to push the majority of a product's
Google is your friend . . .
Although what is being done with the transform is the height of silly (setting
KeyPath=no), the principles are the same:
http://stackoverflow.com/questions/8034798/wix-installer-using-xslt-with-heat-exe-to-update-attributes
--
John Merryweather Cooper
Senior
No, if you have a deferred custom action (and all your custom actions that
modify machine state should be deferred), then you only need to provide a
matching rollback custom action (and proper scheduling) to provide that
functionality.
--
John Merryweather Cooper
Senior Software Engineer |
1) immediate custom action since it does not change machine state (and you want
to set properties);
2) have an input property containing either the possible domain account or a
reference to a property containing the possible domain account;
3) use C# in the usual manner -- you can adapt code
That is the technique I use and it is necessary when access 64-bit-only file
system locations and the like.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Yes, with a custom action.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Sourabh Bhandari
Probably because a German Windows 7 has a localized NETWORK SERVICE. What is
the name of NETWORK SERVICE on the German machine? Should be pretty obvious
from just looking at running services.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
These properties in the Util extension may also be useful:
Fragment
Property Id=WIX_ACCOUNT_LOCALSYSTEM Secure=yes /
CustomActionRef Id=WixQueryOsWellKnownSID /
/Fragment
Fragment
Property Id=WIX_ACCOUNT_LOCALSERVICE Secure=yes /
CustomActionRef
This message has been marked as General Business by Steven Ogilvie on
November-12-14 12:10:52 PM.
The above classification labels were added to the message by TITUS Message
Classification.
For more information visit www.titus.comhttp://www.titus.com/.
From: John Cooper-2 [via Windows
How is this installer assembled? Is there a merge module involved?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original
No. Has to with the way WOW and the Windows Installer Service was implemented.
It's not Wix-specific at all.
At run time, the VersiontNT64 Burn variable is only defined on 64-bit OS's and
you can use this to choose which MSI's to run out of a chain.
--
John Merryweather Cooper
Senior
The property can be defined only once per link job if a duplicate symbol error
is to be avoided. So, yes, this could be the source of your problem. Perhaps
moving the definition of WixUI_Mode into a common file and using PropertyRef's
to bring in the definition could work. Probably would
From your log:
1) is 'SqlComponent' being selected for install?
If so,
2) What is the value of the property USEINTEGRATEDSECURITY from the verbose log?
Note that this property is going to have to be remembered for repair, upgrade,
and patching to work. Note also that it will currently only
I have a product with a similar requirement (it installs extensions to MS
Office in both 32-bit and 64-bit flavors). From a 32-bit install, you can ONLY
write 32-bit registry entries. I work around this issue using a Burn
bootstrapper that installs the 32-bit support with the product, and
1 - 100 of 628 matches
Mail list logo