Hello, how is everything? My life is wonderful now that I lost weight.
http://bitly.com/16V6AuQ It's free to try, what do you have to lose? I love
hearing back on how well this works.
Nothing that is documented today.
On Wed, Sep 4, 2013 at 3:57 PM, wrote:
> Hi all - I've managed to upgrade some of our installs to Wix 3.7 with the
> burn bootstrapper, hooray !
>
> One thing I haven't quite anticipated is this: after our automated build
> we need to push a newly-built install
Hi all - I've managed to upgrade some of our installs to Wix 3.7 with the burn
bootstrapper, hooray !
One thing I haven't quite anticipated is this: after our automated build we
need to push a newly-built installer to a test machine for an automated
smoke/sanity test. First we need to uninstal
On 02-Sep-13 06:02, Ihor Horovetskyi wrote:
> When I try to run the .msi with log, test return value 3:
Please open a bug and include which build of WiX you're running, OS
version, and which .NET Frameworks are installed.
--
sig://boB
http://joyofsetup.com/
On 04-Sep-13 12:44, jo...@msli.com wrote:
> So does anyone know how wix differs from VS2010 setup project for the
> per-user vs. per-machine install choice?
WiX doesn't offer an equivalent because per-user products that install
to shared, per-machine locations are a bad idea. They still require
e
On 04-Sep-13 15:13, Andrew Meyer wrote:
> No matter how I define "Schedule" in the MajorUpgrade node, during a Major
> update, the installer always acts like Schedule is set to
> afterInstallExecute.
Use the Orca tool to verify whether RemoveExistingProducts is actually
scheduled.
--
sig://boB
h
My memory says SourceDir is blank until Source Resolution is executed.
On Wed, Sep 4, 2013 at 10:13 AM, Phil Wilson wrote:
> It will work only during first install, as Rob most likely knows. During
> repair, feature change, and uninstall the SourceDir location is (IIRC) the
> installer director
There are bugs open that track progress of 2013 support.
On Wed, Sep 4, 2013 at 11:16 AM, John H Bergman (XPedient) <
john.berg...@xpdnt.com> wrote:
> I noticed while looking through the history that there were checkins
> related to VS2013 Preview, including a branch merge. Does this mean that
Manual is expected to be working now so if you find dead links, please do
file bugs about them.
On Wed, Sep 4, 2013 at 11:08 AM, Phill Hogland wrote:
> Sorry for the delay in responding to the last post. I updated my user info
> using the link provided in the email, however it always failed un
Ship the patch in a Bundle.
On Wed, Sep 4, 2013 at 10:04 AM, George Fleming wrote:
> I have two applications, a MSI and a bootstrapper/UI that invokes the MSI.
> To prevent double ARP entries, we set the ARPSYSTEMCOMPONENT property in
> the bootstrapper .
>
> This works fine, except when we app
Hello,
I have an strange behaviour with my application. The
ApplicationShortcutSqliteStudio is generated inside its folder
(ProgramMenuFolder\ApplicationProgramsFolder\utils) as expected, but it is
also generated in the root of the start folder.
Why the shortcut is also put in the root of the sta
No matter how I define "Schedule" in the MajorUpgrade node, during a Major
update, the installer always acts like Schedule is set to
afterInstallExecute. The installer will:
1) Install new version first (two copies show up in Add/Remove Programs
temporarily during this process)
2) Uninstall old v
I noticed while looking through the history that there were checkins related to
VS2013 Preview, including a branch merge. Does this mean that 2013 is
supported now (at least the preview version)?
Thanks,
John
--
Learn
Sorry for the delay in responding to the last post. I updated my user info
using the link provided in the email, however it always failed until I used
exactly the same optional 'user name' provided originally. Then it liked
the new password, and I can now log into the new bug tracker. Thanks for
WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT
Installed
worked for me. I had to remove the -UIRef Id="WixUI_Minimal" ilne from it
otherwise I was getting redefined variables with the UI I had added as a
reference through the visual studio properties
--
View this message in co
Phil,
your sample code works for me as well. Off to see where mine is different...
On Mon, 2 Sep 2013 10:25:03 -0700, Phil Wilson wrote:
> My dumb search works just fine - I can't see what the issue is. This works
> for me:
>
> Sample.msi and thing.txt in the same directory.
>
>
> Id="CheckF
I have two applications, a MSI and a bootstrapper/UI that invokes the MSI. To
prevent double ARP entries, we set the ARPSYSTEMCOMPONENT property in the
bootstrapper .
This works fine, except when we apply a patch. Because the MSI is blocked, so
is its patch. We cannot see it, and therefore c
Yes. You need a custom BA.
On Wed, Sep 4, 2013 at 3:49 AM, ak m wrote:
> Dear All,
>
> Launching Bootstrapper executable should only show the internal MSI
> interface.
>
> Not to show any of the Bootstrapper UI.
>
> Is this Possible?
>
> Any one please help me on this?
>
>
> Thanks in Advance.
RemoveFolder doesn't remove the folder if it contains files. It's possible
that you need to explicitly use RemoveFile to delete the shortcut, maybe in
conjunction with RemoveFolder. Also, it wouldn't hurt to verify that the
component associated with the RemoveFolder/RemoveFile is actually being
re
I think that's 4 reasons. :)
I am trying to make an installer that replaces the VS2010 Setup Project
installer, as stated in my first post, and it allows one to set the path
and offers both the per-user/per-machine install on the same dialog.
So does anyone know how wix differs from VS2010 setup
It will work only during first install, as Rob most likely knows. During
repair, feature change, and uninstall the SourceDir location is (IIRC) the
installer directory of the cached MSI file.
It's not good design to rely on external files in the same location as the
MSI. There are too many failure
Could you please give the solution for this?
On Wed, Sep 4, 2013 at 7:01 PM, Rob Mensching wrote:
> Yes. You need a custom BA.
>
>
> On Wed, Sep 4, 2013 at 3:49 AM, ak m wrote:
>
> > Dear All,
> >
> > Launching Bootstrapper executable should only show the internal MSI
> > interface.
> >
> > No
Binging "wix custom bootstrapper application tutorial" gives this:
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
It's a lot of work just to get rid of the bootstrapper UI, but...that's how it
is, unfortunately. I decided to circumvent my problem rather than de
Hi I have this code for a shortcut. This setup is an add on for my main
product so the code adds a shortcut to the shortcuts already installed on
the target machine. On uninstall however the add on shortcut is never
removed, can anyone see what I am doing wrong?
If you follow the example on that web url it should work for you...
You can just add the:
WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and
NOT Installed
That must be within your mailto:nkshirsa...@gmail.com]
Sent: September-04-13 2:28 AM
To: wix-users@lists.sourceforge.net
S
oops http://support.microsoft.com/kb/223300
2013/9/4 Alexey Ivanov
> msiexec /i yourfile.msi /L*v c:\temp\yourinstall.log
>
> or enable in windows by default http://support.microsoft.com/kb/223300/ru
>
>
> 2013/9/4 Natalie Carr
>
>> Hi,
>>
>> Thank you, done exactly the same and it still is
Dear All,
Launching Bootstrapper executable should only show the internal MSI
interface.
Not to show any of the Bootstrapper UI.
Is this Possible?
Any one please help me on this?
Thanks in Advance.
Anil
--
Learn the
msiexec /i yourfile.msi /L*v c:\temp\yourinstall.log
or enable in windows by default http://support.microsoft.com/kb/223300/ru
2013/9/4 Natalie Carr
> Hi,
>
> Thank you, done exactly the same and it still is not deleting :(
>
> -Original Message-
> From: Alexey Ivanov [mailto:alexey.
Hi,
I'm trying to figure out how to uninstall software from another manufacturer as
part of installing our software. This is required on Windows XP because of
limitations that do not allow our two services to run at the same time. So the
idea is to present the user with an information screen de
Hi,
Thank you, done exactly the same and it still is not deleting :(
-Original Message-
From: Alexey Ivanov [mailto:alexey.iva...@gmail.com]
Sent: 04 September 2013 10:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Shortcut not being deleted
Separa
Dear All,
Launching Bootstrapper executable should only show the internal MSI
interface.
Not to show any of the Bootstrapper UI.
Is this Possible?
Any one please help me on this?
Thanks in Advance.
Anil
--
Learn the
Hi,
During patch install is there a way for msp to search and read
properties of ComPlusApplication similar to how we use RegistrySearch
element in wix?
I need to read identity and Password properties of an existing
complus application during the patch install so that I can pass
Separate shortcut from the component.
like this:
https://github.com/krab/vacuum-im-wix-installer/blob/master/Product.wxs#L20
https://github.com/krab/vacuum-im-wix-installer/blob/master/Files.wxs#L54
2013/9/4 Natalie Carr
> Hi I have this code for a shortcut. This setup is an add on for my mai
33 matches
Mail list logo
