I have not been following this thread, but is it not possible to use the Visual
Studio Remote Debugging facilities so that you only have to install a bare
minimum on the test machine rather than the full VS suite? (see
http://msdn.microsoft.com/en-us/library/y7f5zaaa.aspx)
Daniel Madill
2014 7:29 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn custom bootstrapper and ARPINSTALLLOCATION?
On 28-Jan-14 10:52, Daniel Madill wrote:
> However, in my original MSI I set the ARPINSTALLLOCATION property so that the
> install location shows up in ARP. I would lik
entry for the
bootstrapper. How do I set the ARPINSTALLLOCATION for the burn bootstrapper
bundle? I'm passing the same InstallFolder to each MSI in the chain, so the
concept of an "install location" does make sense for my bootstrapper.
t be happening with normal
install/uninstall. Anyway, the bundle log file should show why a package is not
being uninstalled.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: Monday, January 6, 2014 1:27 PM
To: General discussion about the WiX toolset
be the packages are being reference counted by another bundle
still on the machine.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: Monday, January 6, 2014 12:24 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Burn not uninstalling MSI downloaded fr
or 64-bit version of Windows.
It all seemed to work beautifully and seamlessly until I tried to uninstall the
bundle after installing from the web.
Sincerely,
Daniel Madill
--
Rapidly troubleshoot problems before they
assagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx.
Sincerely,
Daniel Madill
-Original Message-
From: Gerry Reno [mailto:gr...@verizon.net]
Sent: December-19-13 8:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ExeCommand will not accept any
ut if burn should run as a 32-bit application, where am I going wrong
here?
A link to a no-burn bootstrapper tutorial would be appreciated :)
José Marques
On Thu, Jul 18, 2013 at 3:21 PM, Daniel Madill wrote:
> Hi Jose,
>
> I have not used burn because I have my own bootstrapper for now, b
Hi Jose,
I have not used burn because I have my own bootstrapper for now, but I believe
burn runs as a 32-bit application even on 64-bit Windows. You can still chain
64-bit MSIs though, as far as I know.
Daniel Madill
www.quanser.com
-Original Message-
From: José Marques
because it hasn't been necessary. At some point we
will likely investigate using burn.
Daniel Madill
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: June-18-13 3:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-user
I use a WiX preprocessor variable for the Win64 attribute value so I can set it
in one spot when using the same source for generating a 32-bit and a 64-bit
MSI. That makes it easy e.g. Win64=$(var.Win64).
Daniel Madill
-Original Message-
From: Tim Hawes [mailto:haw...@anx.com]
Sent
Jacob Hoover is not correct as far as I can tell. I install to both the 32-bit
and 64-bit Program Files folder from a 64-bit MSI. I also pass the ICE
validation tests when building the MSI. I don't believe anything is off-limits
to a 64-bit installer.
Daniel Madill
-Original Me
a
mixed 64-bit MSI for 64-bit platforms from the same WiX source.
Daniel Madill
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: June-18-13 2:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Java Program Installer
AFAIK
I think he wants the component Ids to be such that if the component Ids are
sorted alphabetically then they end up in the same order as the files
themselves when the files are sorted alphabetically.
Dan
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: May-15-
It's not just .NET. Many functions in the Win32 API have the same limitation
unless you use UNC path names (in which case the limit is 32767 characters).
Daniel Madill
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent: May-03-13 2:10 PM
To: General discussio
), and then the data is not removed
until after the service uninstalled.
Daniel Madill
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: May-02-13 11:12 AM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject
ally acceptable, does
not have an advantage over the other?
Just curious,
Marc
-Original Message-----
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: March-28-2013 12:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS Building using Different p
above if statement.
Hope this helps.
Daniel Madill
www.quanser.com
-Original Message-
From: Marc Beaudry [mailto:mbeau...@matrox.com]
Sent: March-28-13 11:55 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] VS Building using Different platforms
Hello
I searched and can&#
pgrade
element has options for displaying messages if the user tries to upgrade or
downgrade and should not be allowed, etc. if that's what you need. If you want
something more complicated on upgrade then you will have to do a little more
work.
Daniel Madill
www.quanser.com
-Origin
*) instead of the default Text documents (*.txt).
If you really want to change the permissions so that it can be edited by the
user without elevated privileges, use the Permission child element (or
PermissionEx). Alternatively, install to a user-editable location.
Daniel Madill
-Origin
file by reference instead of copying it to the project
folder.
Daniel Madill
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: February-26-13 5:33 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Referencing fragment .wxs files from an environment
vari
u can refer to the product
version as $(var.ProductVersion).
Daniel Madill
www.quanser.com
-Original Message-
From: Don Reba [mailto:don_r...@inbox.ru]
Sent: February-10-13 2:05 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] VS - version number from file
If I run Candle fro
Hi Raphael,
I've used mt.exe in the Windows SDK to update the manifest embedded in an
application before. While I've never tried it with a BA generated by burn could
you not use it, or a similar tool, to patch the manifest of the BA *after* it
is built by Wix?
Daniel Madill
---
I found that accessing the timestamp servers was more reliable when using the
actual IP address for the timestamp server (i.e. a.b.c.d notation) rather than
the hostname. Doing so eliminates DNS failures and resulted in far fewer build
failures in my case (I sign a lot of components, not just th
It is possible to improve screen reader support by supporting Microsoft UI
Automation or Microsoft Active Accessibility (MSAA). Older screen readers
supported MSAA. Modern screen readers should support Microsoft UI Automation.
WPF has support for UI Automation but not MSAA.
Daniel Madill
Chief
control is activated."
That suggests to me that higher Ordering numbers get higher priority. I haven't
required this attribute myself however.
Daniel Madill
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: October-03-12 9:53 AM
To: 'Gene
Hi Gareth,
I don't currently use the DuplicateFile table because my 32-bit components and
64-bit components are distinct - mainly because we provide 32-bit support for
our APIs but the full product is native 64-bit on a 64-bit O/S i.e. the user
runs the 64-bit product, but can access 32-bit API
-bit
applications that use our product on a 64-bit O/S. That way I do not have to
worry about compatibility between the 32-bit installer and 64-bit installer - I
can deal with 32/64-bit compatibilities in the 64-bit installer alone.
Daniel Madill
-Original Message-
From: Peter
t includes both 32-bit and 64-bit
components for a 64-bit O/S from the same source files by using the WiX
preprocessor facilities.
Sincerely,
Daniel Madill
-Original Message-
From: Gareth [mailto:gmor...@serif.com]
Sent: June-12-12 6:40 AM
To: wix-users@lists.sourceforge.net
Subject:
Hi Gareth,
I install 32-bit applications in a 64-bit installer all the time. I use the
Win64="no" attribute on the 32-bit registry entries to ensure they go in the
32-bit hive on the 64-bit platform.
Sincerely,
Daniel Madill
-Original Message-
From: Gareth [mailto:gmor...
ly find the WiX errors (or ICE errors) give me enough
information to figure out what's going on. If you give more details, such as
the actual build output and excerpts from your product.wxs then I suspect you
will get more help. This group is quite active.
Sincerely,
Daniel Madill
-
What is the garbage text? My suspicion is that you may have inadvertently saved
the batch file as a Unicode file and that there is a Unicode byte-order mark
(BOM) at the beginning of the batch file. If so, then open the batch file is
Notepad and then choose Save As and explicitly specify the enc
staller use to determine where files go in
Maintenance mode? Could I have some left-over registry entries from prior
install attempts that need to be cleaned up? If so, where do I find them (I've
searched for component GUIDs in the registry and not found the
this in a repeatable fashion so that the generated
fragment is always valid?
Cheers,
James
-Original Message-----
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: 16 January 2012 16:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File
Cheers,
James
-----Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent: 16 January 2012 16:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File
Hi James,
I haven't used heat for quite a while, but I think you can use the
Hi James,
I have an idea how you were feeling about adding 2000+ files because I had a
similar situation with over 12000 files and more than 1000 folders. Glad to
hear you got it working! :-)
Dan
-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: January-16
Yeah, I'm just getting my batch command setup for this. It's building OK as a
fragment but I'm can't work out how to incorporate it into the features so that
it will actually execute during the install process.
James.
-Original Message-
From: Daniel Madill [mail
Hi James,
You can use the "heat" harvesting tool that comes with WiX to generate an
initial WxS installer file for your 2000 files and 650+ directories and then
add that WxS file to your installer.
Dan
-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: Janu
LPWSTR is already a wchar_t *, so LPWSTR is a wchar_t **. Hence it is
complaining that it cannot convert a wchar_t ** to a wchar_t *, which makes
sense. It seems to me that you need to change your "LPWSTR *" type to just
"const LPWSTR", or do you not have control over that data type?
Dan
-
Blair,
I didn't narrow it down exactly because it would have taken a while. The merge
module WiX project that was giving me trouble currently references the project
outputs of 415 projects, so I probably had several hundred WxS files at the
time VS2010/MSBuild was croaking and I moved away from
d croak while building the
> solution. It appeared to be a bug in VS2010 rather than WiX, but, anyways, I
> tend to use WiX include files that I then include in a single WxS file to get
> around the problems with VS2010 (within a single project, but I have multiple
> merge module pr
X include files that I then include in a single WxS file to get
around the problems with VS2010 (within a single project, but I have multiple
merge module projects for sharing installer components with third parties).
Daniel Madill
-Original Message-
From: rhf417 [mailto:rhf...@hotmail.
I hadn't noticed the "VS2008" when I posted last. References to C++ projects
work fine for me in VS2010 with WiX 3.5. I haven't tried VS2008. My mistake.
Sorry about that.
Daniel Madill
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas.
I reference C/C++ projects all the time from WiX 3.5 with no problems at all.
You didn't actually name your project "myC++Project" (i.e. with '+' signs in
the name) did you?
Daniel Madill
-Original Message-
From: RaoHuiFei [mailto:rhf...@hotmail.com]
Sent:
The link worked fine for me.
-Original Message-
From: john.burak [mailto:john.bu...@telvent.com]
Sent: Friday, September 02, 2011 12:49 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Broken link to Mondo documentation page?
Is anyone else getting a server error in the follow
Hello Mr. Gombrelli,
Here is code taken from a *working* wixproj project file in WiX 3.5. MSSDK_DIR
is an environment variable set to the absolute path to the Windows SDK. It
installs the .NET Framework 4.0 client profile. For the full version use
Include=".NETFramework,Version=v4.0". I don't s
To all concerned,
Would you and Peter Stein (and anyone else involved) be so kind as to move this
particular discussion to private emails or another forum if it is to continue?
It would be very much appreciated.
Graciously (I hope),
Daniel Madill
-Original Message-
From: Castro
Sorry, this is a repost because the formatting came out strangely on the last
email.
For a few more details:
- Multi-part CABs can get the total size of a set of files past 2GB, possibly
to 64K * 2GB, but no one file can exceed 2GB.
- Maximum size of all files in one folder (uncompressed) = 2GB
For a few more details:
Multi-part CABs can get the total size of a set of files past 2GB, possibly to
64K * 2GB, but no one file can exceed 2GB.
Maximum size of all files in one folder (uncompressed) 2GB
Maximum size of all files in one folder (compressed) 2GB
Maximum size of a CAB file (comp
I find the Action attribute values confusing as well. It didn't help that all
the examples I looked at used "createAndRemoveOnUninstall" even though that
generally isn't necessary. I would actually have found it much clearer to use
"createAndRemoveOnUninstall" and "createAndRemoveAllOnUninstall"
generic way to trigger off the merged installation?
Or does that depend on each merge module? I'd like to trigger off this
licencing stuff at the end of the rest of the install.
Thanks again,
Dominique.
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com]
Sent
Use a Merge element in your Directory tree, such as:
Note that you can use environment variables in the path with a syntax such as
$(env.MyEnvVar). I use the $(env.CommonProgramFiles) syntax to access standard
merge modules under $(env.CommonProgramFiles)\Merge Modules.
Also add a MergeRe
I would assume you just need to add a CreateFolder element to ensure the
destination directory is created. For example:
Dan
-Original Message-
From: Dave Combs [mailto:dave.co...@kaazing.com]
Sent: Monday, June 13, 2011 1:10 PM
To: General discussion for Windows Installer XML
/wix-tricks-and-tips
Daniel Madill
Quanser Inc.
http://www.quanser.com
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Friday, May 13, 2011 5:45 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] single msi for 32-bit and 64-bit ??
To whom it may concern,
In VS2010, I turned on the Harvest option for a Reference in a Wix merge module
project with the Project Output Groups set to Content in order to produce a
list of the 100s if not 1000s of Content Files I have in the referenced VS2010
project. However, heat.exe fails wit
55 matches
Mail list logo
