2013/6/1 Rob Mensching
> More specifically, you cannot use RemotePayload element and
> Compressed='yes' on the ExePackage element together. That doesn't make
> sense and the bug here is that the compiler didn't give you an error
> message here saying that.
>
Exaclty, you have understood !
Is it possible the directory has been marked for deletion? That is another
way to get access denied (something else, or something earlier in your MSI)
caused the directory to be deleted but some process has a handle locking
the directory so it isn't gone yet... but the operating system won't let
yo
More specifically, you cannot use RemotePayload element and
Compressed='yes' on the ExePackage element together. That doesn't make
sense and the bug here is that the compiler didn't give you an error
message here saying that.
On Fri, May 31, 2013 at 5:37 AM, Markus Wehrle wrote:
> Ok, I see.
>
1. I searched the WiX.chm for "restore point" and got one hit on the Chain
element which has an attribute named "DisableSystemRestore". I think
that'll do what you want.
2. Bundles are not Products. Completely different engines and we're trying
to learn from the mistakes of the engines before us.
I think by "link" John means using a link in Visual Studio to add the file
to multiple projects. Personally, I would use a Library .wixproj to build
reusable chunks which is John's second suggestion.
On Fri, May 31, 2013 at 3:02 PM, Wheeler, Blaine (DSHS/DCS) <
bwhee...@dshs.wa.gov> wrote:
> By
I downloaded the wix38.exe which uses the latest WiX toolset to build and
it seems to set both of the version numbers correctly. Not sure why you'd
see different behavior. Maybe a bug in an old version of WiX toolset
(assuming your using an older version).
On Fri, May 31, 2013 at 3:26 PM, Alain F
When setting my Bundle's version to X.Y.Z (using the Version attribute), the
resulting .exe's Product Version is correctly X.Y.Z, but looking at the .exe's
Properties' Details tab (or even hovering over the icon or filename), the File
Version always seems to display 1.0.0.0 . To my knowledge, we
By link you mean specify the .wxs files on the candle command line?
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, May 31, 2013 2:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn and Wixlibs
Links or wixlibs
Links or wixlibs.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.go
We have about 20 fragments with MSIPackages or EXEPackages in them. I need to
build several Bundles that have some of these Fragments in common. How can I
refer to them without actually having to add the wxs fragments to each Bundle
project. It would be handy to have 1 solution, with all of th
Correct. I should be more precise. A bundle contains burn engine and packages.
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: May-31-13 4:51 PM
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Cc: Wesley Manning
Subject: Re: [WiX-users] *Package Permanent attribute
Yeah, I'm new to burn (and WiX in general), so I'm still getting the lingo
down. Thanks!
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: May 31, 2013 15:51
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Cc: Wesley Manning
Subject: Re: [W
My understanding is that a Bundle is processed by the "burn" engine.
ARP == Add/Remove Programs
On Fri, May 31, 2013 at 12:44 PM, Alain Forget wrote:
> By "burn", you mean what I'm referring to as the Bundle?
>
> And by ARP, you mean "Add/Remove Programs"?
>
> Just making sure I understand. :-
By "burn", you mean what I'm referring to as the Bundle?
And by ARP, you mean "Add/Remove Programs"?
Just making sure I understand. :-)
Alain
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: May 31, 2013 15:41
To: afor...@cmu.edu; General discussion for Window
+1
The chasm between getting things working in a development environment and
getting them working seamlessly in the deployment environment (by end users) is
a lot wider than some may be willing to admit.
Alain
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent:
Just means burn will not try to uninstall it. The package will also appear in
ARP.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: May-31-13 4:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] *Package Permanent attribute
Can someone please clarify the
If it doesn't get built, it won't get tested. Period.
Dev's have a tendency to consider installer building a waste of time (they
always think they can do it better with a 3rd-party zip lib and some sort of
XML config document) until it's one week before beta and suddenly you need to
shake the
Can someone please clarify the effect of the Permanent attribute for a package
(e.g. MsiPackage, ExePackage)?
The documentation
(http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm) says,
"Specifies whether the package can be uninstalled. The default is 'no'."
Making a package imposs
I know that in a will skip
the restore point, but how can this also be done in a ?
In general, how do I set properties like that in a bootstrapper?
lso, why can't elements like and be used in a
bootstrapper's the same way they are for a in a single MSI?
Alain
**
Albert,
Do you require your regular code writing devs to install Wix on their boxes so
they don't get errors opening the wixproj files in the main solution, or do you
keep the .wixproj files off in their own little solution so the devs don't
notice? Also, do your devs handle the installers, or
Bingo. I had no idea I could pass the path to a DLL as an extension to candle &
light, like this:
candle.exe -ext ./lib/WixBalExtensionExt.dll -ext WixUIExtension -ext
WixUtilExtension MyBundle.wxs
Somehow, I had thought only pre-packaged extensions could be referenced with
-ext...although typ
If you are doing this via the command line, I assume it's light complaining
about the extension. You need to use -ext WixBalExtension (subst whatever
Neil's is here , probably need a full path)
Also, in your wxs you want to include references to any custom extensions (Ex:
xmlns:util="http://sc
My bootstrapper UI has some weird artifacts I want to fix, and Neil
Sleightholm's WiX Extended Bootstrapper Application (ExtBA,
http://wixextba.codeplex.com/) seems to provide a more easily customisable UI
than the native WiX bootstrapper application UI (from what I can gather...if
there is doc
I'd recommend starting with a verbose log file to see what is different on
Win8.
On Fri, May 31, 2013 at 7:45 AM, Martin Johnson wrote:
> The following code snippet works on all OS with the exception of WIndows
> 8. e.g. on Windows 7 ExcelHelpPath32 has a correctly formatted path to the
> help
If the name doesn't match the Payload name, the file will not be cleaned
out of the package cache correctly. I suppose you could mark the ExePackage
as Cache='no' but then you'll want to avoid repairing and uninstalling it
because you'd end up with a prompt for source during uninstall.
All of this
Is the payload file extracted in the same folder as the stub.exe from the
ExePackage ?
2013/5/31 Hoover, Jacob
> Sounds like you need to talk to the person who thought of this "great" way
> of passing a parameter to their installer
>
> That being said, you could create a stub exe, which tak
Sounds like you need to talk to the person who thought of this "great" way of
passing a parameter to their installer
That being said, you could create a stub exe, which takes the params and does
this dance for you. I'd suggest making a copy in the temp folder for the
install, and leaving wh
The following code snippet works on all OS with the exception of WIndows 8.
e.g. on Windows 7 ExcelHelpPath32 has a correctly formatted path to the help
file and TSDataDirectory has a correctly formatted path to the data Directory,
On Windows 8 ExcelHelpPath32 is again correctly formatted whils
I need this feature because i'm launching an external installer (.exe) and
i need to give it a serial number (user dependent, asked in the
bootstrapper UI) as parameter, and the only way to give it this parameter
is by renaming this exe file from INSTALLER.EXE to INSTALLER_SERIAL.exe
Yes i know thi
No, and that won't work will with the way that Burn caches packages and
such. This scenario isn't supported today. Why do you need to do such a
thing?
On Fri, May 31, 2013 at 5:08 AM, Benjamin Mayrargue wrote:
> Hi all again,
> i have a strange requirement.
>
> I need to rename the EXE file (set
Oh wow, I can't believe it's not butter working!
Yeah, as you've said, apparently one doesn't use burn.exe to use Burn...go
figure. :-P In any case, I've got it working. For anyone who stumbles upon this
thread with similar confusion, here's the process I use now to bundle the JRE
with my MSI (
Hi,
Can any one help me finding out where I am doing something wrong in creating
Site in IIS. CoreWebsServicesV3 is getting created twice and each one
pointing out to two different App pools. one pointing to default app-pool
and another pointing to app-pool "CWSWebAppPool" which I have created.
Ok, I see.
If you want to have the ExePackage compressed into your bootstrapper.exe
(compressed="yes") you need to specify it using "Source" attribute. Cause it
will be compressed into your boostrapper during compile time, you must not
declare a DownloadUrl.
If you specifiy compressed="no" your Exe
Hi all again,
i have a strange requirement.
I need to rename the EXE file (set in ExePackage) before running it.
The renaming involves a variable set and known only at runtime.
Is this possible out of the box ?
thks,
B.
-
Sorry, this fails:
Compressed="yes"
DownloadUrl="$(var.UrlSauvegarde)"
But this works perfectly:
Compressed="no"
DownloadUrl="$(var.UrlSauvegarde)"
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
xmlns:bal="htt
Hi Benjamin,
we do not have this issue and can successul download exe package in out burn
configuration.
Can you provide more details, e.g. the complete ExePackage definition and the
content of $(var.UrlSauvegarde)?
> Benjamin Mayrargue hat am 31. Mai 2013 um 10:33
> geschrieben:
>
>
> Hi all,
Good afternoon,
This is driving me crazy. I can on my Windows 7 run this installation I've
created and the custom action successfully writes a database backup-file (a
.bak-file that it has as an embedded resource in its assembly) to the
Temp-directory provided by Path.GetTempPath(). On my comp
Hi all,
how are you today ?
It's raining hard here in Paris.
I have found a "bug" in 3.7 :)
If an ExePackage has a DownloadUrl and Compressed is set to yes, light
failed with error LGHT0103: The system cannot find the file '' with type ''.
Compressed="no"
DownloadUrl="$(var.UrlSa
We use a lot of (VS) Project Property Sheets. For WiX we have defined several
property sheets for this. Our solution gives us the possibility to change the
location where WixTools are etc. This way we can easily switch between WiX
versions as well (assuming the schema, on what we use, hasn't bee
39 matches
Mail list logo
