Hello Steven,
As i am thinking more about this, i am at loss to understand as to why would
i have to test the results of my immediate custom actions.
For all i know, if any code changes in the installer result in any
undesirable changes, i would either ways catch it during my unit testing
phase
Hello John,
Thanks for the response.
Couple of other questions though:
-How do you test the entries in AppSearch, RegLocator etc tables i.e the
data contained in standard tables in windows installer?
The msi built using Lux does not contain so many standard actions required
to process such
Hello Bob,
Thanks for assisting me with your answers.
Do you have any ideas on how i could achieve the following:
-How do you test the entries in AppSearch, RegLocator etc tables i.e the
data contained in standard tables in windows installer?
The msi built using Lux does not contain so many
The idea is that you have a variable of type WCA_TODO that's set normally,
then overridden in an #ifdef DEBUG block to whatever the mutation is.
I am sorry.. can one of you explain this in detail?
Where should this variable be set?
Kindly explain.
I am new to all of this.. so kindly excuse my
The idea is that you have a variable of type WCA_TODO that's set normally,
then overridden in an #ifdef DEBUG block to whatever the mutation is.
I am sorry.. can one of you explain this in detail?
Where should the variable WCA_TODO be set?
How would i make use of this in an #ifdef DEBUG
Hello Install gurus,
Could anyone tell me the difference between FileCost and CostFinalize
actions in the windows installer sequence tables?
The description in the MSDN tables is not very clear.
Also the dialogs are displayed after the CostFinalize action.
Does this mean that the costing process
Hello,
Could you let me know as to what issue are you facing?
Or do you just want a confirmation as to whether what you are doing is
right?
To preserve the file that you have mentioned here, there are two ways:
-Schedule RemoveExistingProducts after Install Finalize. This is more
efficient.
I guess what Phil is asking you to do is to make use of MoveFiles action to
accomplish what you want to do.
The MoveFiles action locates existing files on the user's computer and moves
or copies those files to a new location. The MoveFiles action queries the
MoveFile table and moves files
When you copy the modified file over to your new install location, the
upgrade wont overwrite it as it has been modified. You might want to read
the file replacement logic for unversioned files
http://blogs.msdn.com/b/astebner/archive/2005/08/30/458295.aspx
So here is the process:
-Copy the file
I have a similar problem as follows:
I am building a patch package using msimsp.exe from the windows installer
SDK. I make use of a patch creation properties file(.pcp) as part of the
patch building process. The .pcp file has the summary information properties
such as Title, Author, Subject,
Hello Phil,
Do you have any further inputs on what could be done to resolve this
problem?
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-set-Title-in-Summary-Information-Stream-tp709628p7589515.html
Sent from the wix-users
The documentation for PatchMetaData table lists few standard properites.
http://msdn.microsoft.com/en-us/library/aa370344(v=vs.85).aspx
I do not see anything mentioned for populating Title, Comments etc.
I even attempted building the patch by updating the .pcp file to include
the Title
Yes, i have used the DisplayName . I do not think that it corresponds to
Title in the summary information stream.
To be more clear, this is what i want populated:
-When you right click on a .msp file in windows explorer, there is a section
called Description under the Details pane.
-Under this
Hello All,
I am running into a strange issue with a major upgrade of an installer.
I have a bootstrapper which has around 5 .msi packages embedded inside.
The bootstrapper is a VC++ .exe with the requested execution level being
set to AsInvoker.
Let me explain my problem.
- I have
Thanks Blair for the quick response.
I should have been more clear.. What i meant was that all of the .msi
installers were configured for major upgrades.
I figured out the problem. The problem is with the bootstrapper C++ code.
One last thing: With AlwaysInstallElevated, when the installer runs
Hello,
Let me explain my scenario.
During the installation of my product, i need to install print drivers.
We make use of printui.dll to install the print drivers. The driver
package consists of an .inf file, .cat file and the files referenced in the
.cat.
Here is my scenario:
-I install v
Hello Carter,
Thanks for responding back.
Yes, i make sure that the driver is uninstalled before re-installation.
Its by design that whenever a driver is uninstalled, the actual files(.cat,
.inf etc) are not actually deleted from the Driver store. This is to enable
new devices which get
Thanks Phil. Much appreciated.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Strange-problem-with-printer-driver-installation-tp7591538p7591612.html
Sent from the wix-users mailing list archive at Nabble.com.
Hello,
I have a .msi package which sources certain component through merge
modules.Lets call this product A
This merge module is also part of another product and hence the other
product too contains the same set of components. Lets call this product B.
Consider a scenario where i install
*Getting the infrastructure in place to test custom actions is pretty tricky
(thus Lux exists).*
Could you please elaborate on this?
If i have to sell this idea to my management, what are the points to make
out in favour of Lux?
Thanks,
Kiran Hegde
--
View this message in context:
Thanks folks.
This is great information.
Let me digest this and ponder over it and see if i can put all the blocks
together.
Regards,
Kiran hegde
--
View this message in context:
Hello ,
Here is my scenario:
A higher version installer contains lower version of certain binaries . In
the higher versioned installer, sequencing RemoveExistingProducts
after InstallInitialize results in missing files. This is an issue with
Windows Installer service and has been
Folks,
Thanks for all the responses.
This issue happens even with normal files(not just assemblies)
MSI (s) (48:F0) [07:39:21:024]: Disallowing installation of component:
{4D2EB851-13AC-500F-9704-AB78102F8D0F} since the same component with higher
versioned keyfile exists
I dont want to
For all the problematic components, i see the following:
MSI (c) (14:9C) [16:11:09:263]: Disallowing installation of component:
{06F9816A-71E7-4B8E-860B-90E3BBF0B06C} since the same component with higher
versioned keyfile exists
MSI (c) (14:9C) [16:11:09:265]: Disallowing installation of
Hello,
Let me explain my scenario:
-I upgrage from V1 to V2 of my product using a major upgrade.
V1 has an entirely different upgrade code from V2. You can think that V2
now supersedes V1 and hence is like a different product family altogether.
Neither V1 nor V2 have any transforms
Hello all,
I am facing a strange problem where an assembly is not upgraded in the GAC
after a major upgrade.
V1.0 of the msi package contains v1.0.19.0 of the assembly
V1.1 of the msi package contains v1.0.21.0 of the assembly.
This assembly is sourced using a merge module.
When i execute v1.1
Hello,
Is it required that a user installing assemblies into the GAC , has to have
admin privileges?
What if an installer including VC redistributables which install assemblies
into the GAC, has to be installed by a standard user?
Kindly let me know.
Regards,
Kiran Hegde
--
View this
Hello All,I was experimenting with the Languages attribute in Wix.These are
my findings:-The Language attribute for the element determines the language
that would be displayed in the progress bar and the error messages.-The
Language attribute for the element determines the language that gets
Hello,
I am well aware of the component rules. One of the rules is that the
component guid should not be changed if the keypath does not change.
Here is my scenario:
Major upgrade scenario
-Install v1 of the product with a component a
-Install v2 of the product with the same component a but with
Any response would be very much appreciated.
Thanks,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-component-guids-change-across-major-upgrades-tp7598026p7598080.html
Sent from the wix-users mailing list archive at Nabble.com.
Thanks for the response. Much appreciated.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-component-guids-change-across-major-upgrades-tp7598026p7598134.html
Sent from the wix-users mailing list archive at Nabble.com.
Hello All,Here is my scenario:Base product has a version of 1.0-I have a
small update(QFE) which has a sequence number of 1.0.6.0The small update
contains a file named PatchCustomActions.dll with a version of 1.0.3.0Patch
code: {2BA41362-74A7-427D-A219-93CBFF4C5844}The small update also contains
Hello,
Thanks for the response.
I am not using Wix to build my patch.
I am using msimsp to build my patch.
Another follow up question:
Is a superseding hotfix meant to replace everything from supserseded
hotfixes , even if that results in downgrade of files?
Regards,
Kiran Hegde
--
View
The experience speaks for itself (tm)
-Original Message-
From: kirannhegde [mailto:
kirann.hegde@
]
Sent: December-01-14 11:42 PM
To:
wix-users@.sourceforge
Subject: Re: [WiX-users] Patch sequencing problem - Small update + a
supseding hotfix
Hello,
Thanks for the response.
I am
Does anyone has any other thoughts?
Regards,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-sequencing-problem-Small-update-a-supseding-hotfix-tp7598304p7598398.html
Sent from the wix-users mailing list archive at Nabble.com.
Environment: Windows x86 8.1 English
Driver type is file system drivers.
I am making use of the SetupAPI:InstallHInfSecton to install drivers. This
API
is used in my MSI package. When the driver package is installed, the
associated .sys file is copied to
%windows%\system32\drivers.
One of
Here is a description of the problem:
-Environment is Win 7 SP1 Enterprise x64
-We are executing a MSI package which contains numerous INF files. These
INF
files are associated with drivers. To install the drivers , we make use of
the
API: InstallHInfSection.
The exact usage of
Hello,
I declare a property in a merge module and mark it as Secure. However, when
the final MSI is built , i observe that the property is not appended to the
SecureCustomProperties in the Property table.
As per the following pages:
Hello,
Does anyone has any ideas here?
Regards,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Publisher-policy-registry-entries-not-cleaned-up-after-an-uninstall-tp7600854p7600880.html
Sent from the wix-users mailing list archive
Hello,
What happens when you apply the patches outside of Burn?
Also, how did you make sure that Patch 2 is in the view when you uninstalled
Patch 3?
Do you have a verbose windows installer log file?
Regards,
Kiran Hegde
--
View this message in context:
Hello,
*Scenario:*I have a merge module which contains certain assemblies, which
get installed into the GAC.
This merge module is consumed by a msi package.
The merge module also contains GAC publisher policy files associated with
each of the assemblies.
When the msi package is installed ,
41 matches
Mail list logo
