I was using a DownloadUrl from Microsoft as a burn package. Today, this url
no longer exists.
Is there an official site Microsoft will maintain or do I need to copy this
file to my server? Can I legally post it on my server?
I notice some use this url:
I include a legacy msi in a burn package that requires framework 2.0.
However, Windows 8 no longer includes 3.5, it is optional.
http://blogs.technet.com/b/askcore/archive/2012/05/14/windows-8-and-net-framework-3-5.aspx
Is there any way to trigger the Windows 8 shim without including the 2.0
I like the button progress bar on installation. Shouldn't it also be used
during repair and uninstall?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/taskbar-button-progress-bar-to-WixStdBA-on-repair-uninstall-tp7578993.html
Sent from the wix-users
Rob Mensching-7 wrote
If the Bundle is author correctly, you should get those extra files
correctly. They are called layout-only Payloads.
Is this something new? I'm using the Official October beta release and
can't find anything about a layout-only payload.
--
View this message in
We have been using /layout delivered in the October beta version. It
functioned fine other than not always using the local copy which I think has
since been fixed.
With all the discussion about /layout, what is the direction you are
planning on taking.
Rob Mensching-7 wrote
As noted above,
I think I understand that standard command line parameters that MSI support
are automatically passed to each package in the bootstrap application. And
it sounds like others can be passed but I need to specifically add it to the
MsiProperty. However, I'm not clear how to do this.
Here is my
Tried that with no luck.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-command-line-parameters-tp7323306p7323422.html
Sent from the wix-users mailing list archive at Nabble.com.
Scott.Langham wrote
Hello,
When an installer (a colleague built it using burn) is installed, the UAC
dialog says that the program is from an unknown publisher.
As far as I can tell, the exe appears to be signed correctly with an
appropriate certificate. A colleague has used burn to
Can someone elaborate on this? If I set a rollback boundary after my
prerequisites, and had parallelcache set, would the prerequisites start
installing if they are already cached but my primary package is not?
--
View this message in context:
Is there a way to set the icon of the standard burn application form, maybe a
WixStdbaIconSourceFile variable?
Or can the form icon use the IconSourceFile icon?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdba-tp7055053p7055053.html
Sent
Is there a list of possible error responses when using the -layout command
with the burn app? I tried digging through the source without much success
and hope someone can point me in the right direction.
--
View this message in context:
I've been using Votive and 3.6 to build an MSI and create a bundle with Burn.
When I first started I did not see anything built into Votive that harvested
an existing project. Heat is supposed to take a Visual Studio project and do
just that but I didn't get results I could use. It was quicker for
Is Wix, Burn and Votive 3.6 compatible with the VS2010 service pack? I don't
want to upgrade to service pack 1 if there is a problem.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Votive-compatible-with-VS2010-SP1-tp6970417p6970417.html
Sent from
My burn application displays a GUID and throws up a UAC prompt at the end of
an upgrade. I haven't checked the logs but I would assume this is when it is
removing the previous version. I'm using version 3.6.2214 and noticed
SFBUG:3429406 which may be related since my burn application is signed. I
19:28, David L. Beckwith wrote:
I know the external files are automatically harvested in the msiPackage
element. Is there a way to get this from heat?
No, they're entirely separate processes.
Or is there an option with dark?
Not that I know of.
--
View this message in context:
http
David L. Beckwith wrote:
Yes, unfortunately that is what the custom action in the msi is doing.
I could have sworn I tried the payloads under the BootstapperApplication
element, but I'll check again.
Rob Mensching-7 wrote:
I'm a little confused. Are you saying the custom action
at that point where I manually created payloads that the legacy
setup needs. It includes an msi that needs 135 other external files. It is
error prone attempting to do this by hand at the least and a chore
regardless.
David L. Beckwith wrote:
David L. Beckwith wrote:
Yes, unfortunately
I've created two payloads in the MsiPackage element and it places them in the
same folder (cache) as the msi. This works as expected.
However, the resulting bootstrapper exe is not placed in the same cache and
thus runs from a different folder. The custom action in the MSI looks for
the two files
Yes, unfortunately that is what the custom action in the msi is doing.
I could have sworn I tried the payloads under the BootstapperApplication
element, but I'll check again.
Rob Mensching-7 wrote:
I'm a little confused. Are you saying the custom action is using the
current working folder
Bob Arnson-6 wrote:
On 26-Oct-11 22:57, David L. Beckwith wrote:
What is even weirder, is /layout pulls them out in the correct folder.
They also show up in the ProgramData\Package Cache\GUID folder just fine.
If Burn's putting them in the same relative place as they were
originally
not. Is there an option for this? I tried to
create a PayLoadGroup with each Payload and then add this PayloadGroupRef
into the PackageGroup with no luck. The Layout option prompts for the
missing files so it thinks they should be included.
Bob Arnson-6 wrote:
On 25-Oct-11 13:51, David L. Beckwith
David L. Beckwith wrote:
OK, I'm now able to create a detached container. How awesome!
Any suggested file extension to use? Is it a cab file?
But I don't have the install working yet. It seems not all loose files
were harvested. Those in sub-directories were caught but those in the same
Bob Arnson-6 wrote:
On 26-Oct-11 12:48, David L. Beckwith wrote:
But I don't have the install working yet. It seems not all loose files
were harvested.
Only those referenced in the .msi would be automatically included. Are
they actually used?
Yes, two critical files are used
Bob Arnson-6 wrote:
On 24-Oct-11 10:10, David L. Beckwith wrote:
I was hoping output from heat payloadgroups and containers would help me
understand how to create such an animal. Where do you suggest I look for
clues on how to take a legacy install and containerize it?
Maybe you could
I was hoping output from heat payloadgroups and containers would help me
understand how to create such an animal. Where do you suggest I look for
clues on how to take a legacy install and containerize it?
Rob Mensching-7 wrote:
Heat has lots of gaps. It's an area for us to invest in WiX v4.
Verifying the signature verifies the hash of the file. It allows you to
change the exact file as long as the signature is still valid. The behavior
you see is by design.
Checking the hash on an unsigned file means it has to be exactly the same
file when burned. Not so for a signed file. This
and doing it right in the first place. However, it seems
the -generate switch is ignored. I've tried -generate payloadgroup
and container but seem to only get components.
What am I doing wrong?
David L. Beckwith
--
All
I have an MSI in a chain but Burn loaded an old local copy with the same
name. From what I understand it should not have loaded this payload
because the hash should not match. I checked the CachePayload burn code
and it looks like it doesn't check the hash if the certificate is
correct. I
28 matches
Mail list logo
