Hi all,
I have a Take folder, which os for our developers to put the compiled
files into for me to take to put into the installer but with version
changes this directory could also change.
for instance I currently have this:
File Id=foo.bar Name=foo.bar DiskId=1 KeyPath=yes
Could somebody tell me that how I can invoke a function inside a DLL and pass
the parameters for that function through custom action. I am developing a MSI
installer using WIX3 with votive.
Regards,
Veerendra
__
Do You Yahoo!?
Tired of
boB, It does however bring up my UI when someone clicks the change button in
the ARP. My plan was to remove the Remove button so the user would be
forced to use my UI which gives them the option to either remove or repair.
So, under this situation is there any way to allow them to check the box
Hello Richard,
I am still trying to find out some information as subtle advantages of WIX
over InstallShield looking for a demo project. Do you have any other
example project which you can share with me?
Also are there any power point slides or any info available?
Thanks,
Hina
Richard-45
We use an MMC snap-in in one of our applications. I may be simplifying
this too much, but entry point to a Snap-In is the .MSC file. We deposit
the .MSC in the Deploy directory of choice and create a shortcut to the
.MSC.
Component Id=DeployMSCComp
Guid=1ED23462-B5B7-42af-B86A-BF4CB1E86BB6
hina1703 wrote:
Hello Richard,
I am still trying to find out some information as subtle advantages of WIX
over InstallShield looking for a demo project. Do you have any other
example project which you can share with me?
Also are there any power point slides or any info available?
The
In article [EMAIL PROTECTED],
hina1703 [EMAIL PROTECTED] writes:
I am still trying to find out some information as subtle advantages of WIX
over InstallShield looking for a demo project. Do you have any other
example project which you can share with me?
Also are there any power point
In article [EMAIL PROTECTED],
V K Gangwar [EMAIL PROTECTED] writes:
Could somebody tell me that how I can invoke a function inside a DLL and =
pass the parameters for that function through custom action.
Its all in the documentation for custom actions, but first you should
reconsider
Hi all,
I have a condition so the installation is aborted if .NET 1.0 is not
installed, but the .NET section of our product is only a small section.
is there a way I can set a condition so that if the .NET Framework is not
installed then only that Feature doesn't get installed, but the rest does
In article [EMAIL PROTECTED],
Jason Rivers [EMAIL PROTECTED] writes:
I have a condition so the installation is aborted if .NET 1.0 is not
installed, but the .NET section of our product is only a small section.
is there a way I can set a condition so that if the .NET Framework is not
Use a preprocessor variable.
$(var.TakeFolder) and on the commandline to candle pass -dTakeFolder=1.
Then change it to 2 when you need to change it to 2.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Rivers
Sent: Monday, October 29, 2007 4:19 AM
To:
Dear WIX users,
I have a problem when I am trying to launch an executable through a Custom
Action from an .MSM file: the WIX installation fails.
When the executable is launched from an .MSI file everything works fine. So
is launching executables through Custom Actions from .MSM files
I saw in the FAQ that it is supposed to be easier to do this, but I
couldn't find anything in the documentation about it. Is this something
that hasn't been added yet? If not, where can I find info on it? If so,
does anyone know what is necessary to accomplish this? Like what
registry entries
In WiX v2, you should be able to create patches using the PatchCreation
element. The process is documented in the chm. It will build you a PCP file
which you then can to push through a set of Windows Installer tools.
WiX v3 has made patch creation a more native part of the process and that
We currently have a product which installs, literally, thousands of
files (source and binaries) that define applications for creating
operating systems using Windows Embedded CE. The installer is defined
in WiX. But we would like to release updates to the files on a regular
basis, like what
What version of WiX are you using?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Williams
Sent: Monday, October 29, 2007 11:16 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Doing QFEs With WiX
We currently have a product which installs, literally, thousands of
I am a little behind on keeping up with the latest updates, but am
currently using WiX 2.0.3719.
Jim
From: Peter Marcu [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 11:14 AM
To: Jim Williams; WiX-users@lists.sourceforge.net
Subject: RE: Doing QFEs
Thanks for the quick response. I'll take a look at the chms in both
versions. I'll have to stick with V2 for now though, so hopefully I
will be able to do what we need using the PatchCreation element.
Jim
From: Peter Marcu [mailto:[EMAIL PROTECTED]
Sent:
Thanks Richard, I happen to have a copy of Phil Wilson's book sitting on
the desk in front of me. Since our product is new and still in a major
state of flux, doing minor upgrades or patches has been out of the
question. I've been doing major upgrades (using the upgrade table,
etc.) so far, but
Bob Arnson-6 wrote:
That's be design: Light is a smart linker, so it brings in only those
fragments that are referenced. There are a number of *Ref elements that
create such references but not a sequence reference. That's a little odd
-- usually, you'd want to include a custom action
In article [EMAIL PROTECTED],
Jim Williams [EMAIL PROTECTED] writes:
Is there some way to define a QFE-like mechanism by using WiX?
Windows Installer addresses updates as patches, minor upgrades, or
major upgrades. I recommend Phil Wilson's book The Definitive Guide
to Windows Installer
Rob Mensching-4 wrote:
Have you read the MSI SDK about major upgrades? It sounds like you're
not using the UpgradeCode to its full potential.
In what way?? I haven't read the MSI SDK docs - but I did read Phil Wilson's
Definitive Guide to Windows Installer - Chapter 6, on Upgrades.
For some reason my msi file is bringing up the maintenance mode when I
double click it.
So, now I have two questions.
1. How do I make sure that only remove is supported.
I've already set the property ARPNOMODIFY like this:
Property Id=ARPNOMODIFY Value=1 /
but I've done it in a UI block.
Try using the msi prop: CURRENTDIRECTORY
Rad Ricka wrote:
Hello,
what's the most effective way to programmatically get the path to where my
MSI is being run from?
Cheers,
R.
-
This SF.net email is sponsored
In article [EMAIL PROTECTED],
7734456 [EMAIL PROTECTED] writes:
Try using the msi prop: CURRENTDIRECTORY
Eh? The documentation doesn't list any such standard property.
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
In article [EMAIL PROTECTED],
Anthony Wieser [EMAIL PROTECTED] writes:
For some reason my msi file is bringing up the maintenance mode when I
double click it.
This means its already installed.
1. How do I make sure that only remove is supported.
I've already set the property
Hi,
How can I prevent a network installation (msiexec.exe /a XYZ.msi)? I pasted
below the WIX content. Should I add a single dialog to AdminUISequence, to
say that it is not supported, and give the option to finish? Is there a better
way?
(PS: I am not a WIX expert... Never understood why
The WixOfficeExtension exists but is undocumented at present. That in itself
would be enough to make me shy away from it. If you feel like living
dangerously, grab the sources distribution and look at
src\ext\OfficeExtension.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
I might just mention that you have to F5 Refresh Add/Remove Programs
to be sure your entry is gone or not. A/RP doesn't refresh
automatically. Of course, closing and reopening A/RP would refresh also.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
In article [EMAIL PROTECTED],
Davut Karabay [EMAIL PROTECTED] writes:
How can I prevent a network installation (msiexec.exe /a XYZ.msi)?
Why?
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
http://www.xmission.com/~legalize/book/download/index.html
That is what I finally figured out. Thanks.
-Steve
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 3:21 PM
To: Steve Wood (OCS); wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Undefined reference in Type 35 custom action
Normally you should use TARGETDIR
Normally you should use TARGETDIR as the root of your components in a merge
module. When merging, these components' Directory entries will be rewritten
to have their parent set to the Directory that you place the Merge
element in.
Any other directories you specify in your merge module are not
Hi Mike,
Thank you for the answer; but I think the property is in the same file; this
is the XML sequence which works fine in the .MSI:
CustomAction Id=CAPCInstall.Command Property=QtExecCmdLine
Value=quot;[INSTALLDIR]AppSecInc.Performance.CAInstaller.exequot;/
CustomAction Id=CAPCInstall
Deferred custom actions get their instructions on what to do from a property
named the same as the custom action itself, which in the CA code itself is
the CustomActionData property.
When you include something in a module, by default its identifier is
modularized, that is, a GUID is added
I have defined all my features with Display='expand' and
AllowAdvertise=yes with the appropriate components refs but still don't
see the features on the selectiontree. It in fact shows a 2 level tree with
no names to the features, something is definitely not right here since I
have more than 2
in c++ : MsiGetProperty(hInstall, TEXT(CURRENTDIRECTORY), szMSISrcPath,
dwBuffer);
..it's there.
Richard-45 wrote:
In article [EMAIL PROTECTED],
7734456 [EMAIL PROTECTED] writes:
Try using the msi prop: CURRENTDIRECTORY
Eh? The documentation doesn't list any such standard
It's one of those undocumented (and therefore unsupported) properties
you shouldn't be using. DATABASE is another.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of 7734456
Sent: Monday, October 29, 2007 5:32 PM
To:
Are you planning to ship patches? The reason I ask is that patch generation
uses uncompressed images, and /a is a useful way to generate them.
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay
Sent: Monday, October 29, 2007 1:24 PM
To:
Licensed Doctors in the USA
788,886 in total 17,832 emails
Coverage in many different areas of medicine such as Endocrinology, Pathology,
Urology, Neurology, Plastic Surgery, Psychiatry, Cardiology and much more
Sort by over a dozen different fields
This week's special price = $330
I have an existing service - say XYZ AdminConsole (Not part of my MSI)
I want to:
1. Restart this service after installing my MSI
2. My MSI will remove some files during uninstall and I want to:
2.1 Stop this service before removing the files and
2.2 Start it again after removing the
In article [EMAIL PROTECTED],
shapla [EMAIL PROTECTED] writes:
1. Restart this service after installing my MSI
2. My MSI will remove some files during uninstall and I want to:
2.1 Stop this service before removing the files and
2.2 Start it again after removing the files.
How
In article [EMAIL PROTECTED],
7734456 [EMAIL PROTECTED] writes:
in c++ : MsiGetProperty(hInstall, TEXT(CURRENTDIRECTORY), szMSISrcPath,
dwBuffer);
..it's there.
That's working by accident, not working by design. Use at your own peril.
--
The Direct3D Graphics Pipeline -- DirectX 9
In article [EMAIL PROTECTED],
Sajo Jacob [EMAIL PROTECTED] writes:
I have defined all my features with Display='expand' and
AllowAdvertise=yes with the appropriate components refs but still don't
see the features on the selectiontree. It in fact shows a 2 level tree with
no names to the
Dear lists,
I downloaded
ProjectAggregator2-3.0.2925.0.msihttp://downloads.sourceforge.net/wix/ProjectAggregator2-3.0.2925.0.msi?modtime=1180101856big_mirror=0
And
Wix-3.0.2925.0.msihttp://downloads.sourceforge.net/wix/Wix-3.0.2925.0.msi?modtime=1180101890big_mirror=0
From
Jason Rivers wrote:
is there a way I can set a condition so that if the .NET Framework is
not installed then only that Feature doesn't get installed, but the
rest does get installed still?
Take a look at the WiX setup in the WiX source. We do that very thing
for Votive installation when
xyavier wrote:
boB, It does however bring up my UI when someone clicks the change button in
the ARP. My plan was to remove the Remove button so the user would be
forced to use my UI which gives them the option to either remove or repair.
So, under this situation is there any way to allow them
Anwer Nehal Khan wrote:
Yes, I get default icons even after renaming them.
Please enter a bug. I'm not sure why it's not working so it'll take some
research. If you can provide a small sample, that'll help in the debugger.
--
sig://boB
http://joyofsetup.com/
How would I go about having a website created if the target machine is a
Windows Server (2000, 2003, etc) machine only, and for an XP target
machine have a virtual directory created under the Default website. I'm
looking to do this mainly because of the crippled version of IIS on XP
machines.
Hi All,
I am using Managed Custom Action as details in
http://blogs.msdn.com/josealmeida/archive/2004/11/08/253831.aspx
This approach works like a charm but I didn't quite like the idea of packaging
InstallUtilLib.dll file in MSI.
Is there a way to use the InstallUtilLib.dll present in the
From: Richard [EMAIL PROTECTED]
Sent: Monday, October 29, 2007 9:40 PM
Subject: Re: [WiX-users] Maintenance modes
In article [EMAIL PROTECTED],
Anthony Wieser [EMAIL PROTECTED] writes:
For some reason my msi file is bringing up the maintenance mode when I
double click it.
This means
Hi,
Currently I am creating Localized WiX installers based on the steps mentioned @
http://www.tramontana.co.hu/wix/lesson2.php#2.4 (WixUI Customization and
Localization Combined).
Using those steps - I am able to create one installer for specific language.
Is there a way to link the wixobj
51 matches
Mail list logo
