1. Sign your bundle.
2. Submit it to Symantec's false positive web page.
-Original Message-
From: Marty Offe [mailto:marty.o...@dh.com]
Sent: Thursday, February 6, 2014 4:30 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] setup.exe (Bundle) blocked by Symantec Endpoint Protect
> Before that even, I suggest explaining what this is about.
At this moment, Is it only a technical question: can it be done such
installer with WIX?
If it is not possible technically, then the idea is finished.
If it is possible, then the next logical step is to talk with "the
cygwin community"
Before that even, I suggest explaining what this is about. Cygwin
has a working installer. You're proposing creating a new installer
for Cygwin which looks just like the current one. Why? I can imagine
possible reasons, but without knowing some good ones it sound like
a great deal of work for no ga
First of All, I would contact the maintainers of
Cygwin(http://www.redhat.com/services/custom/cygwin/) and ask how that
setup is packaged before trying to retrofit a WiX installer...
Quoting Blair Murri :
> Certainly it is possible using a custom BA from a bundle. Somewhat
> less so from an
Certainly it is possible using a custom BA from a bundle. Somewhat less so from
an MSI. One big advantage of the bundle, however, is that the entire set of
packages can be divided up between some arbitrary set of MSIs abstracted away
from the end user (in fact, the most logical would be to have
Uhh, that is a very old build of WiX v3.6. You're probably hitting some
ancient bug that we fixed in the year+ after that build was made available.
On Fri, Mar 22, 2013 at 11:24 AM, George Fleming wrote:
> Running Wix 3.6.1922, I have a Setup.exe that's a custom managed
> boostrapper applicatio
> Date: Tue, 26 Oct 2010 13:45:22 -0700
> Subject: Re: [WiX-users] Setup.exe
>
> Something along the lines of this:
> http://wix.sourceforge.net/manual-wix3/install_dotnet.htm ?
>
> Also, the Windows SDK has a tool (WiDiffDb.vbs) that does a diff between two
> MSIs. Either
Something along the lines of this:
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm ?
Also, the Windows SDK has a tool (WiDiffDb.vbs) that does a diff between two
MSIs. Either smoke.exe (from the WiX toolset) or MsiVal2 or even the Orca
tool (from the SDK) can run validations.
-Origi
A solution I have been using is AutoIt V3 scripting language. I create
self-extracting executables that are then distributed to the customer. I
would recommend downloading the SciTE editor as well - it has a lot of
additional features.
http://www.autoitscript.com/
-Original Message-
From
Hukumchand Shah wrote:
> I have my msi file created using WIX. I want to make setup.exe which does
> some tasks like copying some file and renaming it and finally launch msi
> installer.
> How can I do that setup.exe?
>
I'd suggest writing it in C++ if it's possible users won't have .NET
insta
lf Of John Daintree
Sent: Friday, June 06, 2008 2:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setup.exe UAC elevation on Vista
OK Rob, thought so. Thanks.
- Original Message -
From: "Rob Hamflett" <[EMAIL PROTECTED]>
To:
Sent: Fri
OK Rob, thought so. Thanks.
- Original Message -
From: "Rob Hamflett" <[EMAIL PROTECTED]>
To:
Sent: Friday, June 06, 2008 10:02 AM
Subject: Re: [WiX-users] Setup.exe UAC elevation on Vista
> Yes, this is expected. If the file looks like its an installer, then
>
Yes, this is expected. If the file looks like its an installer, then Vista
will elevate it unless
the manifest says otherwise. This was to try and aid migration to Vista.
Rob
John Daintree wrote:
> Hello all.
>
> I've written a standalone GUI to spawn the install of 3 separate MSIs. The
> g
Most straightforward approach at present is to diff the source!
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hall
Sent: 16 July 2007 16:45
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] setup.exe has no icon
Weekly releases of WiX are available at
http://wix.sourceforge.net/releases/.
Is there an easy way to find out what is changed from release to
release? The history.txt file looked promising, but it is not always
updated from release to release, and is just a list of changes -
Ian Stevenson wrote:
Where did you get 3.0.3106.0 from? Did you build it from source? I ask
because I notice it's not available for download yet (I just checked)
and as such it may not really be ready for release yet.
Weekly releases of WiX are available at
http://wix.sourceforge.net/releases
Lewis G. Pringle, Jr. wrote:
I realize I can make a manual copy of the setup.exe
'stub', and put an icon in myself, and then use that stub. But is
there some reason WIX doesn't provide an icon for the setup
bootstrapper? Is there some reason its not made more easy to override
the
Where did you get 3.0.3106.0 from? Did you build it from source? I ask
because I notice it's not available for download yet (I just checked)
and as such it may not really be ready for release yet. So maybe that is
why there is no icon yet, maybe you need to send something to wix-dev
instead. :?
C
18 matches
Mail list logo
