You could open a feature request, if one isn't open already.
On Mon, Jun 10, 2013 at 10:50 PM, Roopa Prabhu wrote:
> Is there a way to track this or keep myself updated about it?
>
>
> On Mon, Jun 10, 2013 at 11:24 AM, Rob Mensching >wrote:
>
> > It could be if someone implemented it.
> >
> >
Is there a way to track this or keep myself updated about it?
On Mon, Jun 10, 2013 at 11:24 AM, Rob Mensching wrote:
> It could be if someone implemented it.
>
>
> On Sun, Jun 9, 2013 at 10:12 PM, Roopa Prabhu
> wrote:
>
> > Hi Rob,
> >
> > Will this be supported in the next release?
> > We pla
It could be if someone implemented it.
On Sun, Jun 9, 2013 at 10:12 PM, Roopa Prabhu wrote:
> Hi Rob,
>
> Will this be supported in the next release?
> We plan to defer just the rollback part (and maybe use some clean up
> scripts for now) and go ahead with WiX, if the support for this feature
Hi Rob,
Will this be supported in the next release?
We plan to defer just the rollback part (and maybe use some clean up
scripts for now) and go ahead with WiX, if the support for this feature is
not too far off.
Once again, thanks a lot for the clarifications.
On Sun, Jun 9, 2013 at 11:23 AM
Looks like the same batch file is used multiple times. That just isn't
supported yet.
On Sat, Jun 8, 2013 at 10:07 PM, Roopa Prabhu wrote:
> Hi Rob,
> Thanks for th reply. Iwould need to use the same exe (with different
> parameters) in most of my installation steps in the chain, so would like
Hi Rob,
Thanks for th reply. Iwould need to use the same exe (with different
parameters) in most of my installation steps in the chain, so would like to
know which release this is planned for.
I've now modified my sample application such that different batch files are
used in the EXePackages. Howev
Ahh, I see. You are scheduling the same executable (in this case a batch
file) multiple times in a chain. That is not supported today. As long as
the executables are different the correct behavior will happen. In this
case, you can simply change the contents of the batch file (add a unique
comment
Hi Rob,
I've pasted below the log file of a sample application I've created to
simulate this issue:
[2DCC:2394][2013-06-07T15:57:20]: Burn v3.6.3303.0, Windows v6.1 (Build
7601: Service Pack 1), path:
D:\TestProjects\TestApplication\TestApplication\TestBootstrapper\bin\Debug\TestBootstrapper.exe,
Attachments don't work well for mailing lists. Can you just provide the log
contents or if too big, put the log file on a file sharing service (like
SkyDrive) to see it?
On Wed, Jun 5, 2013 at 2:28 AM, Roopa Prabhu wrote:
> Attached a sample log file four your reference.
> Realized that the dir
Attached a sample log file four your reference.
Realized that the directory created in C:\ProgramData\package Cache which
holds the Execpackage gets deleted the moment I set Result.cancel to
trigger rollback.
But Im not able to figure out why.
On Mon, Jun 3, 2013 at 12:13 PM, wix user wrote:
>
Attached a sample log file four your reference.
Realized that the directory created in C:\ProgramData\package Cache which
holds the Execpackage gets deleted the moment I set Result.cancel to
trigger rollback.
On Mon, Jun 3, 2013 at 12:13 PM, wix user wrote:
> On comparing with the log file gene
On comparing with the log file generated when the bootstrapper used to
rollback properly, I discovered that "Detected package: cached: None" is
being logged now as against "cached: Complete" in the working copy. I don't
know why this happens though.
--
View this message in context:
http://wind
Hi Rob,
Attaching the log file for your reference. I have forced a cancellation in
one of the steps, in order to trigger rollback. Could you help me figure
out what might have gone wrong?
On Sat, Jun 1, 2013 at 8:53 PM, Rob Mensching wrote:
> That error means the executable was removed. More d
That error means the executable was removed. More details from log file
probably needed.
On Sat, Jun 1, 2013 at 5:59 AM, wix user wrote:
> Hello,
> The Execpackages chained in my bootstrapper fail to rollback. The log file
> says:
> Error 0x80070003: Failed to CreateProcess...when it starts app
14 matches
Mail list logo
