Just for completeness.
OnResolveSource was not the proper way to do what we wanted (Setting the
local source to the started Bundle after reboot). SetLocalSource did the
trick.
--
CenturyLink Cloud: The Leader in Enterprise
Thank you for your reply. That's strange... I will keep an eye on it.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Votive-Drawing-Error-tp7591851p7591891.html
Sent from the wix-users mailing list archive at Nabble.com.
Why can't you just compile the source code beforehand and place the binary in
the installer? It's because of the integration; you are compiling both
together? Usually you can compile your software into an intermediate library
that the user can use and compile with their software. Any change
Hi,
I used a command line tool embedded in my burn package like a prerequisite,
this tool calls pkgmgr.exe in order to enable Windows features.
ExePackage Id=IISRoleOcsSetupServer
DisplayName=Web Server (IIS) and Print roles
Cache=no
Hi,
Yes, it is because of the integration. The compile process needs to be done on
the target machine.
Cheers
Sean.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: 20 January 2014 13:18
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users]
Do you get any issues if you create any issues with other project types? If
you create a C# project and go to the properties, does it display correctly?
--
View this message in context:
You can put the file in the Binary table (maybe encrypted) and stream
it out yourself, decrypting it. Or you can install it (encrypted) but
give the component a null guid so that it is not registered, and can
therefore be removed with a custom action or some other method after
its been used.
For anyone coming across this issue in the future, I have filed a bug report
here http://wixtoolset.org/issues/4282/ .
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Buindle-Major-Upgrade-cause-first-msi-uninstallation-tp7590764p7591906.html
Null/empty component guid components are only installed in major upgrades.
Patches are not typical major upgrades and those components are ignored (just
as with all other maintenance transactions).
As it says: it cannot be removed or repaired. A patch is basically always “a
repair” (after the
What is standalonesimulator.exe’s file id?
Blair
From: Suvrajyoti Panda
Sent: Tuesday, January 14, 2014 11:27 PM
To: General discussion for Windows Installer XML toolset.
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not under
dunno. I always use msbuild from the command line:
“FullPathToMSBuild.exe” /nologo /t:Rebuild “FullPathToSolutionFile”
DevEnv has always been a black box and has never been particularly build-box
friendly.
You’ll have to use DevEnv on solutions containing projects that aren’t
compatible
The only certificate installation bug I found in the old sourceforge site was
this: http://sourceforge.net/p/wix/bugs/1353/ and that one was marked fixed in
2008 (it also describes a different bug with the same error code) and in the
new system is found here: http://wixtoolset.org/issues/1768/.
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014 11:14 PM
To: General discussion for Windows Installer XML toolset.
Thanks David that works.
I have used as below:
Property
Hi Blair,
I build them from the same machine at the same from another location.
Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014
When you use the property remember pattern, all packages that store/retrieve
the property at the same location will “remember” the same value. If you need
the two setups to have different values, you should consider using two
different registry locations for your property remember pattern.
And you don’t intend on installing them on any other machine?
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 9:18 PM
To: General discussion for Windows Installer XML toolset.
Hi Blair,
I build them from the same machine at the same from another location.
I do intend, but for that scenario i am changing the path accordingly,
using %~d0\Installers path.
On 21-01-2014 11:07, Blair Murri wrote:
And you don’t intend on installing them on any other machine?
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 9:18 PM
I got it!
Steps to reproduce in VS2013:
- Go to Tools-Options-Environment and choose Color theme Dark
- restart Visual Studio
- View the Paths property page of a .wixproj
Voila! It looks like the Paths page simply uses a wrong background color!
In the Dark theme _only_ the Paths page is grey
18 matches
Mail list logo
