Thanks! That was just what I was looking for. I did try the /f flag
before but the options I was using weren't working.
Thanks again,
Jeff
> 1. Build a new MSI (with the same ProductCode) that uninstalls correctly.
> 2. "msiexec /fv new.msi" to recache/reinstall your MSI over the bad MSI.
> 3
Although my issue and question isn't wix-specific, it does pertain to
installers in general so I'm hoping someone on this mailing list might
have some suggestions.
I'm working on the installer for my product (using the VisualStudio 2008
Setup Project template) and I've boxed myself into a corner.
hi all,
so i have this situation that i need to place a file to a directory with a
fixed name, but based on the env, the content needs to be copied from different
source.
such as : target file ...\config.xml
sources:
if (prod) prod_config.xml
if (test)test_conf
Thanks!
Jeff
> Not in the stock WiXUI's. You'll have to add your own Dialog to gather
> that information from the user.
>
> See the last section at ->
> http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141
Is it possible to present the user with the option to install for everyone
or just the current user? I know there is the option to explicitly set
the option:
...I just realized that my old installer (built using a VisualStudio
Deployment Project) gives the user an option to pick between inst
Thanks everyone, I got it working now. It turns out it was a combination
of two things:
As Chris suggested, I checked and didn't have an ALLUSERS setting. Since
my previous installers defaulted to "Everyone" I added
And as Neil pointed out, I needed to match the UpgradeCode but the Product
Prior to my upcoming release I used a VisualStudio deployment project to
create the installer. For my upcoming release I've built an installer
using Wix. Everything seems to be working with the exception of
installing the new version on top a previously installed version.
When I run my new insta
I have a similar problem. It doesn't happen 100% of the time, and it
doesn't have anything to do with large number of files (I only have 2 I'm
installing and I've been told it's a bug).
I haven't found a workaround so I added a custom string file
(CustomStrings.wxl) to my project and added:
htt
Is the problem that Wix (and heat) aren't in your path?
What I do is:
1. Start a command console
2. Type in path=%path%;C:\Program Files (x86)\Windows Installer XML v3\bin
3. cd to my DLL's location (in your case it would be your OLB file)
4. run heat.
Jeff
> We're using HEAT to create s fro
Cool! I tried using heat with the suggestions you made:
heat file MyDLL.dll -template:fragment -suid -gg -out fragment.wxs
Then placed what was generated, originally within:
...into my existing:
There is registration information but I didn't include the registration
information portion in the posting because it didn't seem like the values
themselves were the issue - it was getting them written to the registry.
If it helps, here is the entire fragment section which was generated from
heat:
I also meant to add, in my Product.wxs file I essentially have:
...
...
Do any of the IDs in the sections need to match with the IDs in
the section? I've essentially copied the entire output which
was generated by heat and added it verbatim to my
This isn't working for me. I'm harvesting the COM registration info with:
heat file MyDLL.dll -template:fragment -ag -out fragment.wxs
And I have appended my Product.wxs file with the generated output. My
Product.wxs is now along the lines of:
http://schemas.microsoft.com/wix/2006/wi";>
> In general, I personally find the library to be limiting but it does try
> to follow some reasonable design principles for simple projects. It has a
I'm not sure if WiX# ready for prime time or not, as there are parts of
WiX which aren't supported in WiX#, but I've found it helpful in learning
W
I'm moving from a Visual Studio Deployment Project to WiX. In my old
visual studio deployment project I'm installing a DLL and registering it
via setting the Register property to vsdrfCOMSelfReg, and I wish to do the
same thing with WiX. I didn't see anything about registering COM DLLs in
the WiX
http://www.csscript.net/WixSharp.html
As far as info, there is a tutorial on CodeProject on WiX#.
Jeff
> What is Wix# and nbsbuilder? Where can I get more information about them?
>
> Thanks,
> Ken
>
>
> -Original Message-
> From: s...@pacaccess.com [mailto:s...@pacaccess.com]
> Sent: T
This is a timely thread for me as I have been recently going through this
myself. In my research I found there are two ways to bundle the VC++
runtime:
* With a merge module. This approach is documented
(http://wix.sourceforge.net/manual-wix3/install_vcredist.htm) but has the
disadvantage of tak
Thanks for the feedback Phil. Do you have any examples of adding
vc_redist.exe to a Wix install script?
Thanks,
Jeff
> The issue has to do with lots and lots of stuff going on when the C++
> runtime support merge modules are uninstalled. I am not aware of any way
> to stop them, other than by u
My installer is fairly simple and only installs two files. I just added
the VC8 runtime merge module to my installer. Installation time increased
a little, but the time to uninstall increased a lot. Towards the end of
the uninstall, the uninstaller appears to wait for 2:45 and gives the
appearan
Thanks! That solved it.
Jeff
> If you want it to run during the UI you need to sequence it in
> InstallUISequence not InstallExecuteSequence. From that code it's not
> running at the end of installation, it's running at the start of the
> InstallExecuteSequence which is when Windows Installer ac
In my installer, at various times I'm getting a message which says,
"Please wait while the installer finishes determining your disk space
requirements" and then never goes away.
I've searched on this error and from what I've read, this happens when the
MSI doesn't have any components to install.
Cool! That was exactly what I was looking for.
Thanks!
Jeff
> Jeff
>
> I set the name and version information in the Description field of the
> Package definition (as well as the version of the Product). This becomes
> part of the SummaryInfo.
>
> This is available through the file properties
I'd like to add the build number somewhere within the properties of the
MSI which is generated, so I can easily tell the version of my product
which will be installed. I've set:
...but this seems to only set the version the system's Add/Remove programs
sees. (When I get properties on my M
I'm new to WiX and am still getting my feet wet. I've build a custom
action. The action runs after the installation has finished, but I'd like
ti to run at the beginning. Here's what I currently have:
The custom actio
Thanks Cody and Peter. I was unaware of CloseApplication (I'm new to Wix
and still getting my feet wet) but just tried it, and just verified that
it has the behavior Cody described (target app is sent a WM_CLOSE
message), which is NOT the desired behavior I want (which is to prompt the
user to eit
I wish to add a feature to my installer which detects if a certain
application is running, and then presents the user with a message asking
them to quit all instances of the application or abort installation. I'm
new to wix development, but I've searched on this subject and although
I've seen a fe
26 matches
Mail list logo
