WiX doesn't do it, the Windows Installer does. WiX is just the language.
Check out the FileSearch element.
On Fri, Jan 14, 2011 at 6:17 PM, Shaun Hayward wrote:
> I didn't realize WiX had a way to actually retrieve a DLL's version and
> compare against it. I was looking all over for that.
>
>
I'm a purist but I write my custom actions as declarative, data driven
beasties designed so I never have to solve that problem again. That attitude
is where the bulk of the WiX toolset custom actions come from.
Simply put, custom actions will be the most vulnerable part of your install.
Avoid the
The .zip files are only intended for debugging. The real source code is in
Mercurial as pointed in these blogs:
1.
http://www.joyofsetup.com/2010/06/28/wix-source-code-using-mercurial-and-tortoisehg-part-1/
2.
http://robmensching.com/blog/posts/2010/7/19/WiX-Mercurial-TortoiseHg-and-the-command-li
Verbose log file should explain why they were left behind. By default, they
should have been removed.
On Fri, Jan 14, 2011 at 8:44 AM, Wilson, Brian wrote:
> Good Morning,
>
> I am very new to using WiX 3.5, and I think it is awesome so far. I used
> Heat to create a fragment file and was able
I didn't realize WiX had a way to actually retrieve a DLL's version and compare
against it. I was looking all over for that.
Any chance you have a code sample up on your blog?
And I'll be sure to check out the DTF articles on your blog.
Thanks
- Shaun
F
Funny you say that, I was doing some work with KB976477 just today. Some
much
that I have that KB memorized.
I don't use a CA to detect this hotfix. I just use the
AppSearch/DrLocator/Signature tables to search [CommonFilesFolder]\Microsoft
Shared\Office12 for MSO.DLL version 12.0.6520.50
Thanks, Chris!
Funny it should be you that replies. I'm looking at deploying a VSTO add-in and
I've read the related articles on your blog. The custom action is to check for
the presence of KB976477. I think I've FINALLY found a fool-proof (yeah, right)
way to determine if it (or a newer patch
VB/JScript is still a no go. The managed blog was ( thankfully ) O.B.E. when
WiX released managed custom action via DTF.
Personally, if I had the C++ chops, had enough reusable libraries and was
typically shipping unmanaged apps then I probably would be an unmanaged
purist for CA's. Wi
That's a Windows Installer limitation on upgrades.
http://msdn.microsoft.com/en-us/library/aa369786(v=vs.85).aspx
"Note Windows Installer uses only the first three fields of the product
version ..."
Phil Wilson
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasyste
To answer my own question, I had to create:
1 CompilerExtension
1 wixlib
2 Custom Actions (that do the same thing - x86 and x64)
For the CA's I created two shell CAs that both reference a common assembly
(CPUAny) that does the actual work. Each shell builds to its own processor
architecture and
Hi,
I have an installer having 4-part version strings. Our installer stops
installation if a newer version is already installed on the system. We
often have alpha/beta releases of our product in which we do not change
first 3 parts of the product. Suppose we have two releases of our product :
R
I should add that I get a very different output from torch.exe when I remove
the files that are to be added in the patch. These files were added as
components to the top level feature, which is always installed. However, I
cannot see a pattern to what files are included in the .msp torch.exe
output
Hello all, I am having some issues creating a patch and was hoping to get
some insight.
I am using the "Using Purly Wix" guide here:
http://wix.sourceforge.net/manual-wix3/wix_patching.htm and have created
many successful patches with this method. In this latest patch I am adding
two files, and no
Hey all,
I'm trying to make a compiler extension that runs a custom action under the
correct processor architecture (x86 or x64) of the MSI platform.
I've got a A) CompilerExtension that contains B) a wixlib which contains C) a
.NET custom action.
A and C are a .NET assemblies built CPUAny
I've
Hello, WiX Community
I've been playing around with WiX for about a year now and took over my
company's installations (WiX-based) a few months ago. I'm really enjoying it.
I'm looking for some advice on the pros/cons of various ways of writing Custom
Actions. I understand that an issue with the
http://wix.sourceforge.net/manual-wix3/heat.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151
Here's a open question to the group...
I'm sure there are ways to make this happen but should you?
To me this seems a form of configuration data. It's one thing to create a
local
user group and assign that group permissions to something but then how can you
make assumptions on what the
Hi,
I have a problem to register a COM DLL via WiX 3.0. This COM DLL is
dependent on a certain Merge Module that is also installed. From Vista on,
SelfRegCost cannot be used in this case, because it will be called not
until the Merge Modules are installed and COM registration will fail (we
are
Here is my code to add an account to IIS_WPG on IIS6 and IIS_IUSRS on
IIS7.
IISVERSION="#7"
Dave
-Original Message-
From: marric01 [mailto:richard.mar...@.gouv.qc.ca]
Sent:
Good Morning,
I am very new to using WiX 3.5, and I think it is awesome so far. I used Heat
to create a fragment file and was able to access the fragment file in my main
WXS file. In the fragment file, there are entries to create registry values
for some of the DLLs. The MSI is created succe
Hi:
Latest Wix 3.0 source zip:
http://wix.sourceforge.net/releases/3.0.5419.0/wix3-sources.zip
hth
Sean.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 14 January 2011 16:25
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX source c
http://wix.sourceforge.net/releases/
(there is one folder for 3.0.5419.0)
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 14 January 2011 16:25
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX source code download
Hi all,
I want
http://www.joyofsetup.com/2010/06/28/wix-source-code-using-mercurial-and
-tortoisehg-part-1/
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 14 January 2011 16:25
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX source code download
Hi all,
I want to get the WiX sources but on sourceforge I found that they were
moved:
"WiX toolset source and releases move to CodePlex.
June 6th, 2010
The WiX toolset source code and file releases have moved off of
SourceForge to CodePlex"
I went to the:
http://wix.codeplex.com/
but here I c
Google the WixUtil extension. Specifically the Group and GroupRef
elements, and the User element.
http://wix.sourceforge.net/manual-wix3/util_xsd_groupref.htm says
GroupRef is used to join a user to a group.
Hopefully that'll be enough to help you do it...
-Original Message-
From: marr
Hello,
I wanted to know if its possible to add an Active Directory user to a local
group (IIS_WPG).
I know this can be done with custom action writen in C# but I wanted to know
if this was possible inside the WIX.
If its possible, anyone have some code example ?
Thanks
Richard
--
View
Just did some research and think the problem is the sequence for the
files in the cab. As files in InstallShield are not sorted
alphabetically and the sequence number has no gaps (at first glance)
following code with two Lists containing the files in the correct
orders seems to work for me. Hope it
What do you use to zip the files? Can you improve compression to get
your msi smaller?
7zip is usually quite good. http://www.7-zip.org/
Dave
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 14 January 2011 14:21
To: General discussion for Windows Installer XM
I looked at the _Validation.idt file and its formatted perfectly fine. That
means the error is coming from within the Windows Installer API. Given that
the _Validation.idt isn't adding that much data (and is formatted
correctly), I believe you have hit a limitation in the Windows Installer
file for
It's possible we broke backwards compatibility for extensions somewhere
during WiX v3.5. Is there an easy way for me to get the
OSSBuildExtensions.dll?
On Thu, Jan 13, 2011 at 5:58 AM, Wesley J. Miller wrote:
> I have been made aware of WIX by virtue of trying to use OSSBUILDS to build
> gstream
I know from experience that this can be done from an installer perspective.
However, one gotcha that I've seen over the years is that at one company
someone
had written a C++ windows service that would fail if the service wasn't
installed at the service name the application code expected. At
Like you say, multiple MSIs means updates/patches are a headache. You
could instead use "instance transforms". From
http://msdn.microsoft.com/en-us/library/aa369523(VS.85).aspx:
"you can install multiple instances of a product if you have a separate
installation package for each instance of a prod
I have created an installation for Windows Service and everything works
well. Next I need to allow the same service to be installed more times
under different names. For example, if I have the service 'MyService' I
need to install two services MyServiceChart and MyServiceImage. These
names will app
Hi dblock,
Would it be possible to get an example project of what you actually do. I am
very much interested in your approach for handling upgrades.
Regards,
Ducati
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/db-install-thoughts-tp5016287p592
I hit this regularly on XP64 even though my VM has 1 GB RAM allocated (our QA
guys VM's have 2 GB & they see it too). The installer which fails is a 420 MB
MSI (cab embedded).
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.
35 matches
Mail list logo
