Hello Fellow WiX Users,
This is my first post to the mailing list, please forgive any noob faux
pas. Feel free to correct me as well.
I recently delivered a project that installed 8.5 GB worth of files. In
addition to WiX, I used John Robbins' Paraffin tool to automatically
generate the file
Can you provide more detail about what you are trying to build?
-Original Message-
From: Hotmail Acc [mailto:rpat...@hotmail.com]
Sent: Thursday, August 13, 2009 5:50 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Need a Good Template or GUI designer
I am trying to create a
I'm scratching my brain but I don't quite remember: is the limit for a
Windows Installer .CAB file 2GB or 4GB? It seems an awful lot like it is
2GB.
-Original Message-
From: Mike Winfield [mailto:mwinfi...@gmail.com]
Sent: Thursday, August 13, 2009 11:21 PM
To:
Blair,
Many thanks for your reply. It is very assuring.
Checking the Patch element in WiX help file, nothing mentions about
ListOfPatchGUIDsToReplace. It looks like done by Visual Studio IDE. I am
working from command line, do you have an example patch wxs file?
Thanks, Shibo
--
View this
Wix Edit is a free utility with a simple GUI designer.
http://wixedit.sourceforge.net/
-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com]
Sent: 14 August 2009 03:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need a Good Template
Hi
I've been trying to get WiX to install some COM+ components for me and have
thus far failed miserably to get it to work. I've looked at the tutorial and
googled, binged, etc extensively but I am no further forward on day 4 than I
was on day 2 so I seek your help.
I exported TypeLibs from my
When the config file is originally built out it looks fine, all the xml is in
tact. After Wix packages it and I run the setup. You can download the exact
file that is output from the setup from:
www.hughgrice.com/my.config.txt
When I open a DLL in word it looks the same as the config file
Hi,
I'm trying to allow Maintenance mode (Repair and Modify) when the
installation was run from temporary location.
I'm using 7zip packer, which unpacks the MSI, CAB files and bootstrapper
to temporary location and runs it from there. The problem with
installation Modification and Repair is
Hi,
If you only need one language help file per OS locale you could
create a shortcut per language and conditionally install it (and the
chm) depending on the OS locale
(http://msdn.microsoft.com/en-us/library/aa372056(VS.85).aspx), if you
do that then you could even localize the shortcut
Blair,
From Wix Help, Patch family attribute Version:
Used to populate the sequence column of the MsiPatchSequence table in the
final MSP file. Specified in x.x.x.x format. See documentation for Sequence
column of MsiPatchSequence table in MSI SDK.
It says that x.x.x.x format is expected
based on your first email:
Source=$(var.PeritoCase.Client.Shell.TargetPath) /
you have the wrong source for your .config file, fix that and your problem
is likely solved.
/Simon
On Fri, Aug 14, 2009 at 12:19 PM, brendan_rice brendan_r...@hotmail.comwrote:
When the config file is originally
The problem is that the cab is always stripped from the MSI (except on
Windows 7) when the MSI is installed and cached. Programs like MS Office
(and ours) store the installation MSI in a directory on the hard disk.
In our case, we dont let the user change the extraction directory and
extract to a
Hi,
The config file you mentioned is actually the executable, and if
you say one of the dlls is actually the config file then you have either
found a really odd wix bug or you have some filename / source mixups in
your wix. IE the f...@name says it's the config file and the f...@source
is
Hi All,
I want to check for the presence of the .Net framework, so I've followed
the instructions in the WiX help and added the code successfully to the
project. It works fine.
However, to simplify my project slightly, I thought I'd take this code
and put it in a file of its own and
You don't reference anything from this file in your main authoring(s),
that's why it is not picked by WiX engine. You can verify this by
opening the resulting MSI with Orca and see the LaunchCondition table.
What I do in my project is grouping the prerequisites in a separate wxi
(include) file and
Is there any good location for this? How do you do proper uninstall?
Does the MSI also deletes itself or do you leave the installation files
on your users' computers? Does it work with Major Upgrades?
I don't want to be like ATI/AMD who copies the whole drivers
installation to
Those are all good questions and I dont have ideal answers. I can only
tell you what we do.
We use ProgramFilesFolder\our own directory for the extract location
and the files are left there until the user uninstalls the application.
Im not so sure thats a good location but it works on all OSes
Bumped into this today.
http://www.cmcrossroads.com/content/view/13160/120/
looks like a decent starting point if you're looking to build an installer
that needs to work with existing websites.
--
Let Crystal Reports
Peter Shirtcliffe wrote:
It all seems to work and we have a few thousand users since we released
earlier this year. If you find better ways to do any of this, Im sure
the list would be interested to hear what you did, even if everyones
requirements differ.
Burn caches to a predictable
Amy Rosewater wrote:
Action start 14:38:31: RemoveExistingProducts.
RemoveExistingProducts: Application:
20ED61C2-44DA-4CD4-AD05-DBE0F7ACAE7C, Command line:
UPGRADINGPRODUCTCODE={3FB60C36-A33C-49EA-B502-5A75AFEB84A2}
CLIENTUILEVEL=0 REMOVE=ALL
Try that command line from outside the
Thanks Simon. It looks like that was my problem.
Simon Dahlbacka wrote:
based on your first email:
Source=$(var.PeritoCase.Client.Shell.TargetPath) /
you have the wrong source for your .config file, fix that and your problem
is likely solved.
/Simon
On Fri, Aug 14, 2009 at
Hello Wix group.
I'm following
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm to create
a shortcut to my app. I want a menu structure like Programs/Company/Flv
Viewer/shortcut_to_app
Light is giving me the following error:
error LGHT0204 : ICE64: The directory
Hi Dave,
you are right, my source setting was pointing at the dll. Changed it and
everything works as expected, thanks for the help.
B
David Watson-3 wrote:
Hi,
The config file you mentioned is actually the executable, and if
you say one of the dlls is actually the config file
Richard,
Thanks a lot. That solved my problem. I really appreciate all your help.
-Sam.
On Fri, Aug 14, 2009 at 5:36 AM, Richard Hollis richhol...@gmail.comwrote:
Hi Sam
Have a look at these:
http://stackoverflow.com/questions/471424/wix-tricks-and-best-practices
Thanks David.
Conditionally installing CHM file according to OS locale does not satisfy the
requirement. My goal is that the user only install once, then the shortcut
works for all locales. It is OK that the shortcut string is English for all
locales, but this shortcut should load
I have a DCOM component which is an executable file. When the exe file
is executed it self registers and places a class in the DCOM Config part
of the Component serivces. Can anyone tell me what element I need to
use to add the parameters on the property pages?
Thanks,
Jim
Hi All,
I am using wix 3.0 to create the installer to install a website. Is there a
way to set the following website properties using the wixiis extension?
Enable HttpKeep-Alives, Enable Logging and setting the general (log file
directory, log schedule) and Advanced Logging Properties
Or should
Making a patch obsolete (MSI 2.x) is an older technique. All currently
supported/patched OSs by Microsoft currently sport MSI 3.x or higher, which
allows you to use the newer technique referred to as superseding.
They are not the same thing.
The pure WiX patch method only supports the supersede
Fragments are atomic blocks of code that are either incorporated or
ignored based on other fragments referencing them (a lot like functions
being included or ignored by the c/c++ linker based on an already included
code segment).
You could either put this in an include file (like Yan suggests) or
I'm not sure but please tell us what would happen if you did this:
DirectoryRef Id=FlvViewerMenuFolder
Component Id=ApplicationShortcut
Guid={8C6AD672-1062-4286-8EF4-450757FFB281}
Shortcut Id=StartMenuShortcut Name=Flv Viewer
Description=CompanyFlv File Viewer
Are you installing on Vista? Does running as admin help? Is this single
component not depending on anything else? You can use dependency walker and/or
ildasm to find out what dependencies you have.
RegistrationHelper.InstallAssembly does Demand/Assert UnmanagedCode permission.
Jirong -
Have you gotten a solution for this problem yet? I have a similar need.
- TopCat
-Original Message-
From: Jirong Hu [mailto:jirong...@gov.ab.ca]
Sent: Thursday, July 16, 2009 12:09 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] How to
Phil Sayers mentioned this site today
(http://www.cmcrossroads.com/content/view/13160/120/)
CodePlex has this: http://wai.codeplex.com/. It looks like it would solve
that issue as well.
extension was written for a previous version of IIS and the APIs for the
newer IIS are all managed code. I
I'm trying to use a custom action in my setup and getting an error when the MSI
runs. The custom action is a DLL written in C# using the Visual Studio
template for custom actions. It's not executing correctly when I run the
setup. Any suggestions as to what I'm doing wrong?
The entry point
Basically I am looking for a good working sample which has the following
items:-
1) Customizable UI (allow users to select Installdir, single/all user
option, licence dialog etc)
2) do both com and .net dll registration.
3) Add some dlls into GAC and into files InstallDir, commonappdata
4) Add
Your entry point wasn't exported in the DLL you packaged:
http://blogs.msdn.com/heaths/archive/2006/08/14/determine-if-the-custom-acti
on-function-is-exported.aspx
Turns out with DTF projects that you can't reference the right DLL to use
using the Binary SourceFile=$(var.ProjectName.TargetPath)
The errors you are getting (ICE47 ICE57) are from the tests Microsoft
developed to help ensure that MSI databases are both internally consistent
and able to be serviced under all sorts of conditions, like turning
per-machine installations into per-user ones.
rant
Yes, I said, turn a per-machine
Anyone,
I'm obviously new to WIX. This is my first project where we are using WIX to
generate the installer. I've got to say that I will never do it another way
again.
I am having a problem that seems to mean I'm brain dead because it is so
basic. I was developing and testing for XP using
I figured it out. Turns out I has some service registration detritus left
over from earlier testing and it was causing the services to fail. Don't
know why it only happened when both are installed but it works now.
-Original Message-
From: Kevin Gallagher [mailto:ke...@hotmail.com]
Let me guess: your three small apps are native C++.
This is a limitation of the APIs Votive uses to extract information about
other projects in the solution. DevDiv has been trying for a decade now to
kill off native code.
The project references currently only work against msbuild and managed
That was the error. I was including the wrong DLL.
However the
Thanks
Oscar
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, August 14, 2009 3:21 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Custom Actions
Your entry
I found the blog I was looking for:
http://blogs.msdn.com/jasongin/archive/2008/05/23/custom-action-project-temp
lates.aspx
In that blog entry, he shows this:
Fragment
Binary Id=MyCustomAction.dll
SourceFile=$(var.CAProjectName.TargetDir)$(var.CAProjectName.TargetName).CA
.dll /
Ah... thanks for the slightly disapointing answer, at least I know my
installation isn't wack
brian
From: Blair os...@live.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Friday, August 14, 2009 7:37:54 PM
43 matches
Mail list logo
