Hi,
I want to provide the TARGETDIR value from command prompt while running the
MSI, Please suggest me how the value can be provided, the WIX XML is
http://schemas.microsoft.com/wix/2006/wi";>
I have found the same and just haven't had time to document the
problems. There are loads of files missing from the source download, I
found the best thing to do was to get the CVS source as well and copy
the required files from there and also search for files on your local
system until it builds.
Let me rephrase. How do I specify preprocessor variables when I build
from command line with MSBuild?
msbuild myinstall.wixproj /p:???
-Original Message-
From: Alex Ivanoff
Sent: Tuesday, October 14, 2008 15:47
To: 'General discussion for Windows Installer XML toolset.'
Subject:
How would you do that? Cmd.exe doesn't mask characters.
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 17:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to masked Password
I've found that MSXML is not terribly friendly with whitespace. XmlFile and
XmlConfig, of course, both use MSXML. If you find a way to get MSXML to behave
better, that'd be cool
-Original Message-
From: Pierson Lee (PIE) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 14:18
T
Thanks for your answer. After including this, Passwords are saving in masked
form in log file. But I want to pass this password from command line
Msiexec /I installer.msi /qn PASSWORD=test123
In above command, I want password in masked form.
Regards
Sandeep
-Original Message-
From: Rob
Property/@Hidden="yes"?
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 16:45
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to masked Password Value
Hi,
While doing silent instal
Hi,
While doing silent installation, I want to pass user id and password id for
services.
How can I give password in masked form from command line.
Regards
Sandeep
-
This SF.Net email is sponsored by the Moblin Your Move D
Thanks Ian. I've noticed that and glad that you find my blog useful. I'll try
to come up with the post regarding fragments vs includes if I will have time
for that.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008
The Windows Installer does not support installing an MSI inside an MSI. That's
called "nested installations". You need to "chain installs" instead...
unfortunately, that requires an external program.
-Original Message-
From: David Bartmess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, Octob
No. Components installed in different directories is handled by the Windows
Installer. As long as the Components have the same Resources the reference
counting is correct.
-Original Message-
From: Ben Greenberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 15:55
To: General
Is that possible with the Windows Installer? I'm not sure I've heard of a
feature like that.
-Original Message-
From: Michael Lin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 16:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to provide warnings when overwrit
Hi,
I want to create a setup msi such that it will give warnings to the user if the
file being copied is not newer than the existing one on the directory.
Can this be done in Wix?
Thanks,
Michael
-
This SF
Hi Jason,
I was building from within VS 2008, the CA project threw the build error. I
then looked at the csproj file that the Votive C# CA Template created, and
in the "AfterBuild" target, it has an which has absolute paths to the
WiX SDK. Eg. "C:\Program Files\Windows Installer XML v3\SDK\Ma
Alex,
Thanks very much. That is very helpful. That might be worth adding to your very
useful blog. I refer to it almost daily!
Ian
-Original Message-
From: Alexander Shevchuk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 3:39 PM
To: General discussion for Windows Installer X
A shared component defined in a merge module is included in two
different packages, but the two packages install the same component into
different directories. So there are two copies of the same component
out the system, and two entries in the DB (according to msiinv).
Not directly a WiX ques
One more thing. Make sure that original installation does not have
ARPSYSTEMCOMPONENT set.
-Original Message-
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 3:28 PM
To: Alexander Shevchuk
Cc: General discussion for Windows Installer XML toolset.
Subject:
Hi Ian,
In simplest terms: everything from will end up in your msi
database. Only fragments which are referenced from the main code will be
included in resulting msi database. For example:
File1.wxs:
File2.wxs:
Main.wxs:
In addition, you can compile file with fragment i
It looks like a simple Registry tag does the trick of removing it:
I had to drop RemoveRegistryValues into the InstallExecuteSequence as well.
Alexander Shevchuk wrote:
> Normally, that registry key holds a ProductName property:
>
> HKLM\SOFTW
Normally, that registry key holds a ProductName property:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductName]
So, your choices are either change your ProductName to match original from
InstallShield or keep your current ProductName and remove that InstallShield
registry key.
Vista x64 is my primary development environment for DTF and WiX, and that works
for me.
Are you building from a 64bit command-prompt / 64bit MSBuild? If so, make sure
you have installed the 64bit WiX MSI. (Also, that configuration is not very
well-tested, so it's possible there are issues.)
--
Just to give you a better idea:
Is what I'm attempting
-Original Message-
From: Pierson Lee (PIE) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 2:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems with XmlConfig
Oops, forgot the actual CustomAction, sorry...
-Original Message-
From: David Bartmess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 3:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Custom actions failing
I'm trying to w
Hi,
I have a custom action project that was created using the C# Custom Action
Template in VS2008. This was building fine under XP 32 bit, but I am now
trying to build on Vista 64 bit, which is causing a couple of issues:
- The hard coded reference to the WiX V3 SDK is incorrectly "C:\Program
I'm trying to wrap my head around the custom actions, and how to code
them. I've got the following in my fragment, and although it builds
fine, I always get an error about "a program required could not be run".
Any suggestions would be helpful and appreciated!
Thanks!
(OFFICEVERSION =
Hmm.. Its really strange. Even when I don't edit that config tag, it still
strips the hex values I put in. Am I to assume that there isn't a way around it
then? :)
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 1:41 PM
To: General discuss
But msxml can be told to preserve whitespace when parsing... In all likelihood
Wix isn't doing that, but it is conceivably possible...
Mark
-Original Message-
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 4:41 PM
To: General discussion for Windows Insta
That's good to know, actually. I'm doing some xml file manipulation in
one of my installers (via custom actions and mxml in my own dll) and
preserving any formatting in the xml file in question would probably be
a polite thing to do.
Mark Modrall wrote:
> But msxml can be told to preserve white
What version of the WiX toolset are you using? Where did you download it from?"
-Original Message-
From: aretha samuel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 12:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] System.TypeLoadExceptio
1. Probably some part of InstallShield wrote that which is not in the
installer. Maybe a bootstrapper?
2. You should be able to use the RegistryKey element to nuke the key.
-Original Message-
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 13:11
To: Gene
How do I pass preprocessor variables to WiX using MSBuild task? I tried
this
But it did not work. Any ideas?
On Tue, Oct 14, 2008 at 12:41 AM, Alex Ivanoff
<[EMAIL PROTECTED]>wrote:
> I wander if anyone can share their experience with building WiX
projects
> with Team Build. What targets to
If you're trying to format the xml itself, you may be out of luck --
msxml (which I believe wix is using) will do the formatting however it
feels like doing it. This is true of most programmatic xml access.
If the text in question is in a CDATA section, however, I'd think that
should work, assu
I think you're fighting MSXML here.
-Original Message-
From: Pierson Lee (PIE) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 13:27
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Problems with XmlConfig
I was attempting to insert #xA; into my web
All of the code I included is defined in the merge module. Thus, any
modularization should occur across all 3 items (custom action definition,
custom action scheudling in InstallExecuteSequence, and binary definition).
Looking through Orca at the main install, it seems to be hooked up
correctly.
I was attempting to insert #xA; into my web configs to specify a carriage
return for some lines of text I'm adding into the config, but it seems like
during the process, those characters are getting stripped. Anyone have any idea
how to do this? Thanks :)
---
When you build a merge module, all IDs get modularized (a GUID is appended) to
avoid naming clashes. So if you have the Binary element defined in one module
but reference it from another, the modularization won't be consistent. If you
really want to do that, you'll have to manually append the GU
I am in the processing of moving from IS12 to Wix for a number of our
products. So far, things are going fairly well.
There is one issue, however. The install we have out in the field is
version 4.0.17. I have done a Wix installer that does a major upgrade to
4.0.20. Everything works fine -- th
According to The Source
(http://msdn.microsoft.com/en-us/library/aa368072(VS.85).aspx):
"Note that custom actions that are executable files must return a value of 0
for success. The installer interprets any other return value as failure."
Are you absolutely, positively sure that your custom act
Thank Jas!
Regards
Simon Powell
-Original Message-
From: Jason Ginchereau [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 15:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Transform Creation
Database sourceDb = new Database("source.msi"); Databas
No i am not running this from a network share, only from a local machine.
Do i need to have the .NET framework 1.1 service pack 1 installed on my
computer for the wix tools to work? Can someone tell me what version of the
.NET framework works with what version of the wix tools?
thanks
aretha
I've been unable to resolve a problem I'm seeing trying to
build recent WIX sources. All documentation says to 'simply run make.bat,' but
I'm not seeing this succeed.I'm actually hit two problems -
1)
C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common
Take a look at the existing extensions in WiX v2. There were huge changes from
WiX v2 -> WiX v3 on the extension story.
-Original Message-
From: Mukesh Agrawal [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 11:16
To: General discussion for Windows Installer XML toolset.
Subjec
That's the impression I get from the documentation as well. Looks like
I'll have to have a closer look at that method. I'll let you guys know
if I find anything-it seems to be a tricky bug to reproduce. Somehow
you have to get the same cert in the store twice.
-Original Message-
From:
Hi All,
I was able to use 'foreach' in wix v3.
But, when I tried using it with v2 I got the following error:
The variable named 'LCID' is not allowed in foreach expression.
In the documentation, I read that only LCID is allowed for v2. Even that does
not se
Hi All,
I followed the same steps as were there in Peter Marcu's blog for writing wix
extensions. I was thrilled to see it working.
I used wix v3.
But, WixExtension class was nowhere to be found in wixv2. Is there any pointer
on how can I achieve the same thing in wix v2.
Thanks
Mukesh
Microsof
So, this only is a problem for custom actions defined and scheduled by my
merge module. I have the same custom action assembly with helper assembly
that is referenced directly by the main install for several custom actions,
and all of those actions work fine.
My merge module has the custom action
Hi,
I haven't yet used Wix fragments but have used a couple of include commands.
I've been trying to research what the difference is between using fragments vs
including code via type tags but am not finding anything.
Can anyone offer a basic explanation on how the two differ?
Thanks,
Ian
--
I'll check that out too, I just get confused with the setting of properties
and when I can query them, but the link Rob sent seems to have solved it.
Thanks
Ryan
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 18:33
To: Gene
Oops. Sorry about that.
-Original Message-
From: Jim Williams [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem with RegistrySearch
It looks to me like those properties begin with t
It looks to me like those properties begin with the letter O... but it
is tough to see with that font, but there is a slight difference (the
letter O is more round and the number 0 is more oval).
Jim Williams
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL P
There is good info on major upgrades here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
There is a section called "How upgrade works" that should help you out.
If I understand you correctly when you install the upgrade, the original
product is be
The first character of each of those is an "O" (oh), not a zero. I
already ran into that..
It looks like it's fixed with taking the trailing slashes off the Keys.
Cut n paste error strikes again!
Thanks!
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL PROTE
Also, I believe properties cannot begin with numbers so the following
properties are illegal:
O2003PIAINSTALLED
O2007PIAINSTALLED
-Original Message-
From: David Bartmess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 8:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-us
Thanks Rob, those docs helped a little.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 14 October 2008 16:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems Executing a Custom Action on uninstall for
a major upgrade.
Tak
Could it be the trailing backslashes?
-Original Message-
From: David Bartmess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 08:29
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Problem with RegistrySearch
I'm having a problem with RegistrySearch and hoping someone ca
Yes, already fixed it.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 10:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Services are not removed on uninstall
ServiceControl?
-Original Message---
I thought you were referencing to MsiSetProperty API.
Thanks.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 10:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Set property conditionally
In the WiX.c
Take a look at the MSI SDK about Major Upgrades. There are a few different
ways to schedule Major Upgrades and there are Properties set based on your
Upgrade element.
-Original Message-
From: Ryan O'Neill [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 06:43
To: 'General discu
I'm having a problem with RegistrySearch and hoping someone can help me.
In the code below, the first RegistrySearch is fine, while the following
two are causing the errors seen below the code.
I don't see any difference in the three, as far as syntax goes.
Any ideas what the problem may be?
T
That's the Merge Module design yes. Work around... don't use Merge Modules
maybe?
-Original Message-
From: Ben Greenberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 07:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Set the InstallExecu
ServiceControl?
-Original Message-
From: Alex Ivanoff [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2008 21:05
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Services are not removed on uninstall
I know I am missing something obvious, but I cannot get
In the WiX.chm?
-Original Message-
From: Alex Ivanoff [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2008 17:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Set property conditionally
In the WiX script?
-Original Message-
From: Rob Mens
Hi,
We have a number of large solutions which I am creating the installer for.
There will only be a single final "installer" (i.e. msi), but there will be
a few features within that.
I am not sure of the best way to structure the wix library projects. I am
opting away from merge modules as it
Make sure you are inserting the correct DLL into the Binary table. That DLL
should be the output of MakeSfxCA, which is the native SfxCA.dll stub with
managed assemblies appended as a cab. Verify it has the expected entrypoint
that MSI is looking for by running "dumpbin.exe /exports YourCA.dll".
Database sourceDb = new Database("source.msi");
Database targetDb = new Database("target.msi");
string transformFile = "transform.mst";
// Create a new transform from source to target.
targetDb.CreateTransform(sourceDb, trasnformFile);
// If the transform is to be applied during an installation,
An embedded UI handler cannot call custom actions directly. The Session object
you get in the IEmbeddedUI.Initialize() handler is only a limited session which
lets you get/set properties and not much else (there's no database either). The
limitations are imposed by MSI's embedded UI design, not
I am packaging the helper assembly with the custom action by passing it as
the last parameter to MakeSfxCA.
The verbose log has the following around the error message.
MSI (s) (EC:14) [08:38:00:565]: Doing action:
InitInstallDIR.FE2FB413_1E39_4B13_AC8B_A3F8022742C4
Action 8:38:00: InitInstallDIR.F
If you look at the verbose log you can see what custom action it is trying to
run just before that error. And are there any other error messages nearby in
the log?
Is the helper assembly getting packaged with the custom action by MakeSfxCA? It
should be automatically if there is an assembly ref
Condition the custom actions based on a property within the merge module,
defaulting the property value such that the custom actions run by
default. Then the user can pass a different value on the command line for
that property so that the condition will no longer be true and the custom
actions wo
OK, so i've made some head way. I now have 2 custom action assemblies with
12 and 13 custom actions respectively, and a third "helper" assembly with
common code needed for both sets of custom actions. Once I got everything
compiling and rebuilt, I ran my install and got the following errror:
Er
Is this by design?
Any suggestions for a reasonable work around?
Thanks,
Ben
Bob Arnson wrote:
> Ben Greenberg wrote:
>
>> I am including a Merge Module in my MSI that includes a few CAs. I want
>> to allow the user to pass a command line property to skip these CAs.
>>
>> I can edit the Con
Hi all,
I know this has been asked numerous time and I just saw another variant of
it, but I'm scratching my head here.
Can someone explain the steps for a major upgrade? Is it a complete
uninstall and reinstall (as I suspect). Does this mean I can't really detect
when I am being properly u
Yes, that would probably be a good idea since I get this question every now and
then.
-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2008 8:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DTF: InstallerExc
Hi
My custom actions are working with conditions for install and uninstall
appropriately, but though I give the execution type as immediate, custom action
is not responding for exit code(The exit code returned is 1)
REMOVE
REMOVE
NOT Installed
AND NO
Thanks a lot peter, custom actions are working now.
-Original Message-
From: Peter Vestergaard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 6:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How can I run a custom action only on uninstal
Not for the whole process, at least as far as I know. Windows Installer is
very deliberately split
into 2 parts - interacting with the user and working stuff out, and actual
system changes. Only the
latter part runs elevated.
Rob
Nimisha Saboo wrote:
> Thanks again Rob!
>
> Is there no way
Thanks again Rob!
Is there no way, my msi can prompt the user to give permissions to it to run
as admin?
What I am looking for is: double clicking my msi shows the UAC prompt, and
if the user decides to continue as an admin, then only my msi runs.
Regards,
Nimisha
On Tue, Oct 14, 2008 at 5:27
Hi,
change Execute="deferred" to Execute="immediate".
Kind regards,
Hans
>
> Hi,
>
> I have written a customaction running an exe which is written in .Net. The
> exe is returning the exitcode as 0, but if there is any error the exitcode
> is returned as 1, but the custom action is not stopping
Hi,
you must set the appropriate conditions:
Installed
NOT
Installed
The custom action will fire if the condition is evaluated to true.
Kind regards,
Hans
>
> Hi,
>
> I have two custom actions one should run on install, one should run on
> uninstall, but
You'd have to run the whole installation elevated, either from an elevated
command line or using
some kind of bootstrapper which runs elevated.
Rob
Nimisha Saboo wrote:
> Hi Rob,
>
> Thanks for the reply. Actually, I just went into details of deferred
> actions, and I realised that I don't wan
Hi,
I'm trying the Embedded UI and I get an
Microsoft.Deployment.WindowsInstaller.InvalidHandleException.
I added a dll in the Binary table and tried to read it in the class
that implements IEmbeddedUI :
object result = session.Database.ExecuteScalar("select Data from
Binary where Name = '{0}
The custom element should have a condition. This is done by adding a text
element. Your InstallExecuteSequence should look like this:
REMOVE
REMOVE
NOT
Installed AND NOT PATCH
NOT Installed
AND NOT PATCH
the custom element containing REMOVE will run on uninstall and
Hi,
I have written a customaction running an exe which is written in .Net. The
exe is returning the exitcode as 0, but if there is any error the exitcode
is returned as 1, but the custom action is not stopping the installation
when the exitcode is 1 thought the return="check".
my custom action i
Hi,
I have two custom actions one should run on install, one should run on
uninstall, but both my custom actions are running in install only. please
see my wix xml.
Please help me in the rollback.
http://schemas.microsoft.com/wix/2006/wi";>
Hi Rob,
Thanks for the reply. Actually, I just went into details of deferred
actions, and I realised that I don't want my custom actions to be deferred.
I had tried adding teh deferred attribute only so that I could use the
Impersonate attribute.
Also, my custom actions are being invoked at Insta
Hi,
What are the basic steps to create a Transform with DTF?
Regards
Simon Powell
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, p
Hello Guys,
Thanks for your suggestions.
I'd like to share the results here in case if anyone else run into the
same problem.
To begin with, DISABLEROLLBACK switch during uninstall really reduced
the time required to complete uninstallation, from 22 minutes to 7. So,
with this option, the instal
Why doesn't it compile? What's the error that candle/light gives? Are the
custom actions scheduled
in the correct part of the sequence to actually be deferred?
Rob
Nimisha Saboo wrote:
> Hi,
>
> I am new to WIX, and apologise if this has been asked before.
> I am running a setup, that works
Hi,
I am new to WIX, and apologise if this has been asked before.
I am running a setup, that works fine on Widows server 2003, but fails on
Windows Server 2008.
However, if I do "Run as administrator", it succeeds on Windows Server 2008
as well.
What I want to be able to do is;
Either elevate th
> I have a VS 2008 solution with a DTF project and a WiX
> project which uses my DTF custom action DLL. I have manually
> set the project dependencies such that the DTF project builds
> before the WiX project.
>
> Theoretically, a change in the custom action code in the DTF
> project should trigge
There should be a tool in v3 called WixCop that will convert your source files
for you.
Rob
MAKARAND HAZARIKA wrote:
> Hi,
>
>
>
> I am new to Wix, just started learning with the tutorials from
> http://www.tramontana.co.hu/wix/
>
>
>
> The code examples are in version 2.0 but I am using
91 matches
Mail list logo