my msi file was originally created under folder ..bin\Release\ along with
the setup file, so I can do the installation using either msi or setup
application.
Then I add a wxl file (from visual studio 2010 using add new wxl file), did
some localization, things work fine except the msi file was crea
Hi Subbiah,
Why not try logging and take a look at the log file?
msiexec /i your.msi /L logfile.txt
Best Regards
Francis
> Date: Thu, 16 Aug 2012 18:15:24 +0530
> From: subbiahtv...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] recurring reboot
>
> Hi all,
>
> After
Even including all the full path of this file, there is only 180 characters.
Actually, I don't think it's a file length issue, because *absolute path
works fine*. The issue *only happens on relative path*.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabb
>>First, the progress bar in the MSI UI doesn't show any progress while it
is installing. It this universally >>the case? Has anyone else seen this?
I'm also having this issue, are there any solutions?
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.68755
Hello,
I was trying to replace some text on the deployment UI (attached screen),
it seems could change that text by adding (to a .wxl file in the project):
{\WixUI_Font_Bigger}Replacement text
here
However, our current deployment project does not have .wxl files, instead
it includes some
Hi,
I have been tasked to develop this (below)for a msi setup program:
I have a setup that has 10 instance transforms embedded in it. Help files are
installed to a common location (this is not duplicated across all the
instances, there is just one copy of the help files). I need to make one
sh
I have one developer who is unable to build a MSI and successfully incorporate
a bootstrapper file. The build output reports the warning MSB3165: The value of
the 'Hash' attribute in '<< bootstrapper product name>>' does not match that of
the file '<>'.
We have verified that the "Hash" attribut
I found one workaround. Putting the RegistryKey inside of another RegistryKey
that does have a value marked as the keypath. That satisfied the ICE38 rule
for that component.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-empty-registry-ke
Hi,
I have a rather straight forward wxs that installs an executable and its
dependency into ProgramFilesFolder/[Vendor]. Additionally, it creates two
shortcuts: one to application itself, another to uninstall the application
in ProgramMenuFolder/Vendor/Product.
Thanks, Palbinder
That lead me to the problem. All of the settings for my wixproj were under the
Release configuration but MSBUILD was using the Debug configuration because I
hadn't told it to build Release. I'm good to go.
Though since I did figure out how to specify preprocessor variables in
Hi, Yes I finally found an answer, im now using this:
It seems to work ok(I think) :)
Thanks
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 16 August 2012 14:19
To: General discussion for Windows Installer XML toolset.
S
That looks ok but you don't normally reference WOW6432Node as that redirection
happens automatically if your msi is 32bit.
Neil
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 16 August 2012 2:08 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-user
Can anyone tell me if I have done anything wrong here, it does not seem to
be working. And also do I have to call a custom action to run this search?
Whats my best way for testing it?
Kind Regards,
Natalie Carr
--
Hi all,
After installing/uninstalling a msi which is built via Wix v3.6, sometimes
the system keeps rebooting and unable to recover. What is the best way to
see that the installer doesn't corrupt the registries or possible way to
debug this?
Thanks,
G.Subbiah
---
If you add the length of the current directory path (whatever that is) to 155
does it go beyond 260 characters ?
-Original Message-
From: shengyixing [mailto:shengyix...@hotmail.com]
Sent: 16 August 2012 11:50
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Relative Path caus
I'm wondering, how to include a configuration-dependent project output in
WiX Setup Project? For example, let's look at Visual Studio solution with
one .NET application and one Wix Setup Project.
I've added a reference to .NET app in Setup project and created component
in setup source:
Newly found,
"AmberCore.IgmapPlus.PlugIns.ImportExport.ImportE.dll" can be found by
Light.
Altogether,
"AmberCore.IgmapPlus.PlugIns.ImportExport.ImportES.dll" can't.
..\..\..\..\..\..\..\..\..\external\\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportE.dll
is 155 characters.
--
Vie
Try using the "Suppress specific warnings" field in the individual wixproj
files where appropriate.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions L
Currently, I have a wix script, contains a component with file source
attribute value:
..\..\..\..\..\..\..\..\..\external\Test\x64\Release\FileOperationProviders\Test\Test\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportESRI.dll
My script is under such a folder:
C:\Perforce\PSEBP4\PlatformSDK\br
Looks like someone else already had the same idea ->
http://sourceforge.net/tracker/?func=detail&aid=3535563&group_id=105970&atid=642717
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
> From: edwin.cas...@fiserv.com
> Date: Wed, 15 Aug 2012 12:12:44 -0400
>
> I think it is important to ask these questions if only to determine the
> intentions of the licensors and encourage that the license be more explicit
> about its intentions. These things should not be determined in cour
21 matches
Mail list logo
