On 03-Nov-11 10:35, David L. Beckwith wrote:
> "error LGHT0103: The system cannot find the file ..."
>
> I suspect this file name is too long (72 characters). However, when this
That's not a problem as long as the full path fits in MAXPATH characters.
--
sig://boB
http://joyofsetup.com/
--
I made a lot of payloads but now seem to have another problem. I try to
assign the following SourceFile to a Payload element:
x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700.cat
However, when I attempt to build it I get the following:
"error LGHT0103: The system cannot find t
On 02-Nov-11 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.
--
sig://boB
http://joyofsetup
OK, I'm back where I started. Basically, heat does not create a PayloadGroup
with "-generate". If that option was available this thread would probably
not be here. The help says:
"Specify what elements to generate, one of: components, container,
payloadgroup, layout (default is components)."
Howe
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
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
I'm a little confused. Are you saying the custom action is using the
current working folder to find files? If so, that won't work out most of
the time or rather it will work in very limited situations.
If you want Payloads cached with the bootstrapper, you can add additional
Payload elements under
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
Add Payload elements under the MsiPackage element to manually add files
that are not described in the MSI file itself.
On Mon, Oct 31, 2011 at 6:09 AM, David L. Beckwith wrote:
>
> Bob Arnson-6 wrote:
> >
> > On 26-Oct-11 22:57, David L. Beckwith wrote:
> >> What is even weirder, is /layout pull
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
> orig
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, there must be something pe
Bob Arnson-6 wrote:
>
> On 25-Oct-11 13:51, David L. Beckwith wrote:
>> Basically, I have a legacy install program that I would like chained.
>> Specifically, it is Microsoft's Point of Service for dotNet. There is
>> no "ClickOnce" install, instead it is delivered as a self extracting
>> zip.
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 ar
On 26-Oct-11 12:48, David L. Beckwith wrote:
> Any suggested file extension to use? Is it a cab file?
It is, though that's an implementation detail.
> 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 automatical
On 26-Oct-11 16:15, David L. Beckwith wrote:
> Once a detached container is created, how do you reference it? I added
> a ContainerRef in the in the bundle, but how do I get the payload into
> the chain from the container? Do I create the container with one
> project and suck it in as a Payload
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
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
directory as the msi were not. I
On 25-Oct-11 13:51, David L. Beckwith wrote:
> Basically, I have a legacy install program that I would like chained.
> Specifically, it is Microsoft's Point of Service for dotNet. There is
> no "ClickOnce" install, instead it is delivered as a self extracting
> zip. It has a setup bootstapper wi
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
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 explain what "containeriz
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
Heat has lots of gaps. It's an area for us to invest in WiX v4.
On Wed, Oct 19, 2011 at 10:08 AM, David L. Beckwith <
beckw...@interaccess.com> wrote:
> I'm using Burn and I got to say I love it!!!
>
> However, it makes me want more...
>
> I'm trying to get a legacy installation package chained a
I'm using Burn and I got to say I love it!!!
However, it makes me want more...
I'm trying to get a legacy installation package chained and am
struggling. I would like to containerize the legacy install so my
bootstrapper is small and incremental. I've tried heat in the hopes of
it saving time
23 matches
Mail list logo
