I have seen many posts about the following error message:
The Localization Identifier 'SomeIdentifier' has been duplicated in multiple
locations...
I have seen many guesses as to why.
However, I have not seen very much in the way of real answers as to why this is
occurring.
Could one of the Burn
My apologies for the multiple posts, but I've found some more information that
might tell some of you something, even if I don't know what it implies.
One thing I might not have previously mentioned is that the restart request
does NOT appear if I wait for a few minutes after install before tryi
Is the extension that you have used first including WixNetFxExtension.dllIf you
download the source code, you can find the code in
"wix37-sources\src\ext\NetFxExtension\wixlib" the wix project called
NetFxExtension contains all the code used to provide the extensions for the
versions of NetFX.
Hello,
Sorry for the delay.
Finally, after all your coments, I redesigned the application:
/home is pointed to $USERPROFILE
/OUT is pointed to $TEMP
/EXPORT is pointed to $USERPROFILE/BGINFO4X/REPORT
/BASE/CONF/OUT is pointed to $USERPROFILE/BGINFO4X/BASE/CONF/OUT
Now, there is no necessary to
I've had to deal with this in the past. DIFX just unloads the driver from the
device. DIF_REMOVE is only called when removing the entire device as happens in
device manager when using the Remove option. I got around this with a CA that
sent the DIF_REMOVE directly to the device class using the
I've found a number of Restart Manager posts similar to this:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-and-the-Restart-Manager-td3162984.html
Since our services' JSL exes basically use Java, maybe it's Java that's locking
our files, and the uninstaller doesn't/can'
64-bit Windows Vista and beyond places 32-bit programs into Program Files
(x86), and 64-bit programs into Program Files. It's just the convention they've
adopted going forward with 64-bit operating systems.
I do think I've seen 32-bit programs sneak themselves into Program Files on a
64-bit OS,
Blair (and anyone else interested),
You were bang on about both manually trying to launch the service to test it
and using " around the formatted string. Sometimes when I've been working
at something for too long, I don't think of things like that and can't see the
forest for the trees. :-s
Un
To get *version* comparisons the quotes from around the version numbers
(that makes them strings) and put a "v" in front. So the following should
evaluate to true: "v4.0.0.0 < v14.0.0.0"
On Fri, Jun 21, 2013 at 12:21 AM, Michael Stoll wrote:
> Here're the SQL CE 3.5 and 4.0 packages.
>
> Th
Hi, I am able to create MSI file for our product using wix installer.
When I install this product on client PC(windows xp), it kept all the files
C:\Program Files\Safety (the target directory & it's hot coded in code)..which
is OK.
But when I install this product on client PC(windows 7), it ke
Unsubscribe, then:
https://lists.sourceforge.net/lists/listinfo/wix-users
On 21 June 2013 15:38, Wesley Wells wrote:
> Stop sending me this useless stuff!!!
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Friday, June 21, 2013 9:30 AM
> To: General
I would recommend you unsubscribe yourself from said "useless stuff":
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Wesley Wells [mailto:wwe...@midsouthmetalsupply.com]
Sent: June 21, 2013 10:39
To: 'General discussion for Windows Installer XML toolset.'
Stop sending me this useless stuff!!!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, June 21, 2013 9:30 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Give NetFx40Redist a local download path?
PS: The "redist" fo
PS: The "redist" folder is what's authored in the extension (you can see it
in src\ext\NetfxExtension\wixlib). It could have been anything. Looking for
a file locally before looking for a file remotely is standard Burn engine
behavior.
On Fri, Jun 21, 2013 at 2:14 AM, Pally Sandher wrote:
> WiX
Yes. If the Property is defined hidden and compiled into the Merge Module
and the CustomAction is set to HideTarget and compiled in the Merge Module
then the toolset should take care of modularizing things for you.
On Fri, Jun 21, 2013 at 5:31 AM, Steven Ogilvie wrote:
> Classification: Public
>
Classification: Public
Can you explain what you mean by that please?
If I am using Hidden/HIdeTarget regardless in a Merge Module or the parent
project it should work, right?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: June-21-13 2:50 AM
To: General discus
@Blair: I did download WixContrib and the WiX code (which is why I know
about the existence of tables.xml). To be honest, I feel like trying to
reverse engineer the WixContrib code is a bit futile. In order to
understand it, you need to understand certain things about WiX extensions
so you know why
Hi at the moment I have my windows installer version at 4.5. I need to cover
v3.0, is it just a case to lower the version or what implications would this
have?
Thanks
Natalie
--
This SF.net email is sponsored by Wind
The light task is called once for each CultureGroup item. You will probably
need to do the same in your post-build target(s).
Each CultureGroup has an OutputFolder metadata you can use to locate that
culture's MSI/WixPdb to pass to torch.
> Date: Wed, 12 Jun 2013 12:31:34 -0700
> From: phogl.
Did you consider the book "WiX 3.6: A Developer's Guide to Windows
Installer XML" (ebook + kindle edition + hardcopy available) from Nick
Ramirez. There
Chapter 14: Extending WiX + Building a custom WiX extension
- Setting the stage
- Extending the CompilerExtension class
- Adding an XML schema
-
Depends on the version of the Windows Installer engine on the machine you apply
the patch with. If you set your minimum MSI version to 200 you don't need to
worry about SequenceStart.
See this blog for an explanation:
http://blogs.msdn.com/b/heaths/archive/2006/05/19/602133.aspx
> From: jaco
To quote RobMen on stackoverflow: "You might take a look at the extensions in
the WiX contrib (http://wixcontrib.codeplex.com/) project. Since they aren't
part of the WiX toolset they have the extra steps needed to build the
extension."
The WixExtension is required in most wix extensions and s
WiXNetFxExtension will check a sub-directory called "redist" where your bundle
is for the package then download it if it doesn't exist at that path e.g.
"redist\dotNetFx40_Client_setup.exe".
This is standard Burn behaviour.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F
in the sources: src\ext\NetFxExtension\wixlib will have wxs files you can
examine (that are supplied to your projects whenever the WixNetFxExtension is
referenced in a build).
> From: y...@slb.com
> To: wix-users@lists.sourceforge.net; mark...@live.it
> Date: Fri, 21 Jun 2013 00:01:37 +
> S
Alain,
Temporarily remove the ServiceControl\@Start and install. Then use the service
control manager and start. See what errors are reported, diagnose, and tweak
the installation. Once your service starts when installed, replace the @Start
attribute.
I didn't see anything special done when j
I would recommend updating the conditions to
64-bit:
32-bit:
This is clearer and separates out the maintenance part of the condition from
the precondition part.
> From: haw...@anx.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 19 Jun 2013 10:03:12 -0400
> Subject: Re: [WiX-users] Ja
From: http://wix.sourceforge.net/manual-wix3/light.htm use -sval if you use the
commandline
From: http://wix.sourceforge.net/manual-wix3/msbuild_task_reference_light.htm
set SuppressValidation if you use the Light task from MSBuild
From: http://wix.sourceforge.net/manual-wix3/votive_property_page
Here're the SQL CE 3.5 and 4.0 packages.
There's a significiant difference in the behavior of those two!
The SQL CE 4.0 packages detect SQL CE 4.0 of ANY language. While 3.5
detects only a specific language.
The SQL CE 4.0 package could be altered to look for a specific language,
but I like the
28 matches
Mail list logo
