> In theory, you should be able to pass UserLanguageID or
> SystemLanguageID as a MsiProperty to apply a transform to a
> MSI package.
This was my idea. But the question was about a pointer to information
how to do this. Can similar be read in any example project?
Regards
Helge
-
Well, it's a bit strange when I just entered all my UI in the MSI
installer declarative as XML and have now to write a native
application with the UI. But if it is the way to go I will follow it.
The documentaion
(http://wix.sourceforge.net/manual-wix3/bootstrapper_application.htm)
tells me that m
Are there any blogs or other publications that a beginner of burn
should read before the WiX 3.6 edition of Nick Ramirez's book is
delivered?
Regards
Helge
2013/2/23 Helge Kruse :
> Hello,
>
> I use WiX before, but am completely unexperienced with burn.
>
> I have build loc
2013/2/25 Chaitanya :
>
> In the WIXUI_InstallDir,i want the change the logo.
>
> How to change,can u tell me the suggestions,
I think it's worth to read "user interface"/"UI wizardry" in the
tutorial: http://wix.tramontana.co.hu/
Regards
Helge
---
Hello,
I use WiX before, but am completely unexperienced with burn.
I have build localized .msi packages. I have further read that one can
build a transform (mst) that is more-or-less a diff file between the
localized .msi packages and run msiexec with command line arguments that
will combine
Neil,
thanks that works perfectly. Obviously VS2008 tried to execute candle
without creating a new process. This might save time when executing
but gives trouble when a different run-time version is required.
Your answer save me the evening.
Thanks, Helge
2013/2/19 Neil Sleightholm :
> I believe
in VS2005 still fails although ProjectAggregator2
is installed.
Regards
Helge
2013/2/19 Helge Kruse :
> Now I tried to use VS2008. This shouldn't need
> ProjectAggregator2.msi. Now I get this message:
>
> '...wixproj' cannot be opened because its project type (.wix
/ResetSkipPkgs" did not help.
How can I check, that the support for WiX is installed in Visual
Studio and how can I repair this?
Regards
Helge
2013/2/18 Helge Kruse :
> Hello
>
> I have used WiX 3.5 until today. Now I just wanted to upgrade to WiX
> 3.7 and ran the installer.
Hello
I have used WiX 3.5 until today. Now I just wanted to upgrade to WiX
3.7 and ran the installer. Now I can compile with the new tools.
Unfortunately I can't edit any .wxs file in VS2005 anymore. When I try
to create a new WiX MSM project in VS205 I get the error message:
The application for
Steven, thanks for reply.
> Did you change the Product Id="some GUID">
Yes, the GUID is auto-generated each time when WiX compiles the
source. This is defined by the . But just for
completeness: I just generated a new GUID and repeated the test,
without success.
> DowngradeErrorMessage="A ne
I want to install my first major upgrade. The older product MSI
version 1.05.02 has been build with InstallShield. Let's say the
UpgradeCode of the old product is
---5-6.
My new installer has the same UpgradeCode as the old product version.
The upgrade should be
I write a merge module that includes a local server MyProg.exe. This
server has a lot of COM Classes that must be registered.
I know the method with RegSpy to generate a registry file and to
harvest with "heat reg". This has the drawback that it generates each
registry value as an indivual compone
ding, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
>
> -Original Message-
> From: Helge Kruse [mailto:helge.kr...@gmx.net]
> Sent: 13 December 2011 06:34
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Detect VC++ runtime
registry search.
>
> http://blogs.msdn.com/b/astebner/archive/2010/05/05/10008146.aspx
>
> Phil W
>
> ________
> From: Helge Kruse [helge.kr...@gmx.net]
> Sent: Sunday, December 11, 2011 11:11 AM
> To:wix-users@lists.sourceforge.net
> S
Detlef,
this mailing list does not support attachements. So we can't find your problem
with the information in your mail.
Regards,
Helge
Original-Nachricht
> Datum: Mon, 12 Dec 2011 09:31:55 +0100 (CET)
> Von: "Detlef Amende"
> An: wix-users@lists.sourceforge.net
> Betreff:
The WiX help recommends to deploy the Visual C++ runtime using merge
modules. I refer to section "How To: Install the Visual C++
Redistributable with your installer". While this is possible, I don't
want to include the MSM in every MSI I will generate. Instead I prefer
to add this to the bootst
27;t harvest the project references.
> But I would like to know if in 3.6 they're planning to take that out or
> whether its just a bug that causes heat.exe not to be called at all.
>
> On Sat, Nov 12, 2011 at 5:54 PM, Helge Kruse wrote:
>
>
>> I had the same exprience
I had the same exprience that harvesting is dropped in Votive/(WiX3.6).
I thogh there was a documentation for Votive that explicitly describes this
harvesting. Can you help me with a pointer to this documentation/tutorial?
- Original Message -
From: "Dandre Jansen van Vuuren"
To:
Sent:
.pdb' />
>
>
> (We always package our binaries and PDBs together to get better error
> reporting in the field)
>
>
> -Original Message-
> From: Helge Kruse [mailto:helge.kr...@gmx.net]
> Sent: Monday, November 07, 2011 12:11 PM
> To: wix-users
Am 06.11.2011 19:18, schrieb Harper:
> As far as I remember correctly, one advantage of Votive was the simple
> integration of other projects output to a WiX project. Am I wrong here? What
> does the Harvesting group in the Reference properties means?
> Current settings: Harvest=True, ProjectOutput
ow to react
> when a dependency is not installed on the target system. I guess I see this
> as a WiX Cookbook Wiki.
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please
inter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
> --- On Mon, 5/16/11, Helge Kruse wrote:
>
>
> From: Helge Kruse
> Subject: Re: [WiX-users] Detection of run-time DLLs
> To: wix-
ment PC but does not run on a
system where this run-times are not installed.
Helge
>
> ---
> 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
>
> --- On Mon, 5
Hello,
I know from InstallShield (IS) that it is capable to detect all the
dependencies of a binary to run-time DLLs.
When VS2005 C++ DLL uses the msvcrt IS adds the corresponding MSM to the
project. How can do similar with WiX 3.5? It would includ this tasks:
- detect automagically which run
Hello,
it's my first try to localize my setup. I am using WiX 3.5.
The Product.wxs has these lines besides all others defining files etc.
My localization files are:
http://schemas.microsoft.com/wix/2006/localization";>
1033
LicEN.rtf
http://schemas.microsoft.com/wix/2006/localization";>
1
Am 03.05.2011 18:30, schrieb Kurt Jensen:
> The full command line contains over 70 other projects with variable
> definitions all of which contain one or more "."
>
> None of the other $(var.Spiricon..TargetPath) is listed as an
> error.
>
>
>> -dSpiricon.Factory.Manager.TargetPath=E:\BaseI\CodeBas
Hello,
I know that a MSI file can handle only one locale. So I need a bootstrapper to
select a MSI file on customer's choise. Where can I find information, how this
can be done with WiX? I assume this can be a frequently asked question.
Thanks,
Helge
--
NEU: FreePhone - kostenlos mobil telefo
27 matches
Mail list logo
