Hello,
First of all, I am new to WIX so be gentle :-) Testing WIX to see if we can use
it in a project. Using Wix 3.7 on Windows 7 at the moment.
The script below generate a working msi file but I am not fully sure how it
works and if it is a sensible setup.
It appears
Why not put D2.dll in it's own Component?
On Sun, Aug 11, 2013 at 10:37 PM, Michael Partridge
michael.partri...@petrosys.com.au wrote:
Hi All,
I was wondering if the state of play has changed at all since
http://stackoverflow.com/questions/703359/wix-add-new-file-to-shared-componentwas
Yes, the Component Directory attribute is a reference to the Directory with
matching Id. This pattern is used heavily in the WiX toolset. The Directory
attribute isn't required when the Component element is nested under a
Directory. The doc could be updated to note that a Component's Directory
I have an installer of an application that needs to be installed over any
existing version, regardless of version number. Can this be done using Wix
3.7v?. If yes can I know how to do this ?
--
View this message in context:
Dear All,
I want to create an installer which will install the Printer driver using
INI file.
My problem is explained
Input
--
Printer driver set
Output:
---
Option 1: MSI file
Option 2: EXE file
Option 3: Installer + Printer driver set + INI file
Option 1,2 created
Hello,
Our installed app crashes after 'Launch' click with windows dialog that
saying: Looking for solutions. Windows 7
I found this message in Event logs:
Faulting application name: #.exe, version: 2.0.0.0, time stamp:
0x5208c428
Faulting module name: KERNELBASE.dll, version:
If over any existing version means that the old product will be removed
and replaced by the new one, a major upgrade with RemoveExistingProducts
early (e.g. just after InstallInitialize) will do that. You'll need to set
the major upgrade to detect and replace any installed version, even products
Phill/Alnoor
I had to make a few more adjustments to my code to match what you have, but
it will still only launch in English when running on a French OS. If I use
the command line option -lang 1036 then the Burn wrapper will correctly show
UI and License in French.
So how do I get it to show
According to the log file
[2013-08-12T17:22:27]i360: Creating a system restore point.
[2013-08-12T17:22:27]i362: System restore disabled, system restore point not
created.
the bootstrapper is already trying to create a system restore point. Does it
fail only because of some system settings, or
I am trying to solve that same issue, so I do not have a solution yet. I was
in the process of importing the 'extended bootstrapper' and writing a
BAFunction.dll to try and get the language of the UI to be the same as the
OS UserLanguageID and also address an issue where I need to restrict which
The former (controlled by system settings). For example, it's common to have
VM's configured with restore points disabled.
--
John Merryweather Cooper
Build Install Engineer -- ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
Okay thanks, If 3.8 does correctly detect OS language and launch Burn wrapper
in detected language then that should solve part of that issue.
As for your 2nd issue, are you talking about conditioning your MsiPackage so
that it will only use your supportted language .mst's that you need to pass
to
Yes, we support seven languages. If I pass UserLanguageID or
SystemLanguageID in my var LCID and then pass it as a property to the MSI
package in the form of TRANSFORMS=LCID.mst all is well for the supported
languages, however an unsupported language results in an error because the
transform does
Hello,
My name is Marlos and I'm working with WiX for the last 6 months. I'm
migrating a system from InstallShield to WiX and I'm excited with the
toolset. I'll be glad to contribute to the list.
But I'm having the following problem with Burn:
I created a bootstrapper to installed two msi
Burn will automatically detect if MSIs are installed. No need to do
anything. Additional help probably requires more detail about what exactly
the searches and conditions were.
On Mon, Aug 12, 2013 at 12:36 PM, Marlos Gottschild
marlos.gottsch...@gmail.com wrote:
Hello,
My name is Marlos
Thanks, Rob,
Here is the code:
util:RegistrySearch Root=HKLM
Key=SOFTWARE\Classes\Installer\Products\PACKED_GUID Value=Version
Variable=PkgA_Installed Result=exists /
Chain MsiPackage Id=PkgA SourceFile=PkgA.msi
DisplayInternalUI=yes Visible=yes
InstallCondition=PkgA_Installed /
Then my
The way the language detection works in WiX is to search for a language
matching the full language ID and if that isn't present it searches the primary
language and then defaults to US English - so if you support Spanish but not
Mexican then Spanish is selected. I am wondering if you could set
Thanks for the idea. I will try that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587954.html
Sent from the wix-users mailing list archive at Nabble.com.
I assume that your (Neil's) description of the WiX language detection
behavior applies to 3.8, because I have not observed that behavior with WiX
3.7. For me with 3.7 I always have to use -lang LCID to see any of my
supported bundle translated strings. So far I have only tested using
Windows 8
No this also applies to 3.7 but there is a bug that means it detects the system
language not the user language which probably explains what you are seeing. If
you make the system language match the user selected language it works as I
described.
-Original Message-
From: Phill Hogland
Can anyone point me to a reference that recommends a best practices project
structure for WIX - using boot strapper?
I have two projects - one for Setup and one for BootStrapper. I have 2
dependencies - .net framework 4 and iis express. I was going to create a
Dependencies folder for those; a
When I started with WiX I downloaded the WiX source code and used the
src\Setup tree of files as an example. I found CommonLib and CoreMsi to be
helpful in building my MSI. I used Bundle as a model and initially got a
MBA similar to WixBA working. The web download stuff is not operational
yet.
If I put D2.dll in its own component, then, assuming Product1 and Product2
installed, when Product2 is uninstalled, D2.dll will be removed. However, A.dll
will still be at version 1.1.0, so will have lost its dependency and thusly
won't run.
NB: I can't change Product1 - it's already in the
Anyone have any ideas please?
On Sat, Aug 10, 2013 at 12:40 AM, Jeff Nevins j...@jeffnevins.com wrote:
I can't seem to get wix cabinet caching to work.
I have
PropertyGroup
CabinetCreationThreadCount3/CabinetCreationThreadCount
CabinetCachePathcabs/CabinetCachePath
24 matches
Mail list logo
