Yes I did what's in it but still I keep getting error messages. I'll
elaborate what exactly I did.
I have a directory in "C:\ProgramData\MT\STR" and I want to place a short
cut to this "STR" directory on Desktop using the installation. I placed the
following code in the structure.
Your custom action is failing... try setting CustomAction/@Return="ignore"
On Tue, Apr 20, 2010 at 10:24 AM, Pierson Lee (PIE)
wrote:
>
> Trying to uninstall a service and it fails to uninstall. Log shows:
>
> MSI (s) (68:00) [17:20:43:678]: Invoking remote custom action. DLL:
> C:\Windows\Ins
This sounds like a design problem, not a setup problem and
*definitely* not a WiX problem... you will get a better answer by
asking on stackoverflow.com or some other developer forum.
Some suggestions off the top of my head...
- build a Merge Module that 3rd party apps can consume (and so can
inst
So you want to prevent repair, uninstall and upgrades? Ugh.
If the Product ID isn't changing, Windows Installer should bail
automatically with "Another version of this product is already
installed" from memory, if you're using an automatically generated
Product ID you can use the fact that Windows
Have you tried searching the mailing list archive? This same question
has been asked and answered virtually *every single week*.
The official answer from the team has been "when it's done". Try
asking in another 6 months and you might get a better response :)
Personally I use the irmakebootstrap
Thank you John for your reply.
The IIS 6 Metabase Compatibility is already installed.
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Tuesday, April 20, 2010 2:09 AM
To: General discussion for Windows Installer XML too
Thanks MikeR.
For example, The FileA sets file version , and FileB depends on FileA's
version.
In this case, I write the code as follows :
Is this correct?
Thanks, Akihiro.
> -Original Message-
> From: MikeR [mailto:michael.ru...@gmail.com]
> Sent:
Unfortunately, not supported today.
On Fri, Apr 16, 2010 at 8:25 AM, Anthony Nelson wrote:
> Hey all,
>
>
>
> How can I get the current location of the "located" website?
>
>
>
> For example if I have
>
>
>
> Id="WS.DefaultWebSite">
>
>
>
>
>
>
>
> I would like to change WEBINSTALL
Thanks for the reply
I compared source and MSI extraction using http://winmerge.org/ WinMerge ,
and it showed no difference.
-
Thanks
Jeff in Seattle
--
View this message in context:
http://n2.nabble.com/heat-exe-warning-limit-of-1600-components-per-feature-what-will-happen-tp4928703p4928
Actually, this has been deprecated in Wix 3.5. Windows Installer no longer
has this restriction.
To your questions, WiX would have been fine. The issue would have been on
machines before Windows 2000.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove
On
heat.exe : warning HEAT5155 : Although there are no limitations to the size
of a ComponentGroup, Windows Installer has a limit of 1600 components per
feature. Please consider reducing the size of ComponentGroup
'$(var.ComponentGroupName)' from current count of '3037'.
What is the impact of my ins
Trying to uninstall a service and it fails to uninstall. Log shows:
MSI (s) (68:00) [17:20:43:678]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSI42ED.tmp, Entrypoint: ExecXmlFileRollback
ExecXmlFileRollback: Error 0x80070003: Failed to get modified date of file
E:\PricingManager
Thanks Gary. You are spot on! I just figured this out too but now I am stuck
with HeatProject failing. It looks like the Heat task in Wix.targets does not
honor the RunWixToolsOutOfProc property. This looks like a very simple fix
(just pass the property) -- so I hope this gets into WiX 3.5.
Hea
I think you need to install the IIS 6 metadatabase support for IIS in order to
get this to work for you.
-Original Message-
From: Houssam Hamdan [mailto:houssam.ham...@netiks.com]
Sent: Friday, April 16, 2010 9:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Multiple dummy
To be a little more specific, the _SetDefaultPathValues target is likely
what's causing you grief. It looks at registry keys to try and detect if the
32-bit version of Wix is installed. If so, it sets the WixToolPath property
accordingly. It then checks if the WixToolPath was set, and if not (i.e.
In my case, I just stopped running the Wix tools in process.
true
On Mon, Apr 19, 2010 at 6:21 PM, Navid Azimi-Garakani
wrote:
> I am using WiX 3.5.1602.0. If you look at the executables with corflags,
> you'll see that they are compiled for the 32-bit architecture.
>
> d:\wix\3.5.1602.0>corflags
I am using WiX 3.5.1602.0. If you look at the executables with corflags, you'll
see that they are compiled for the 32-bit architecture.
d:\wix\3.5.1602.0>corflags candle.exe
Version : v2.0.50727
CLR Header: 2.5
PE: PE32
CorFlags : 11
ILONLY: 1
32BIT : 1 <-- 32-bit flag
Signed
I've created an installer for a driver. It installs the driver itself, 32-bit
and 64-bit DLLs and import libraries. 3rd-party applications will link to the
DLL in order to use the driver. I know that I shouldn't install files to
system32, but if not there then where? If I install to Program Fil
Thanks Dave. I don't know why I didn't see that. I looked at it several
times.
On Mon, Apr 19, 2010 at 1:28 PM, Dave Brotherstone wrote:
> On Mon, Apr 19, 2010 at 9:48 PM, Mike Rerick wrote:
>
> >
> > Is there a work-around I can do to get this installer to build?
> >
> > [exec] light.exe
I am attempting to determine if a specific version of a product is already
installed on the system. I basically want to do this to disallow/bail out
of an install if the MSI that is being executed is already installed on the
system.
Here is my authoring using 3.0 RTM. I must be missing something
On Mon, Apr 19, 2010 at 9:48 PM, Mike Rerick wrote:
>
> Is there a work-around I can do to get this installer to build?
>
> [exec] light.exe : error LGHT0001 : Item has already been added. Key in
> dictionary: 'MyWelcomeDlg/Title' Key being added: 'MyWelcomeDlg/Title'
>
Height="60
I am attempting to build an installer with a couple of modified standard
screens in the FeatureTree UI: CustomizeDlg and WelcomeDlg. I copied the
FeatureTree UI wxs file and modified it. The CustomizeDlg screen builds
without any problems. I get an error on the WelcomeDlg - see below. I run
the com
It is not about creating web site, but creating of app pool is failing :(
It is already in bug database.
-Original Message-
From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com]
Sent: Monday, April 19, 2010 6:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cannot Creat
Phil,
Thank you very much for the tip. That's exactly what I'm looking for.
I already started writing a CA DLL for launching both CAs. But I like
the simple solution. If you happen to be in Dallas, TX, let me buy you a
beer. :)
Louis Z.
-Original Message-
From: Wilson, Phil [mailto:phil
If you sign external cabs, you can try the new tool "Insignia". If you use
Insignia, you don't need to use the DigitalSignature element. This tool only
exists in WiX 3.5. To use insignia, don't use any "DigitalSignature" elements.
Sign your cabs, and then run insignia, and it will update your MS
I am trying to create a package that installs a web site on Windows Server
2003, using WiX 3.5.1602.0 (the latest I am aware of). No matter what I do I
get errors like this:
MSI (s) (1C:D4) [16:58:25:165]: Executing op: CacheSizeFlush(,)
MSI (s) (1C:D4) [16:58:25:165]: Executing op: InstallProte
I don't know the exact syntax, but you should be able to just add another to
the Publish, or add another Publish. That Order value (when there is more than
one) is the order you want them to happen in.
Phil Wilson
-Original Message-
From: Zhou, Lei [mailto:lz...@sychip.com]
Sent: Sa
You can make this file a companion file to a file that you know will
overwrite/update properly due to the file versioning rules. There is a
companion file attribute on the File node within WiX, which forces the file
to follow the versioning rules of the specified companion file.
Akihiro.Shibuta
Hi,
I'm signing external cabinets using signtool.exe after the MSI is
created. I would like to learn more about the "DigitalSignature" element
and I'd like to know, how to tighten the security of the setup even more.
Do you have any examples or tutorials describing the "DigitalSignature"
elemen
Hi,
Can anyone help with my question below on Burn? Is there a release data for
this much awaited tool?
Thanks,
--- On Fri, 4/16/10, fiordean dacian wrote:
From: fiordean dacian
Subject: [WiX-users] Burn [Re: Bootstrapper]
To: "General discussion for Windows Installer XML toolset."
Date:
Hi,
How to overwrite forcibly a file which ignores file version and timestamp?
I want to overwrite forcibility a file during patch install or update install,
upgrade install.
The file is set file version, and a file included new msi is older than
installed file.
Thanks, Akihiro.
-
Hi Rob,
I have attached log files for both builds. On build 1602 installer doesn't
pop-up the database already exists dialog. Also it doesn't create the
database or run the scripts.
thanks.
Regards,
Asiri Wanigarathne
http://www.asiri.name
On 17 April 2010 10:48, Asiri Wanigarathne wrote:
>
I've had a look but can't find it. The only other other option that would work
I think is to use
selfreg or create custom actions to call regsvr32, but they have their own fair
share of problems.
Rob
On 17/04/2010 10:06, Thomas Kehl wrote:
> Hi.
>
> Rob, can you remember, where you have read
33 matches
Mail list logo
