Hi Anton.
Thanks for the reply.
Project I saw had a reference to wixproj. The reference properties had
description as "WiX project reference", which is why I felt if wixproj could
be referred?
-Original Message-
From: wix-users-requ...@lists.sourceforge.net
[mailto:wix-users-requ...@li
Hi Dirk,
Thank you for your reply. I tried the way as you suggested that write an
setup.exe with dialog, where the user can select the language. The next button
will call the appropriate language msi to install the package. Therefore, the
setup.exe is only a small program to perform the languag
Hi Chunyan,
do you have one msi per language? If so, you could merge them into one msi
and call it with the necessary TRANSFORM parameter to use the correct
language.
I've done that and am pretty satisfied with the outcome.
Hope it helps,
Dirk
2009/7/14 Jiang, Chunyan (GE Healthcare)
> Hi Dir
On 14 Jul 2009, at 05:29, Igor Lemsky wrote:
> I have x64 Windows XP. I tried to make 64 bit package by setting
> attribute:
>
> and during compilation got an error:
> light.exe : error LGHT0310 : Failed to open package for validation.
> The
> most common cause of this error is validating an
Anton de Wit wrote:
> Now I have a problem. I'm using the 5419 build of Wix 3 and started out
> doing the same. Place files in GAC and create registry keys.
If your VSPackage is in the GAC, it's not available until the setup is
finalized, after InstallFinalize, so trying to run VS90Setup then wo
zhihai guo wrote:
> In reality I just don't want the uninstall can be interrupted.
>
Installation can always be interrupted, even without a cancel button.
Your setup should tolerate that with proper rollback.
--
sig://boB
http://joyofsetup.com/
---
Makrai Jozsef wrote:
> I could get things this far is to use different product/package codes,
> which seems to imply different entries in the "add/remove progs" list.
> There is no clear ordering between the modules, so making them as upgrades
> doesn't seem viable. And merge modules, AFAIK, can on
Igor Lemsky wrote:
> I have x64 Windows XP. I tried to make 64 bit package by setting attribute:
>
> and during compilation got an error:
> light.exe : error LGHT0310 : Failed to open package for validation. The
> most common cause of this error is validating an x64 package on an x86
> system. To
Hi,
I create simple wix installer, I want add 5 *.dll file to my
specjal folder in "Program Files"
I can compile without errors or warnings in Visual Studio 2008, but
when I run compiled installer, I have only 3 from 5 *dll files.
---
Thanx for your reply! I'll dive into it first thing tomorrow.
Cheers,
Anton,
On Tue, Jul 14, 2009 at 2:03 PM, Bob Arnson wrote:
> Anton de Wit wrote:
> > Now I have a problem. I'm using the 5419 build of Wix 3 and started out
> > doing the same. Place files in GAC and create registry keys.
>
If you are using the visual studio plugin "Votive"...to link to
wixca.wixlib...add a reference to "WixUtilExtension", the same way you would
add a reference to any 3rd party assembly.
You can find it located here:
C:\Program Files\Windows Installer XML Toolset 3.{some
version}\bin\WixUtilExtension
Without a log file it's hard to tell what happened. Try running your
installer with a log file msiexec /l*vx installer.log /I Your.msi
-Original Message-
From: A.S [mailto:ansic.s...@gmail.com]
Sent: Tuesday, July 14, 2009 8:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
Out of curiosity, did you mark any off your 5 DLLs as Assembly=".net" ?
-Original Message-
From: Michael Clark [mailto:mcl...@fullarmor.com]
Sent: Tuesday, July 14, 2009 8:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] create installer with dll
W
Hello WiX Community,
I've just done "cvs up" and built WiX 3.0, but I've got 3.0.5412.0
version as an output, not 3.0.5419.0, which is a release.
Does anyone know why version don't correspond? I assumed that starting
from July, 4 there should be 5419 revision...
Thanks.
-- Yan
---
I thought that this kind of dialog - choosing start menu folder - is rather
common...
Does anyone have a working sample by any chance?
Natalia wrote:
>
> Hello all,
>
> I'm facing the problem while trying to make a dialog for choosing start
> menu folder for creating application shortcut.
>
>
this is this code,
all DLL is ~ 11 MB,
but my setup.exe <5 MB
Can You check my code? I think, i make mistake w
You may want to check the root folder (C:\) to see the files were placed there.
I've had setups in the past in which the files ended up being placed there.
Matthew Yost
Software Engineer
GLD Solutions, Inc.
-Original Message-
From: A.S [mailto:ansic.s...@gmail.com]
Sent: Tuesday, July
Please remove Name attribute from the element. Also avoid the
hardcoded guids. I hate duplication :)
2009/7/14 A.S
> Guid="3AD63215-4F9E-4416-A24F-A5CF91F86329">
> Name="Microsoft.Office.Interop.dll"
> Source="../zzz/Microsoft.Office.Interop.dll" />
It appears that we are still using version 2 of wix, not 3...and so I do not
see WixUtilExtension.dll
Is there a way to do this in version 2 of wix?
From: Phil Sayers [p...@cds-am.net]
Sent: Tuesday, July 14, 2009 6:36 AM
To: 'General discussion for Windo
Hi All
In this article, MS gives a solution for the above issue: replace DPCA.dll,
generate the msi, and run the EnableHostHeaders.js against the msi file to
insert a new screen.
http://support.microsoft.com/default.aspx?scid=kb;en-us;821335
Now this project is using Wix 2.0 creating the msi fi
Hi All
This article tells how to add customized screen in Wix 2. It's very easy to use.
http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
How can I add a screen in Wix2? We have one project still used Wix2.
Thanks
Jirong Hu
Build Master
780-644-5488
This communic
I took WiX3.msi and decompiled it using dark.exe. I got the wxs also working.
Then, re-compiled the project and was able to successfully install the new msi.
Where can I get the Custom Actions and their source?
Am I looking at the right WiX Installer source or is there some ot
Bob Arnson wrote:
>> This is similar to "plugin" installations where the plugin later needs
>> to
>> be uninstalled together with the main product. Is there a good solution
>> for these cases?
>
> MSI doesn't support that. However, composing a product of multiple MSI
> packages is increasingly com
Can I make my installation without cancel button?
2009/7/14 Bob Arnson
> zhihai guo wrote:
> > In reality I just don't want the uninstall can be interrupted.
> >
>
> Installation can always be interrupted, even without a cancel button.
> Your setup should tolerate that with proper rollback.
>
>
Hi all,
I have an application that will be distributed on CD, primarily, to
extremely non-technical users who very rarely have internet
connections. Some of them are, and I'm not making this up, located in
Outer Mongolia. Others are our salespeople who, at tradeshows, will
not have access to int
No, there are no 64 bit files, I just remake x86 installer to x64, and all
files is x86. So there are must be no x64 Components.
Did anybody test x64 work of light?
On Tue, Jul 14, 2009 at 6:04 PM, Chris Ridd wrote:
>
> On 14 Jul 2009, at 05:29, Igor Lemsky wrote:
>
> > I have x64 Windows XP. I
hi,
Im reedit my code, but i still have this problem,
compiler/linker doesn't add all library to my installer.
I remove Giud ( place *) and remove name section.
Can I view some log from building?
I don't have any errors or warnings
TIA
2009/7/14 Konstantin Vlasenko :
> Please remove Name attri
Use the Orca tool
http://msdn.microsoft.com/en-us/library/aa370557(VS.85).aspx.
It is the swiss army knife for the setup developers. Also find the
information related to msi tables (usaly MSDN helps).
You will find an idea why this happens.
BTW: Send me your wsx-file. I'll check it
2009/7/14 Matt
28 matches
Mail list logo
