I am out of the office until 01/12/2010.
Please email Cognos RD Build Engineering Support or for urgent matters
contact Robert Lyonnais or Ben Fowler.
Note: This is an automated response to your message "Re: [WiX-users]
Saving the MSI file" sent on 11/30/10 17:02:40.
This is the only notific
After Several days of trial I cracked down the problem, I was using sca.wixlib
for certificate installation, when I removed the WiXlibrary from my setup and
created patch, it works fine!!!
No Idea why.
With best regards,
Mahesh D
-Original Message-
From: Blair [mailto:os...@live.com]
Yes. Althought I believe it's better to use PackageCode rather then
ProductCode
to make sure that it's unique.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message ---
If I understand correctly, I could change my bootstrapper to extract the MSI
file (which is embedded as a resource) into [LocalAppDataFolder]\Downloaded
Installations\{productid} instead of [TMP] like I do currently, and then run
MsiInstallProduct directly on that copy?
--Quinton
-Original
Some code that does that in C++ here:
http://msiext.codeplex.com/SourceControl/changeset/view/70150#816758.
-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Sunday, November 28, 2010 5:08 AM
To: General discussion for Windows Installer XML toolset.
Subjec
Well, that could happen no matter where you put it. InstallShield puts it
in [LocalAppDataFolder]\Downloaded Installations by default but I'm not sure I
agree with that. They do this ( as I recall ) so that a setup.exe manifested
as Invoker could cache the file for a standard user. Problem (
Where do you cache it to? Everywhere else I thought of won't get cleaned up
and/or might get erased prematurely (e.g. TMP folder).
--Quinton
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, November 30, 2010 2:03 PM
To: General discus
I usually just let my bootstrapper handle the caching for me before invoking
the
MSI.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Quinton Tormanen
This issue must have discussed dozens of times, but I couldn't find
anything. Quite simply, I want to ensure that our full MSI file is
available for repairs later (there's a issue currently out of our
control that makes this necessary related to the DifxApp toolkit). Our
MSI is only 12MB and the be
Unfortunately, the files are part of a driver package that I don't want
to mess with.
I'm consider (brace yourself) of doing the REINSTALLMODE=amus thing
since all files are
within our install folder. Anything less ugly?
--Quinton
On Tues, Nov 30, 2010 7:06 AM, Rob Mensching
wrote
>
> Wow. Uhh,
No. Looking at the log, it appears that the decision to skip those
components was made in CostFinalize so it doesn't seem like it'd help.
Thanks though.
--Quinton
>Peter Shirtcliffe wrote:
> Have you tried moving RemoveExistingProducts to before
InstallInitialise?
> That worked for us in a simil
We use the FT245BM. We use our own PID and have a resold driver, but we
kept the filenames the same since they didn't support it. We have
certified the resold driver updated for our VID/PID.
I would not be surprised if what you're seeing (issue #2) is related to
the driver not being signed. I have
How do you code against something you can't build against? How do you know the
source file will actually compile? How do you test your installer in-house?
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
atten
Hi:
I could, but I don't have access off-site, it's a proprietary app!
Cheers
Sean.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 30 November 2010 19:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] using
Why do you compile after you install? While this is common in the Unix
world, in the Windows world we typically compile then package for
installing. Is there some licensing issue you are trying to skirt around or
something? It seems like you could just include the other application into
y
Guys, I appreciate the reply.
Do you have any suggestions on how to accomplish this? If I understand you
correctly, you are referring to a "status code" that might be presented in
the (verbose?) log ?
Parsing the log was something I have thought about, but it is really going
to add more complexit
Hi Chris:
Ok, to answer your questions:
This package integrates with another application. Basically it installs a
source file in to a directory which doesn't matter. It then runs a custom
action to compile the source to binary form. Due to the fact that the customer
hasn't paid for source code,
This just doesn't sound right for an installer and would require a review of
your application architecture to properly answer. Understand that if the
source
code is in the installer, anyone can get to it even if you don't install it.
Also I wonder if the source file is being customized durin
Hi:
I'm using the WindowsVolume property in two DirectorySearch elements.
I need to use a DirectorySearchRef element in the second case.
Given that I need to use the WindowsVolume property as the reference what
should I set Parent to, or can I leave it blank as in "".
Cheers
Sean.
On 11/30/2010 07:06 PM, wixNewbie wrote:
> DEBUG: Error 2769: Custom Action UninstallCertificates did not close 3
> MSIHANDLEs.
It is the same problem described in this ticket:
http://sourceforge.net/tracker/index.php?func=detail&aid=3105643&group_id=105970&atid=642714
It should be fixed in late
Ah of course. I now see what Rob meant about Component/@Directory that
is probably cleaner than using Component/@Feature and more flexible if
ComponentGroups are in multiple features.
Thanks
Neil
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 30 November 2010 17:38
To: 'Ge
Hi:
This would work, all the custom action needs to do is call an executable on the
target system--seems overkill?
Any other options?
Cheers
Sean.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 30 November 2010 17:13
To: 'General discussion for Windows Installer XML toolse
Here's how I have done what you seem to want to do:
"ComponentGroup" file:
Main file:
...
...
...
But in my case, I often have several features and several directories and I
want to assign several related c
There are two types of "error" codes in windows installer: internal "status"
codes and external "result" codes. As you noticed, the catchall for the
external codes tends to be 1603. Sometimes, however, the internal codes that
end up in a detailed log are actually more useful.
If you have the abili
Have your custom action code retrieve the source file from the Binary table,
perhaps?
-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Tuesday, November 30, 2010 7:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] using a
In response to #2: It looks like you are using the same / similar hardware
that we do. We also use an FTDI product (FT232R). However, there are some
differences:
(a) We use our own product code so as not to mix the device up with normal
FTDI devices.
(b) As a consequence, we renamed and modi
Hi all,
I am seeing error in custom action uninstallcertificates on uninstalling
a web application in iis.
Is there a setting I am missing in my code pasted below?
DEBUG: Error 2769: Custom Action UninstallCertificates did not close 3
MSIHANDLEs.
The installer has encountered an unexpected
Absolutely; handling rollback scenarios can increase the complexity
surrounding file removal several-fold.
(But when there aren't specific timing requirements, you just run such
a delete from the commit phase.)
Given that there is no clear way to know the future upgrade paths
(does anyone ever pr
After installing a msi built with wix i need to re register msiexec to
install/uninstall other msi.
steps
1) Install my msi
2) After this i can install/uninstall this msi or others.
3) After some time (minutes), i can't install nor uninstall any msi. The
message displayed is "The windos insta
Broken Link. The correct one is http://wixcontrib.codeplex.com/
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, November 30, 2010 9:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [BUG/limitation in WIX/MSI]N
Ok time to eat humble pie - I managed to completely confuse myself.
WixUI_Advanced doesn't have a welcome page but WixUI_FeatureTree,
WixUI_Mondo and WixUI_InstallDir do. Somewhere I swapped to
WixUI_Advanced when building my install and it just so happened that
coincided with the v3.5 upgrade. Ye
What I was hoping was to simplify this sort of structure as I always end
up adding a Component and forgetting the ComponentRef:
Then is my main file
In WiX 2 there was a FragmentRef a
Hmm, not my strong area but you might check to see that MigrateFeatureStates
is run before your check runs.
On Mon, Nov 29, 2010 at 8:20 PM, Loofsr wrote:
>
> G'day All,
>
> I am trying to display a MessageBox only if a feature has been selected and
> only if IIS 6 Compatability is NOT turned on
Should just work. What problems are you having?
On Mon, Nov 29, 2010 at 7:10 AM, Brian Pang wrote:
> I have a need to allocate a 64K size in a property value for storage. This
> is
> to keep feature compatibility with a previous Wise Installer.
> What is the best way to do that in WiX or is it
WiX toolset uses the browse dialog in its install. You might look there.
On Mon, Nov 29, 2010 at 1:09 PM, wixNewbie wrote:
>
> Hi,
>
> Can someone share an example or directions to display directory selection
> dialog using the browsedialog?
>
> The code below does not work
>
> Height=
Getting the RemoveFile table entry right is *a lot* easier than getting
rollback correct in all the cases it is required. The RemoveFoldersEx custom
action does the same sort of work in the http://wix-contrib.codeplex.comproject.
On Mon, Nov 29, 2010 at 7:02 AM, Michael Urman wrote:
> The trick
Hi:
I'm in the process of creating an installation whereby the installation
compiles some source code on the customers machine and then needs to delete the
source file but leave the binary representation.
What is the best way to do this without installing the source file.
Cheers
Sean.
---
Wow. Uhh, easiest fix is probably going to be to release the 1.1 DLL with
the version 1.3. Time travel is hard so just go forward naturally.
On Mon, Nov 29, 2010 at 11:00 AM, Quinton Tormanen wrote:
> Perhaps this question has been answered before, but I couldn't find
> anything in the wix-users
Sadly, no.
On Tue, Nov 30, 2010 at 5:33 AM, Andy Clugston wrote:
> Hi All,
>
> After doing some searching, it seems that the general understanding is that
> Windows Installer does a poor job with exit codes returned when an MSI does
> not complete "successfully" for some reason. A case that we h
Personally, I find the Component/@Directory more useful to put my Components
in a Feature instead.
On Tue, Nov 30, 2010 at 5:31 AM, Bob Arnson wrote:
> On 30-Nov-10 02:43, Neil Sleightholm wrote:
> > The problem with this is that there isn't a reference to any of the
> > components in the main i
Has anyone installed a kernel-mode driver that doesn't have an INF file? I
know not all drivers
have them since there's documentation from Micrsoft about signing drivers that
don't. Specifically
I'm trying to install a build of the dokan file system driver. The
instructions from dokan are t
I'm confused, I am sure the behaviour is different between 3.0 and 3.5 -
I will knock up a sample to demonstrate and either attach it to the bug
report or close the bug report.
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 30 November 2010 13:29
To: wix-user
On 30-Nov-10 02:43, Neil Sleightholm wrote:
> The problem with this is that there isn't a reference to any of the
> components in the main install so none of the components are included in
> the msi.
Component/@Feature doesn't change the requirement that references flow
from the entry section to
Hi All,
After doing some searching, it seems that the general understanding is that
Windows Installer does a poor job with exit codes returned when an MSI does
not complete "successfully" for some reason. A case that we have encountered
is where we are preventing downgrades for our install package
On 30-Nov-10 02:17, Neil Sleightholm wrote:
> If you run the install on a clean machine then the welcome page is
> displayed during the initial page and then it jumps straight to the
> licence page.
That's not the welcome page; it just looks like it.
https://sourceforge.net/tracker/?func=detail&a
I can't say I agree with the WiX help topic "How To: Install the Visual C++
Redistributable with your installer". It's generally accepted that shipping
3rd party merge modules creates servicing issues so why is it suddenly
acceptable to do it in this case? I suspect the choice to document the
Actually you can write a custom action scheduled after PublishProduct to
directly update value. Checkout:
http://stackoverflow.com/questions/317647/using-the-estimatedsize-value-inside-a-program-uninstall-key-to-correctly-display
Christopher Painter, Author of Deployment Engineering Blog
Have
On 29 Nov 2010, at 18:52, Wilson, Phil wrote:
> This may be an issue with the SxS and policies depending on your OS. Some
> people install the redist with the vcredist exe which also installs publisher
> policy that redirects everyone up to the newly installed libraries. Some
> people install
There isn't much you can do. The Windows shell estimates the size for
you. Those other programs are lucky.
You used to be able to set ARPSIZE but that is ignored from Windows XP
SP2 onwards.
Theres an old thread with a link to some (old) detailed information here
http://windows-installer-xml-wix-to
Have you tried moving RemoveExistingProducts to before InstallInitialise
? That worked for us in a similar situation.
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: 29 November 2010 20:23
To: General discussion for Windows Installer XML toolset.
Subject
Hi Thomas,
Thanks a lot for posting the code for this. Because I need the CA to be
run only when uninstall, not also through an update, I conditioned the
CAs, so the code looks like:
REMOVE="ALL" AND NOT
UPGRADINGPRODUCTCODE
REMOVE="ALL"
AND NOT UPGRADINGPRODUCTCODE
and it works as exp
Hi Sean,
Would be great if you would post the code here. There are so many
unanswered posts about this issue that you most probably will make a lot
of people happy.
Thank you,
MeCoco
On 11/29/2010 4:43 PM, Sean Farrow wrote:
> Hi:
> That's what I'm in the process of doing for a very similar si
Hi Peter,
Thanks for the link. I'll have a look.
MeCoco
On 11/29/2010 4:04 PM, Peter Shirtcliffe wrote:
> I see why you need a custom action. Your best approach is to have your
> custom action write temporary rows to the RemoveFile table and let
> Windows Installer do the deleting for you. That
Hi Michael,
Thanks a lot for the explanation and for the link. I'll take a look, as
this would be the "approved" way of doing this.
If one wants to do that with CA, then the code would be (I'll put the
code here for further reference):
REMOVE="ALL" AND NOT
UPGRADINGPRODUCTCODE
REMOVE="ALL
Hi:
I have the following in a wix library file:
When using the DirectorySearchRef element, does the depth property of an
underlying DirectorySearch element refer to t
55 matches
Mail list logo
