Both files have 5/10 as time stamps on my machine. In an earlier
release (2 weeks ago or so) I had problems with the strong names too.
After installing the latest build using the .msi (not the zip) it's
now working again.
Best regards,
Sebastian Brand
Instyler Software -
Hello,
I have the following challenge:
1. I transformed the heat-output for my purposes with xslt to a
files.wxs so that I can use it within the build-process.
2. I created a slim merge module:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=MyProgram Name=MyProgram/
/Directory
I found out
Do you also know how the ProcessorArchitecture attribute of the file
element is actually used during deployment.
_
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 17 October 2007 06:07
To: Stone, Darren (HBOS FS, IT , DDC Infrastructure)
Cc: wix-users@lists.sourceforge.net
Subject:
Thank you Peter for information...
Does anybody know any tool, which can create delta patch from two
versions of MSI? I tried MSI Patch Builder, it's not so bad, but on
any project settings it crashes too. I was able to create .EXE patch
only...
Thanks.
David.
2007/10/16, Peter Marcu [EMAIL
I did the UI-less admin install and the error still occurred so it's safe to
say it's not in my UI.
This is my wxs fileUnfortunately I don't know enough about WiX yet to
understand if there are any problems with it.
http://www.nabble.com/file/p13248873/eProject.wxs eProject.wxs
I'm
Bob Arnson-6 wrote:
Karim MacDonald wrote:
would replace the Class element, or if this particular Heat bug (think
I
saw it logged but can't find it now!) is likely to be fixed any time
soon?
So far, nobody's volunteered to maintain Heat so the bug isn't likely to
fixed soon.
I may
Karthik wrote:
The problem is that autogenerated Id is not unique. It should be simple to
write a temporary postprocessor that goes through and adds Id=[unique
value] to each RegistryValue element.
Thank you for your reply Karthik. I don't think this is the problem, as each
generated Id
Nick,
I've had good success using NSIS (http://nsis.sourceforge.net) to create
my bootstrapper. It can easily launch any application you may need. I've
also heard good things about InnoSetup
(http://www.jrsoftware.org/isinfo.php), but I have not used it myself.
Hope this helps.
Regards,
Richard
Yes and no. As a former SMS 2003 guy, I'd just use filemon to sniff out the
extracted MSI location and break it out into it's own SMS package. I rarely
used setup chainers because SMS has it's own chaining tool. You end up
consuming less space on your distribution points, pull less bits (
Can it handle silent installation stories and understand ProductCodes,
PackageCodes to do things like invoke first time install, minor upgrades and
maintenance UI stories?
[EMAIL PROTECTED] wrote:
Nick,
I've had good success using NSIS (http://nsis.sourceforge.net) to create
my
It appears that the wix.dll included in the wix3-binaries.zip is a different
from the one included in the .MSI, at least for the last couple of weekly
builds. The one within the .MSI appears to be the correct one, with the
right Public Key Token.
Just a heads up for anyone that is trying to get
Silent installations yes or at least it used to... I haven't tried
recently because any user running the bootstrapper is doing so
interactively and wants feedback on the process. Advanced users who want
a fully silent installation handle the prerequisites for themselves,
then trigger our main MSI.
I think I found what Bob recommends - Bootstrapper Manifest Generator
http://www.codeplex.com/bmg
I'll definitely check out NSIS and InnoSetup as well; thanks for all the help!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 17, 2007 07:30
Yeah, you're right. I wrote something that autogenerated Id's as a fix to
get my test build working, but my coworker, who had to use it in his
project, ended up using regasm /regfile to generate the right entries.
On 10/17/07, Karim MacDonald [EMAIL PROTECTED] wrote:
Karthik wrote:
The
Hello,
I have custom action in C++ dll that opens installed file and modifies it.
But in Windows Vista if file needs admin rights(for example if file is under
Program Files tree) opening file for writing fails.
I'm trying to use
CustomAction Id=SettingUpConfigFile BinaryKey=InstallHelper
I believe this ends up in the MsiAssemblyName table together with some
other assembly name attributes. If you get it wrong the usual symptom is
that the assembly won't be uninstalled from the GAC. Assuming this is
for the MsiAssemblyName table, IMO WiX should be getting this value for
you
Sorry if this has been covered already, but I couldn't find anything in the
archives. I was looking for a French Translation of WixUI, and found an almost
complete one at http://www.tramontana.co.hu/wix/loc/index.php. The only
problem I ran into is that anything that had an accented character
Does it fail even if you run your setup elevated? If you’re able to run your
MSI non-elevated, it’s probably using the compatibility features to write to a
mirror program files directory under the user profile, not the real one. If
you run your msi, does Windows ask if you want to elevate?
I am a newbie with WiX. I had a quick question regarding structuring my WiX
wxs file. The way I have it set up is that all the UI code is in this one
large .WXS file. I was wondering if I could break up this WXS file into
smaller files (maybe like each UI Dialog in its own file or something) so
The process to create a user, create a service, and then set the
service to run as the user is fairly straitforward. I have User and
ServiceInstall elements and I've verified that they're working fine
by themselves; both the user and the service are created upon install.
The problem comes when I
Did you ever find a solution? I am seeing the same warning. My initial guess
is that its happening because my merge modules are in Wix 1.0 and since then
they must have added more rules to the ICE validation
Thanks,
-M
David Howell-2 wrote:
Hi Again,
I am now trying to using the
The commonly accepted solution is breaking up the code into fragments. The
source code of WiX UI (wixui.wixlib) might be of your interest, as it is a
good example (I think, what I write at least stands for WiX 2.x).
In this case, for each level of UI - depending on how far it is reduced
-
You need to set the codepage attribute to the Franch codepage. Than it will
work.
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Wednesday, October 17, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject:
You can e.g. replace the license.rtf file found in the wix binaries
directory, but that would be a bit rude solution. I think otherwise the file
should be placed in the folder with the .wixobj files to be built with
light.
I hope someone corrects me if I'm wrong.
2007/10/17, Levon Levonian
Hi All,
I am using WixUI_Minimal, but I want to have my custom EULA. The
tutorial says: To specify your product's license, include a License.rtf
file in the current directory when you run light. Well, I included such
a file, but nothing happens.
Any ideas?
Thanks!
Thanks, but I tried putting it into the /obj directory, into /obj/debug, then
into the same dir as the *.wxs file, but it just doesn't include my
License.rtf.
I wonder if anybody did that successfully.
Or is there some command line switch to include the EULA?
Hi,
Is this still an issue with the version 3.0.2925.0?
I have a WiX v3 installation which uses the SqlDatabase to create a
database. This works great. However, as soon as I add a child
SqlScript and a corresponding Binary my installation just hangs until I
kill the process and never
I am able to use these elements successfully with 3.0.3328.0. This is the
first v3 build I've used so don't know if there was an intentional change
between these releases.
Amy Rosewater wrote:
Hi,
Is this still an issue with the version 3.0.2925.0?
I have a WiX v3 installation
Hi,
I have the following in UI sequence
Show Dialog=PrereqCheck After=CostFinalize![CDATA[Installed= AND
NOT RESUME]]/Show
Show Dialog=Installing After=PrereqCheck![CDATA[Installed= AND NOT
RESUME]]/Show
Now the problem is I can see the PrereqCheck dialog, but it instantly
disappears
Hi,
I tried the following, but it doesn't work
Condition Message=Not Admin \n\r don't have 2.0(NOT Priviledged) AND
MsiNetAssemblySupport lt;= 2.0.50727/Condition
How to display message in multiple lines.
Thanks,
Nitin
DISCLAIMER
==
This e-mail may contain privileged
Hi
WiX does not directly support this.
But you can create the Public Property from Custom Action (e.g.
CRLF) and this property will contain the new line sequence \r\n.
After that you can write your message in the following way:
Condition Message=Not Admin [CRLF] don’t have 2.0(NOT
Priviledged)
You are missing Impersonate=no in your CustomAction element. On Vista, the
action runs impersonating the installing user, who (with UAC turned on) does
not have write permission under Program Files, since it is the user before the
elevation prompt.
If you set Impersonate=no, then the custom
32 matches
Mail list logo
