Thank you for this explanation.
To make the solution easier to find for others possibly having the same
problem, here is what to do:
HEAT.exe file my.ocx -out my.wxs
That will create a file my.wxs containing the necessary WiX commands to
register the OCX. Compile it and then link it with the
perhaps this helps: http://wix.sourceforge.net/manual-wix2/preprocessor.htm
to define $(var.myValue) simply write
?define myValue = 3?
-Original Message-
From: Bill McCormick (LIST) [mailto:wpmccorm...@ace-co.com]
Sent: Montag, 29. März 2010 19:01
To: WiX
Subject: [WiX-users] how to
Thanks Bob. It has solved the issue. Much Appreciated !!
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, March 30, 2010 5:42 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 2812 when Navigating Through Custom Dialogs
On 3/28/2010 1:40
Dear All,
One of the files which is going to be installed on the target machine can not
work if there is a space in the path, so I need to check the install path to
ensure there is no space in it.
Dose any body have a sample code to check space in the target path?
I need to show a custom
Should properly written Windows software not be able to work with a space in
a path?
I mean: installation usually occurs in 'Program Files'. This already has a
space in the path. If your software cannot handle this, maybe you should
change the software...
2010/3/30 S.P iraniangirl9...@yahoo.com
Hi,
when i install my sample product, in the middle of the installation
prompting system to restart.
i found ForceReboot. Return value 4. and because of this another two
actions like ExecuteAction. Return value 4.
INSTALL. Return value 4.in the log file found failing to execute. can any
one
You can use the operator which means TRUE if left string contains the right
string. So you
could condition your error dialog based on something like:
[PROPERTY_FOR_FOLDER]
Rob
On 30/03/2010 08:44, S.P wrote:
Dear All,
One of the files which is going to be installed on the target
On Tue, 30 Mar 2010 08:21:05 +0200, Markus Karg wrote:
Markus,
I wonder why this simple instruction is not found in the manual or tutorial.
;-)
http://www.tramontana.co.hu/wix/lesson6.php#6.1 ;-)
Bye,
Gábor
---
Gábor DEÁK
Hi guys,
I really don't want to be pushy but I need to find a solution for this:
besides my application I also install a service that is babysitting my
application, eg: restarts it when it crashes or whatever. When the
product is uninstalled I get the message: The setup must update files
or
Hi
I need to show up a dialog box from from my c# custom Action.
I browsed through the forum got many threads related to MsiMessageBox and
MsiProcessMessage.
But all were in C++.:-(
Can anybody share a dummy code in C# to pop up a message box through my
customAction code.
Thanks in advance
Hi John
Thanks for the suggestion. That was the one I was looking for. I'll
see if I can make my project work now :)
Regards
Patrick
On Tue, Mar 30, 2010 at 07:42, John L Krupka john.kru...@nmwco.com wrote:
You add the wxs in to the call to candle which compiles the wixobj file.
Then
Hi all,
I would like to schedule the RemoveExistingProducts after
InstallInitialize in my installer:
[code]
RemoveExistingProducts After=InstallInitialize/
[/code]
in order to have first a full uninstall and then an install as my
product it's really small so it's no efficiency issue.
But I
Hi all,
I would like my application to be upgraded if a newer version is run. So
the behaviour should be: if the user tries to install the already
installed version (meaning current version) or an older version, the
installer should bail out with the message current or newer installed.
The
You only need to put that code into your newer releases which will be
doing the upgrading e.g. v1.0.0.1
Your v1.0.0.0 has nothing to upgrade so the code isn't needed. I'd
suggest commenting it out for your first release so you can add it back
for subsequent releases.
You may find that code doesn't
Great! Thanks a lot! :-)
-Original Message-
From: DEÁK JAHN, Gábor [mailto:d...@tramontana.co.hu]
Sent: Dienstag, 30. März 2010 11:27
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Beginner's Question: Registering OCX
On Tue, 30 Mar 2010 08:21:05
OK. when I reread your post, it made me think that maybe the wxs file in
question is not known until build time. If that is not the case, then what
I told you should work fine. Otherwise, I would generate the candle and
light commands at build time adding the needing wxs file. But that is not
When, during the uninstall process, are you getting the error? Is it
happening during the RemoveFiles action? If so, you might try adding the
Wait=yes attribute to your ServiceControl so that it waits for it to stop
the service before moving on to remove files. It may be that the SCM is
taking
Hello Sagar
Publishing the value for PROCEED or WARNING in DLG1 will help little in
navigation. Instead in the main dialog tree (not in dlg1) you need to
check this property on the Dlg1 Next button's new dialog event.
You will have something like:
Publish Dialog=Dlg1 Control=Next
Bear in mind everyone who replies to queries on this list is doing it
*voluntarily*. None of us get paid [...]
Yes, I know that and that's why I very much appreciate any help I'm getting.
Viv
On 3/30/2010 1:37 PM, Pally Sandher wrote:
Be as pushy as you like. Bear in mind everyone who
I have a WiX project which uses the WixUI_InstallDir to let the user
pick the directory to install the application. In my setup I don't
hard code any reference to the Program Files directory. I've used the
following setup in my main wxs file:
Directory Id=ProgramFilesFolder
Directory
Add ..
using System.Windows.Forms; in declarations and then where you want to
show the message box, use:
MessageBox.Show();
Doesn't that work?
Rohit
-Original Message-
From: Sagar [mailto:sagarkavitak...@gmail.com]
Sent: Tuesday, March 30, 2010 3:49 PM
To:
Using System.Windows.Forms can be done but then your custom action won't be
following the UILevel specified by the install session. You could tell that
MSI to run silently and your custom action will still be popping up message
boxes which is not good.
Using MsiProcessMessage is the proper way
Which language code are you using in your Product Element?
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
Cool! I tried using heat with the suggestions you made:
heat file MyDLL.dll -template:fragment -suid -gg -out fragment.wxs
Then placed what was generated, originally within:
Fragment
DirectoryRef
Component
File
...into my existing:
Product
Hi all,
This is potentially a silly question but I haven't found a clear answer on the
web yet.
Our installer consists of:
1) WiX source files (WXS) - defined in the WiX project file
2) Additional files used in the MSI package e.g. banner images - defined
in the WiX project file
Hi little.forrest,
I can't answer your question (what does repair do) directly, but here's
how I'd find out. The first step is to turn on logging for windows
installer. You can either do this when you run the MSI (assuming you're
directly running the MSI file, not using control panel) or use
In Visual Studio, you can set a Build Order for your projects (assuming that
they're all in the same solution). That way, your custom actions will be
built before your WiX files, assuring you that they're always up to date.
You can't, as far as I know, directly reference a custom action project
My application keeps various files in the common app data directory
(C:\ProgramData\MyApp\ on Vista), and the users local and roaming application
directories. These are created by the application it's self if they don't exist
(Where applicable files are also created from defaults in the main
And the classic problem that people get when they don't use MsiProcessMessage
is that the message pops up behind the install window. Then they ask how they
can force it to be on top, etc etc.
Phil Wilson
-Original Message-
From: MikeR [mailto:michael.ru...@gmail.com]
Sent: Tuesday,
It goes through each component and checks that its KeyPath is present and
correct. In your case, I suspect that some custom action is running, maybe some
code that re-installs the add-in or tries to shut down Outlook.
Phil Wilson
-Original Message-
From: little.forest
The way we have it set up is we have the Custom Action project as well as the
Wix project in the same solution. The build order is set so that the Custom
Action project builds BEFORE the WiX project. We then reference the built
CA.dll using relative path to the Custom Action folder. Works
Actually, you can reference other projects directly from your WiX project.
If you add your custom action project(s) to the same solution as the WiX
projects, you can just add a project reference to any WiX projects that use
the custom action DLL. When you change something in the custom action
Here's the scenario: A limited user called Fred installs the product. It
requires admin privilege to install, so an elevation dialog pops up and an
administrator enters his credentials so that the install can proceed.
Later on in a custom action you ask for the current user's credentials.
Hi,
How Do I create a pool 32 bit?
Or how Do I change a pool 64 bit for 32 bit?
Thanks,
Carolina Zuqueto Amaral
carolina.ama...@conv.com.brmailto:carolina.ama...@conv.com.br
tel +55 21 2494-5476
cel +55 21 9524-7186
Confidencialidade: A informa??o contida
Good Afternoon!
How to create a Patch?
I need to updates the database, to remove and to insert programs, to insert
services in the IIS and others.
Grateful,
Carolina Zuqueto Amaral
carolina.ama...@conv.com.brmailto:carolina.ama...@conv.com.br
tel +55 21 2494-5476
cel +55 21 9524-7186
I explained that there was difference between Vista and previous OS versions in
ServiceControl behavior, and also that there may be a bug in Vista and later
when you have more than one ServiceControl action. However you didn't say what
OS you're actually using, or whether you have more than one
Thanks Don!
Those are some great info.
From: Don Pratt don.pr...@cox.net
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Tue, March 30, 2010 8:55:19 AM
Subject: Re: [WiX-users] What does Repair do?
Hi
Wilbert - When it's a recompilation for Windows of Unix software, spaces
can be a problem...
S.P. - I have the same problem (I compile a distribution of Perl for
Microsoft Windows and create its installer using WiX.)
For how to connect it in to an WixUI_InstallDir UI, look at lines
152-230 of
On Tue, 30 Mar 2010 13:12 +0200, Viv Coco vcotirl...@hotmail.com
wrote:
Hi all,
I would like my application to be upgraded if a newer version is run. So
the behaviour should be: if the user tries to install the already
installed version (meaning current version) or an older version, the
Thanks Phil.
Yes, it seems a custom action unregistered a dll during Repair.
From: Wilson, Phil phil.wil...@invensys.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Tue, March 30, 2010 11:54:04 AM
Subject:
Hi All,
Allow me to recap this issue please.
Basically, we have an old product(uses Wix 2.0) that is an Outlook plugin
application. We use a COM component adxloader.dll from Add-in
Express(http://www.add-in-express.com/) in the product. What we need to do is
to install the adxloader.dll and
The reason behind calling web-service from msi is that i need to install a
file on the webserver rather than just calling copying it on target machine.
And the webserver exposes a web-service to do this.
Sagar
--
View this message in context:
On Wed, Mar 31, 2010 at 1:39 AM, little.forest little.for...@ymail.comwrote:
Hi All,
I totally understand 'using regsvr32 in Wix' is not recommended. But in
this adxloader.dll case, we can't use tallow or heat to generate fragments
from the dll. This is not the problem of tallow or heat,
43 matches
Mail list logo
