On Jan 24, 2008 4:21 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Peter Jaworski wrote:
> > I have tried to build some test example setup project to test GUI and
> > my CustomActionDLL. I have done something similar to wxs file
> > presented at
> > http://www.wixwiki.com/index.php?title=Simple_Cust
Thanks for responses.
I created DLL in MicroSoft Visual Studio
and the type of file is "Application Extension"
Please find uploadfile for the DLL.
http://www.nabble.com/file/p15081184/invdll.txt invdll.txt
and following is wix code
In dialog
-
1
SERVICE_
Hi all,
When a release is made is a corresponding tag made in CVS so we can
get the sources corresponding to that release? I can't seem to find
one way or the other. Currently I'm working from the date of the
corresponding wix/history.txt file.
Thanks,
Luke
--
In article <[EMAIL PROTECTED]>,
"Wilson, Phil" <[EMAIL PROTECTED]> writes:
> MsiInstallProduct *DOESN'T* return 0x80004005 for a missing MSI file. It retu
rns ERROR_FILE_NOT_FOUND (2) if the file isn't found and ERROR_PATH_NOT_FOUND (
3) if the path does not exist. This goes back to Richard'
Hello all,
The MSDN documentation on the REINSTALLMODE property states the
following for the "v" option:
Use to run from the source package and re-cache the local package. Do
not use the v reinstall option code for the first installation of an
application or feature.
Why should it not be used
Use . WiX generates ModuleInstallExecuteSequence
table entries if you're building a merge module.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare
Sent: 24 January 2008 22:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Mer
Hello,
I've got a few merge modules generated with Wix that have custom actions
included in them. I'd like to populate the ModuleInstallExecuteSequence
table to generically schedule them. Any ideas on accomplishing this? I
looked through all the children of Module element and I'm not seeing
The preprocessor code returns this error if any XmlException occurs when
loading the document after it has been preprocessed. One source of problems
as I recall is that the XML namespaces used in the include file aren't
'hoisted' into the including document. Ensure that all namespaces used in
the i
Hi, I need to detect if my minor upgrade is already installed?
The "Installed" tells me if the current product code is already installed
but what I need here is to determine the first time the upgrade is being
installed and the second time this property should tell me that the updrage
is already in
MsiInstallProduct *DOESN'T* return 0x80004005 for a missing MSI file. It
returns ERROR_FILE_NOT_FOUND (2) if the file isn't found and
ERROR_PATH_NOT_FOUND (3) if the path does not exist. This goes back to
Richard's question, which (paraphrased) is how the heck are you calling
MsiInstallProduct?
I'm getting the following error...
candle.exe : error CNDL0124 : An error has occurred that most likely indicates
that the .NET Framework 1.1 Service Pack 1 has not been installed. Please see
the following website for more information about the service pack and how to
install it: http://suppor
Hi, I'm creating an upgrade for an existent product and I need to add a few
new *optional* features that didn't exist in the original one.
I want the new features appear checked in the feature tree by default. The
only way we found to achieve this is by defining the Allow="Disallow"
attribute in th
Kevin Richardson wrote:
> It looks like the current bootstrapper calls msiexec.exe, rather than
> using the APIs. I inherited the code and it looks like it was done
> that way to make it convenient to pass command line arguments, among
> other things.
>
> If I continue to call the executable,
Chris Weiss wrote:
> Ahh - thanks!. What's the syntax for attaching a condition directly to
> a component?
>
Use a child Condition element.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email is sponsored by: Micro
Peter Jaworski wrote:
> I have tried to build some test example setup project to test GUI and
> my CustomActionDLL. I have done something similar to wxs file
> presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll.
>
> But after build I have gotten in Visual Studio 2005:
> Er
> The UI part gathers the information from the user and the target system as
> usual, then opens the MSI database of the target package, "patches" it with
> new GUIDs, starts the main installation as msiexec /I
> and silently closes itself. In such case every
> time you install your product, from
> Am using one DLL custom action.
> (..)
> There is no wrong in dll. Because it is working fine in some OS's.
Tell us something more about DLL, especially what kind of DLL is it
(MFC, COM, .net...).
How it is linked. It may need some runtimes that cause that on some
installations it works (because
>
> I'm very new to WiX and have just subscribed to this mailing list.
> Sorry, if the questions below are stupid.
>
> Due to the fact that it is recommended to use WiX v2 for production
> projects so far, I have a couple of questions:
> 1) Will the MSI produced by WiX v2 be "valid" and compatibl
That is very `interesting`, but I'd really suggest that you read this article
first:
http://msdn2.microsoft.com/en-us/library/aa369523(VS.85).aspx
http://msdn2.microsoft.com/en-us/library/aa367797(VS.85).aspx
http://msdn2.microsoft.com/en-us/library/aa369528(VS.85).aspx
http://blog.dep
Actually this is possible with multiple instance transforms if you follow a few
simple design guides. I discuss it in detail on my blog.InstallShield has
custom tables to teach the build engine to generate and embed these tables and
I've recently written some XML driven custom automation t
I suspected that. Alas, I was hoping there was some obsecure trivia that I was
missing that could mitigate the bisbehaving control.
Bob Arnson <[EMAIL PROTECTED]> wrote: Christopher Painter wrote:
> Right, I'm familiar with MenuLocal and MenuAllLocal. The problem is
> consider this feature tree
Hello,
I have tried to build some test example setup project to test GUI and
my CustomActionDLL. I have done something similar to wxs file
presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll.
But after build I have gotten in Visual Studio 2005:
Error 1 "Light.exe"
There has been a previous thread on this which I copied for your
convenience
Subject: Re: [WiX-users] Make User Run exe when the msi is run
If the issue is that your Launch Condition prevents an uninstall, then
you probably need your LaunchConditions to be
performed only on an install. In
Hi, I generated a bootstrapper using the msistuff.exe SDK tool and now we
want to force the user to launch the installler only from the bootstrapper
(not by executing the MSI).
Is there any chance to achieve this?
Thanks!
-Adrian
Maybe elaborate a little bit more on 'working fine in some OS's' (which
do work?) and what the Custom Action is trying to do?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of SaiTeja
Sent: donderdag 24 januari 2008 11:20
To: wix-users@lists.sourceforge.net
Hello,
I've resolved the issue. The problem was that when I installed another
executable I had an OpenFile common dialog from which I chose that
executable. This file dialog caused the current directory to be changed.
I then called MsiInstallProduct with a relative path which failed
because the i
I had the same problem once and here's how I solved it.
I split my installation project into 2 projects: the first one is a
so-called UI part, the second one is the main project and it actually
installs the product.
The UI part gathers the information from the user and the target system
as usual,
Hi Yan
I wonder how did you 'patch' the second package with new Guid.
Daniel
From: Yan Sklyarenko [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 10:32
To: Daniel Janz; Daniel Hatala
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix multiple i
Thanks
That is an interesting way to deal with the problem. I understand now how to
deal with the problem.
Regards
Daniel
From: Yan Sklyarenko [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 10:51
To: Daniel Hatala; [EMAIL PROTECTED]
Cc: wix-users@lists.sou
Via VBScript custom action:
' open the MSI database of external package
Set installer = CreateObject("WindowsInstaller.Installer")
path = Session.Property("SETUPEXEDIR") & "\name.msi"
Set database = installer.OpenDatabase(path, msiOpenDatabaseModeDirect)
' setting new product code
newPr
Hi,
Am using one DLL custom action.
This custom action am calling when user clicks next button in xyz.dlg
Some machines it is working fine(i.e. opened next dialog) and in some
machines immediately it is displaying Prematurely Stopped dialog and
installation fails.
There is no wrong in dll. Bec
Hello Community,
I'm very new to WiX and have just subscribed to this mailing list.
Sorry, if the questions below are stupid.
Due to the fact that it is recommended to use WiX v2 for production
projects so far, I have a couple of questions:
1) Will the MSI produced by WiX v2 be "valid" and compat
I don't think that this is possible because of the GUIDs which would
have to be different every time you install the package.
Try to build an installer which copies the same files into different
locations instead.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Hi
I am trying to create WIX install that could be installed multiple times on
one machine. To explain myself better I need to be able to install the same
application on one computer several times in different locations (there is a
good reason for this). Currently every time I install new into a
HI
I am aware of escaping square brackets and I have done it. My query looked
exactly like /redirections/redirection[\[]last()[\]] and when error was
displayed it had the proper XPATH format. I still wonder if there was some
bug in WIX not handling XPATH right.
Daniel
_
> It looks like the current bootstrapper calls msiexec.exe, rather than
> using the APIs. I inherited the code and it looks like it was done
> that way to make it convenient to pass command line arguments, among
> other things.
>
> If I continue to call the executable, I assume that I'll need to
>
36 matches
Mail list logo
