Hi Blair,
This is the original link I was referring to in my message. It talks about a
bug report.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CertificatePath-in-Certificate-element-does-not-work-td6579192.html
I suppose no one bothered to file one. I’d be happy to file the
Hi Phil,
The compile is done at install time--after the file is copied by executing a
dos application.!
Is there any documentation regarding giving the component a null guid, what
exactly does this do or perhaps not do maybe the right question to ask?
Cheers
Sean.
-Original Message-
http://msdn.microsoft.com/library/aa368007.aspx
“ComponentId
A string GUID unique to this component, version, and language.
Note that the letters of these GUIDs must be uppercase. Utilities such as
GUIDGEN can generate GUIDs containing lowercase letters. The lowercase letters
must be changed
Please file a bug with that exact repro.
Thank you,
Blair
From: bwehking
Sent: Monday, January 20, 2014 11:50 PM
To: General discussion for Windows Installer XML toolset.
I got it!
Steps to reproduce in VS2013:
- Go to Tools-Options-Environment and choose Color theme
It appears that no one ever entered one. Today you go to http://wixtoolset.org/
and click on the red “File a bug” link, then enter a new bug. It will require
you to setup an account on that site.
The new bug system doesn’t accept uploaded files (but the entries are in
“Markdown” syntax) and
And how do you intend to communicate that path into the MSI? And how will that
path relate to the source path of the files before they have been added to the
MSI when on other machines those files won’t exist yet?
I’m just trying to understand what your scenario is here to help guide you to a
Not an issue Blair, i appreciate your concern. Attached is the bat
file(in text format) that i am using to create the msi installers. The
machine on which i run this will have the code checked out from svn(this
is my scenario) from where through heat i would harvest the file.
Ultimately i
Done!
http://wixtoolset.org/issues/4286/ http://wixtoolset.org/issues/4286/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Votive-Drawing-Error-tp7591851p7591929.html
Sent from the wix-users mailing list archive at Nabble.com.
Classification: Public
We use TFS as our source repository so I get the setup source first then build
set DevEnv=%DevEnvDir%devenv.exe
echo DevEnv=%DevEnv%
set MSBuild=msbuild.exe
echo MSBuild=%MSBuild%
set TF=%DevEnvDir%TF.exe
echo TF=%TF%
if $%DevEnv%$==$$ echo DevEnv not set
if
Thank you Blair. That worked great. I use Msbiuld in other parts of my build
process, but did not think about trying it to solve this problem. I appreciate
the help.
David S. Echols
Senior Programmer
HA Architects Engineers | www.ha-inc.com
d: (757) 213-6049 p: (757) 222-2010 f: (757)
Instead of MsiNTProductType (the MSI property), the Burn variable NTProductType
should be used. Otherwise, the InstallCondition will evaluate to False.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434
The not ideal qualities of Dism.exe may also apply to running
pkgmgr.exe - it's an external exe that may show UI inappropriately
(silent installs) and not allow graceful error reporting other than
the program run as a custom action failed, also whether it matters
that there is both an x86 and x64
Can you attach the log file?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-with-WIX-BootStrapper-tp7591935p7591941.html
Sent from the wix-users mailing list archive at Nabble.com.
I have a WIX installer built that installs fine on XP machines.
When I go to install on Win 7 machines that have UAC enabled the install gets a
Premature Failure and rolls back.
How do I get the installer to install on these Win 7 machines without disabling
UAC?
It looks like adding this to Package may do the trick:
|InstallPrivileges=elevated|
I'll try it and see.
On 01/21/2014 08:21 PM, Gerry Reno wrote:
I have a WIX installer built that installs fine on XP machines.
When I go to install on Win 7 machines that have UAC enabled the install gets
Hi Blair,
Yeah I was able to sort out the problem, I was using same name for all and
so the problem was occurring. Thank you so much for your help.
Regards
Tony
On Tue, Jan 21, 2014 at 10:52 AM, Blair Murri os...@live.com wrote:
When you use the property remember pattern, all packages that
Hi,
For one of our application after installation, 4 dlls are needed to be
registered using REGASM.exe. Earlier when we were building setups using
visual studio, this was done automatically. In WiX is there a way to do
this during installation or after installation? At least is there any other
praveeds wrote
I am using an WIX BootStrapper inorder to bundle one MSI (for instance
take Notepad++.msi).
When i run the BootStrapper it starts installing the Notepad++.msi but
once the installation is completed it would restart the installation for
the second time. What would be cause of
praveeds wrote
I tried with Windows 7 box and it has the same behavior. Any idea what are
those registry entries?
Yes, they are Run and RunOnce keys to tell Windows to run the installer on
next startup, in case the installer needs the computer to reboot. I'm not
sure whether this is related
19 matches
Mail list logo
