Hi
I am trying to achieve this UI in my installer page:
(*) Choice1
[ ] Check1
[ ] Check2
( ) Choice2
[ ] Check3
[ ] Check4
Here's my code:
While it looks OK, I am unable to click on Check1 or Check2 becaus
Hi
I have a digital certificate and I signed my MSI with it. When I view the
properties of the file in Explorer it shows the certificate correctly. So
far so good.
Then I modified the MSI file in a binary editor (changed one byte). Now when
I run the signtool I get an error that the verific
ust embedded somehow into the file and
does not encrypt or compress of the contents.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, June 24, 2013 8:51 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Multi-platform installer with WiX
On
[mailto:b...@joyofsetup.com]
Sent: Monday, June 24, 2013 8:25 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Multi-platform installer with WiX
On 24-Jun-13 14:44, Ivo Beltchev wrote:
> When the installer runs it extracts one of the MSIs and the shared
> cab. Then wit
No, my bootstrapper is an EXE, not MSI. If you call it directly it will
create the correct MSI and then launch it. You can also call it with
"extract32" or "extract64", which will just extract the correct MSI and you
can do whatever you want with it.
The EXE does other things as well, like calculat
23, 2013 7:59 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Multi-platform installer with WiX
On 23-Jun-13 15:13, Ivo Beltchev wrote:
> I need an installer that can work for both 32-bit and 64-bit OS.
> Currently I build 2 separate MSIs and bundle them togethe
It is a shell extension. I need to register both 32-bit and 64-bit DLLs when
I install on 64-bit OS. Also I would prefer on 64-bit systems to install in
the main Program Files, where all self-respected applications supporting 64
bits should go.
-Original Message-
From: Nick Ramirez [mailto
since MSTs can't contain
resources, I have to put all my files into the main MSI. This gives me
warnings that I have files with the same target name. It is fine though,
because I have mutually-exclusive conditions for each of the components."
I am not sure about the cabs...
Steve
-----Origi
Hi.
I need an installer that can work for both 32-bit and 64-bit OS. Currently I
build 2 separate MSIs and bundle them together in a bootstrapper EXE. The
problem is that 90% of the files are common between the two platforms and my
installer is almost double of what it can be.
One solution
I think you can edit the registry (via custom action or another way) to
set WindowsInstaller to 0, and change UninstallString to "MsiExec.exe /x
{blah} /l*v C:\q.txt".
I don't know what is the best way to achieve this, or if there won't be
any ill effects.
Castro, Edwin G. (Hillsboro) wrote:
>
emoved if it (and all of its subkeys) are discovered to be empty
> during uninstall.
>
> -Original Message-
> From: Ivo Beltchev [mailto:i...@roadrunner.com]
> Sent: Monday, July 26, 2010 9:46 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-u
Please help, guys.
I screwed up badly and need to fix this before the problem gets worse.
My current idea is to run a custom action before upgrade that stores the
registry key in a file and then another action after the uninstall to restore
the key. I have implemented the custom actions, but I'
application?
>
> -----Original Message-
> From: Ivo Beltchev [mailto:i...@roadrunner.com]
> Sent: Wednesday, July 14, 2010 9:04 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Restart Manager (reboot after uninstall)
>
>
isn't activated during logoff or logon, so
> the marked files are never actually removed until an actual reboot.
>
> -Original Message-
> From: Ivo Beltchev [mailto:i...@roadrunner.com]
> Sent: Tuesday, July 13, 2010 8:55 PM
> To: General discussion for Wind
Hi
I have an uninstaller that uses the Restart Manager. When it detects
that files are in use it shows one of two messages:
1) When uninstalling in quiet mode, there is a popup saying ".. a
reboot will be required to complete the setup"
2) When uninstalling in UI mode, there is a list of p
The action may run in some cases
when it shouldn't, but no harm done since the helper tool will not find
the EXE and quit silently.
The solution works, but it's a bit hacky. This makes me think there must
be a better way. Any ideas? I doubt I'm the first person to hit this
pro
N -1 No action to be taken on the feature or component.
>
> -Original Message-
> From: Ivo Beltchev [mailto:i...@roadrunner.com]
> Sent: Saturday, June 26, 2010 2:23 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Problem with "Clos
ent). If your code
> differs materially from my example, you will need to understand what your
> code is doing and what effects it will have under different
> situations/platforms/etc. You should also always prevent things you
> explicitly don't support (such as attempted per-user
hope it makes it through.
Thanks
Ivo
Rob Mensching wrote:
> The Upgrade table needs to be authored correctly as well. What does the
> verbose log file say?
>
> On Thu, Jul 1, 2010 at 11:28 PM, Ivo Beltchev wrote:
>
>
>> Hi
>>
>> I am upgrading my produc
Hi
I have an installer with 2 features. Each feature has an EXE. I only
allow per-machine installation, and not per-user.
I want to create a folder in All Users\Start Menu\Programs, which
contains shortcuts to both EXEs. I also want to make that folder
optional, with a property controlled by a
Hi
I am upgrading my product from a Visual Studio setup project (version
1.9.8) to WiX (version 2.7.5). I want the new WiX version to be able to
upgrade the old one. I also have 2 builds - 32 and 64 bits.
For 32 bits there are no problems. I install version 1.9.8 first, then
upgrade to 2.7.5 a
on be true.
>
> -Original Message-
> From: Ivo Beltchev [mailto:i...@roadrunner.com]
> Sent: Saturday, June 26, 2010 8:11 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Problem with "Close App" condition
>
> Hi
Hi
I have a custom action that closes my app when its feature is being
uninstalled. Here's my code:
For some reason the action gets triggered during "Repair" and also when
ANOTHER feature is being uninstalled. Why is this happening? Doesn't my
condition mean "if MyAppFeature is installed, an
Pally Sandher wrote:
> If it's a readme why not use the "Launch an Application after install"
> functionality described at
> http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm to
> simply ShellExecute the RTF? That way you can give the user the option
> to see your RTF using the
Pally Sandher wrote:
> Answer to problem 1: I already posted a link to yesterday on this very
> thread (in fact I can see it on my screen as I type this further down
> the thread). Between Neil S's blog & the WiX UI pages in the WiX manual
> you should have all you need to make the changes requir
Hi,
WixUI_FeatureTree is almost exactly what I need. I just want to change 2
things:
1) Add a Readme.rtf file at the end of the install. This can either be
in a dialog similar to EULA (that's what Visual Studio setup projects
do), or a checkbox to execute the RTF when the installer closes. Give
Hi
My name is Ivo Beltchev. I am working on the open source project Classic
Shell: http://classicshell.sourceforge.net/
Currently I use a Visual Studio setup project to create my installer,
but I'm hitting some of its limitations and I'm looking for a better
solution.
Here
27 matches
Mail list logo
