Since Sudripta is in-house, I contacted her and took a look at the msi's. There
are some component rule violations happening here. :)
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com]
Sent: Friday, December 12, 2008 3:02 PM
To: General discussion for Windows Instal
That doesn't sound like a full log - a full log would detail exactly what file
is being overwritten and why. Something like this for the component:
MSI (c) (E8:F8) [16:20:56:127]: Disallowing installation of component:
{1CA051B0-1B70-11D2-9ADD-006097C4E452} since the same component with higher
It is uninstalling the previous installation correctly. I can see no files from
the previous installation being there. The MSI log also doesn't state much. It
only says that installation was successful. It shows every installation step as
success.
Sudripta.
Re: [WiX-users] Upgrade MSI havi
That should work, so a likely problem is that maybe the upgrade isn't actually
uninstalling the older product, then your 2.5 files won't replace the 5.1
that's still on the system. That placement of REP should completely uninstall
the old product first, so either that upgrade is not happening or
Are the files in question assemblies being installed to the GAC?
Also, why are you lowering the version of the files?
-Original Message-
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su...@microsoft.com]
Sent: Friday, December 12, 2008 12:30 PM
To: wix-users@lists.sourceforge.ne
Right, so add a CreateFolder element under the Component. What version of the
WiX toolset are you using? I thought this was done automatically... but maybe
not.
-Original Message-
From: Cromwell, Ryan (LNSSI-Dayton) [mailto:ryan.cromw...@lnssi.com]
Sent: Friday, December 12, 2008 12:35
Ideally, you should never need to specify action/@Sequence attributes.
Instead, use the "Before"/"After" attributes. In your case:
OLDFOUND
Much easier to maintain.
-Original Message-
From: Adriana Rodean [mailto:adrya1...@gmail.com]
Sent: Friday, December 12, 2008 12:14
To: wix-users
I agree, I wrote an extension, still needs a bit more work.
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Friday, December 12, 2008 12:43
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Help please, doesn't execute httpcfg
I included and empty xml file in the installation then I used xmlfile to
write everything I needed to into the file.
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Friday, December 12, 2008 3:40 PM
To: General discussion for Windows Installer XML toolset.
Su
I while back I asked whether there should be HttpRegister action so you
do not have to use httpcfg.exe. Never got any feedback, but I still
think it is a good idea, especially with the wide spread of WCF.
--
SF.Net email i
I want to create app configuration (xml) file from scratch during
install process. XmlConfig requires File attribute, and there is no
"CreateFile" action. How do I do this?
--
SF.Net email is Sponsored by MIX09, March 18
This is the error...
error LGHT0204: ICE18: KeyPath for Component: 'StartService1Comp' is
Directory: 'INSTALLDIR'. The Directory/Component pair must be listed in
the CreateFolders table.
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Friday, December
Hi,
I am facing a problem regarding creating an upgrade MSI. Our previous
installation package (msi) had some files which had a higher version than our
current installation package (msi). The files in the previous installation had
a version of 5.1.. The files in the new installation pack
Hi,
Figured out what was the problem, it did execute the command, but on
installation it did rollback imediatly after it.
So correct code is:
OLDFOUND
>
>
> After="InstallService">$OPGatewayComponent>2
>After="UnInstallService">$OPGatewayComponent=2
>
>
1. svchost has its own servicing issues.That was more because
there were just too many system services running in separate processes. My
understanding is that a fair bit of Win7 perf is coming back because they are
reducing the number of system services. Think about that next time you cre
You should talk with the svchost group then, but yes I agree. :P
What would suggest in the way of conditionally starting the service upon
feature selection? Currently if I create a component with a single
ServiceControl element and add that to a feature, it balks about not
having any Files (or s
TARGETDIR and SourceDir are Windows Installer concepts, standard Directories.
Documented in MSI SDK.
Those $(var.) things are WiX concepts, preprocessor variables. Documented in
WiX.chm (Preprocessor topic).
You can see the preprocessor variables passed by Votive to candle.exe on the
command
Heath, is this maybe related to the Binary bug you're tracking in pyro?
-Original Message-
From: Scott Sam [mailto:s...@clearviewecm.com]
Sent: Friday, December 12, 2008 07:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Error 2721: Custom action not f
Windows Installer doesn't really support that scenario unfortunately. They
require the ServiceInstall to point at the KeyPath of the Component (the File
in this case) and you can't duplicate the file in different Components...
unless the file is in different directories.
Basically, putting mul
Sorry, and that tag is incorrect for the RBG.
Should read
cemiles wrote:
>
> You could set up a radiobuttongroup control and tie that condition
> property to it.
>
> So, something like this would be the short version for 1 property
> DATABASEUSER:
>
>
>
>Title="!(loc.DBUser
You could set up a radiobuttongroup control and tie that condition property
to it.
So, something like this would be the short version for 1 property
DATABASEUSER:
ISINTEGRATEDSECURITY=0
ISINTE
I have successfully created an install which uses the same EXE to
install two different Windows Services using ServiceInstall. It was
pretty simple. Looks something like this:
My dilemma is figuring out a way to have two distinct Features for each
service.
If they
In article <4941b98f.1040...@joyofsetup.com>,
Bob Arnson writes:
> Dale Quigg wrote:
> > I have a custom dialog and when I press "Next", I want a custom action to f
ire to check a value in an edit box. If the CA detects an error, I want it to
display a dialog (which does not work apparent
Is it possible to include a new feature inside of a patch that didn't exist
in the original msi?
I've been reading about this and from my understanding if it's not at the
top level, it should be okay. So I've nested the feature directly within an
existing feature, but still can't compile the msi
Hi,
My setup project is Setup.wixproj, in the .wxs file, can I use
$(var.TargetDir) or $(var.ProjectDir) to refer to the related path?
For the target directory, I have this section before I use the
var.TargetDir so I assume I don't need to redefine TargetDir variable,
is this correct?
Also here is the relevant part of the log.
Action 10:11:59: RemoveCasPol.CustomActionData.
Action start 10:11:59: RemoveCasPol.CustomActionData.
MSI (s) (14:C0) [10:11:59:116]: Transforming table CustomAction.
MSI (s) (14:C0) [10:11:59:116]: Transforming table CustomAction.
MSI (s) (14:C0) [10:1
I'm trying to create and apply a patch. I can create the patch without
any errors or warnings. When I go to apply it I get the error "Error
2721: Custom action RemoveCasPol not found in Binary table stream".
How can I fix this?
Here is where I declare my custom action:
Here is where
There is a good explanation of how it to do it here:
http://wix.mindcapers.com/wiki/Upgrade
If you add RemoveExistingProducts to the InstallExecuteSequence after
InstallFinalize, it will do what you want in terms of only upgrading the
files you want. (see the link to the MSDN article for an exp
28 matches
Mail list logo
