I think you meant
"ja-jp"
http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx
:-)
-Original Message-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Thursday, January 05, 2012 5:40 PM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subj
I'm just started digging into WIX this week - sorry if this is answered before
- but searching hasn't been successful. This is part of a migration from
Visual Studio Setup Projects to WIX.
I used dark to reverse engineer the MSI - and there are several assemblies that
the Setup Project Identif
Bill, I'm trying to use the functions that you provided, and I'm just
curious as to where the ExitOnFailure logs are saved? I've placed my
own logs around the function, and I know it's failing somewhere in
there. Thanks.
On 1/3/2012 4:28 PM, Bill Tutt wrote:
> On Tue, Jan 3, 2012 at 5:26 PM,
Here's the equivilant C# code for anyone interested: ( using
Microsoft.Deployment.WindowsInstaller )
ProductInstallation productInstallation =
ProductInstallation.GetRelatedProducts("{9B70A6F1-4A3E-4955-8C34-2D354042B87
E}").First();
string template = new SummaryInfo(productInstallation.Local
Thank you Alberto!
Also thanks to Jon Torresdal for putting instructions on his blog page:
http://blog.torresdal.net/CommentView,guid,001283D1-5C8E-4B16-B369-7008675E2E72.aspx
Using Jon's instructions, I successfully added a manifest and elevation occurs
first. The only downside is I now have a
My problem is solved.
I found I used a wrong cultureid (jp-jp) but not ja-jp, also with adding the
codepage=932 definition in wixlocalization, it built correctly.
Thanks for your time,
Nan
From: Nan Zang
Sent: Thursday, January 05, 2012 5:40 PM
To: General discussion for Windows Installer XML t
No real error checking,just stuck together code using VS 2010 UpgradeCode as a
test:
#include
WCHAR pbuf [40] = {0};
UINT eres = MsiEnumRelatedProducts
(L"{776922EE-1E34-36CE-A15B-82BB65DC183E}", 0, 0, pbuf);
WCHAR localpath [MAX_PATH+1] = {0};
DWORD plen =
Native C++.
-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Friday, January 06, 2012 11:23
To: General discussion for Windows Installer XML toolset.; General
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Querying the package andinstal
I have a Wix project that I have set to allow major upgrades. I'm using
WixUI_Advanced to allow a choice between per-user and per-machine
installs. When I install and upgrade per-user everything works as
expected, the installer recognizes an upgrade and there is only one
entry in Programs and Feat
There are methods on the automation objects that you can call to resolve a
product code that machines and upgrade code then get the file path to the
cached MSI for that product code and then open the database to get access
to the summary information stream and then access the template summary
p
I'm re-posting this as I never got an answer.
Canceling Installing burn generated install results in the following. If
additional information is needed please let me know as I can reproduce this
at ANY time.
Faulting application name: BootStrapper.exe, version: 1.0.0.0, time stamp:
0x4ea1ab8c
Fau
I am sorry, I should have been more explicit in the question: given the
installed product upgrade code how do I find that product architecture?
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Thursday, January 05, 2012 18:58
To: General discussion for Window
Hi,
We created several bootstrapper projects, which include some MSI packages
with option Compressed='no'. As a result the MSIs have to be:
1) available on the file system at the right location (relative to the
bootstrapper) and
2) available in the right version (which means it has to be exactly
13 matches
Mail list logo