Hi,
when creating a new version of a burn bootstrapper (using wix 3.9), I noticed
that the
util:FileSearch did not work as I thought it would.
I tried to find a textfile in an application-specific c:\programdata sub-folder:
Unfortunately this did not work out: The burn logfile always said:
Hi everyone,
I was thinking about looking into an old topic where one
could specify a RebootBoundary somewhere in the chain
and make sure that all prior MSIs requests for reboot
will be executed at that point:
http://wixtoolset.org/issues/4026
Anyone got any ideas, thoughts etc. about this topic
Hi Bob,
like discussed last Thursday, I have added additional changes like requested in
pull-request
https://github.com/wixtoolset/wix3/pull/164
for my pull-request at:
https://github.com/wixtoolset/wix3/pull/162
Would be nice if you could integrate them prior to building the first 3.10 :-)
Bes
Hi everyone,
as I have not seen any invitation over the mailing-list yet, I was wondering
if there will be an online-meeting today...
Tobias
--
___
WiX-devs mailing list
WiX-dev
Hi everyone,
I was wondering if that would be something that we could put into 3.10?
I also get quite a few complaints that the success-page of uninstall is
a bit puzzling...
Best regards,
Tobias
Von: Hoover, Jacob [jacob.hoo...@greenheck.com]
Gesendet: Donnerst
I have created a new bug-entry about the issue I have mentioned in the
wix-users mailinglist:
http://wixtoolset.org/issues/4571/http://wixtoolset.org/issues/4571/
I have also tested a quick-fix for this, and I would like to discuss if this is
the correct course
of action... so any comments or f
Hi everyone,
As I needed the ability to get the state of a checkbox on the Modify-Page
prior to uninstalling an MSI, I looked through the mailing-list and found
several questions concerning this topic.
As I did not find any open feature-requests for this topic, I opened
one myself:
http://wixtool
ystem.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: Thursday, October 23, 2014 2:32 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Recompiling WixBalExtension.dll for test-usa
“Tools\WixRelease.relproj” to get the binaries.zip files
and use that in your private build process.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de
Hi again everyone,
some of the installers I have generated have come under scrutiny lately as
they leave large amounts of logfiles (having an agile development process,
the number of new versions is rather large ;-)
So the question came up if there was any way to disable this logging
(yes I know
Hi again,
or to widen the scope a little: If I have created an (informal/internal)
release-build, is there some kind
of batch-file to copy all necessary files into my installer-directory for
testing?
Or if there is some kind of document describing this I'd be really grateful...
Best regards,
Hi everyone,
I have just installed RC4 and pulled the current source and I was trying to
test a change
of the WixBalExtension. I could compile it successfully, but when I replace
the installed
version of the dll with the newly compiled one, I get CNDL0144 that it cannot
find the
dll during my
Cool thing - and thanks to you & Bob for doing this on your holiday :-)
Now that 3.8 is settled I was wondering how I should proceed with the stuff
that I had prepared
as pull-requests in my 3.8 branch - any way that I can "switch" my private
3.8 branch into 3.9 ...
I'm still not so sure about
iX toolset developer mailing list
Betreff: Re: [WiX-devs] WX Online Triage Meeting #11.5
No triage today. WiX v3.8 Release Day. US holiday.
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: Thursday, November 28, 2013 7:59 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs]
Is there a link to today's triage somewhere yet?
Von: Robert J. van der Boon [rjvdb...@gmail.com]
Gesendet: Dienstag, 26. November 2013 10:55
Bis: WiX toolset developer mailing list
Betreff: Re: [WiX-devs] WX Online Triage Meeting #11.5
I'll probably not be able t
Hi Rob & Bob,
assignment agreement is in place now...
_
Von: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Gesendet: Dienstag, 12. November 2013 11:17
An: WiX toolset developer mailing list
Betreff: Re: [WiX-devs] Issue & possible solution: Burn Startup-Screen is shown
t
Hi Blair,
thanks for the info. Actually I could not add my new commits to the
pull-request, I always
got an error-message from codeplex.
So I cancelled the old and issued a new pull-request.
My last change was to allow for conditional compile of the fix for the Windows
XP driver-install-issue
You are right of course.
Thanks for your pull-comments, I already incorporated your suggestions and
pushed them to my fork - do you
guys need a new pull-request for this, or does the old one suffice?
One question:
After I compiled the release-version for testing (non-official release as I do
We were talking about it the other day, but due to the other topics it got lost
somewhere in between...
I'd be grateful if it made 3.8 as this is currently the only showstopper that
keeps me from using burn
for my new installers. And as it will fix the same issue for (at least) the
other two g
Hi everyone,
I've changed my fix to use OsGetVersion, created a fork on Codeplex and issued
a pull-request.
Now "just" the topic of the Assignment Agreement remains open :-)
Best regards,
Tobias
Von: Rob Mensching [r...@robmensching.com]
Gesendet: Sonntag, 10. N
-devs] Issue & possible solution: Burn Startup-Screen is shown
twice (on Windows XP) if bootstrapper contains driver-installation
On 10-Nov-13 17:15, Tobias Erichsen wrote:
a.) an administrative one: I have not signed the assignment stuff yet which I
want to do
We need a signed assignment agree
vote you put together a pull request for 3.8 soon.
Blair
Tobias Erichsen wrote:
Hi Bob,
would it possible for you to incorporate my proposed changes in the next RC of
3.8?
I think the changes are not that "severe" and will fix the problem with using
driver-installs
in burn on Wind
Hi Bob,
would it possible for you to incorporate my proposed changes in the next RC of
3.8?
I think the changes are not that "severe" and will fix the problem with using
driver-installs
in burn on Windows XP. For all other OS-versions nothing will change...
Best regards,
Tobias
_
Von:
un once key
Clear the sync object name from the session
Release the sync object and exit
I'd strongly advise against adding any more options to the command line, as
we have had issues already today w/ the command line and options exceeding
MAX_PATH.
From: Tobias Er
Hi everyone,
after some twiddling I got the 3.8 branch to compile on my machine and
recompiled burn.exe to test the "Run instead RunOnce" approach.
Seems to work like a charm...
There were only a few changes I needed to make in file registration.cpp:
Changed consts to refer to correct registry
...now again with shortened body to not break the size-limit of the
mailing-list:
Even if the other solution with the named object sounds like the most elegant
version, I'd
would probably go with the simplest (k.i.s.s), as the room for breakage is the
least
(and not being totally unselfish, I
But what about my proposal to "refresh" this key once before each package being
installed,
so it will always be there before the next msi in the chain is being
installed...
So if the bootstrapper happend to be fired prematurely (and thus the RunOnce
key being deleted),
it is there for the next
ce: 913-341-3434 x791011
jocoo...@jackhenry.com<mailto:jocoo...@jackhenry.com>
www.jackhenry.com<http://www.jackhenry.com>
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: Friday, November 8, 2013 3:18 AM
To: wix-devs@lists.sourceforge.net
Subject: [WiX-devs] Issue & pos
key
Clear the sync object name from the session
Release the sync object and exit
I’d strongly advise against adding any more options to the command line, as we
have had issues already today w/ the command line and options exceeding
MAX_PATH.
From: Tobias Erichsen [mailto:i...@tobias-erichs
Problem:
When burn is used to install one or more MSI-packages (very probably also
exe-packages) on Windows XP
and one of the packages contains a driver install, the burn-bootstrapper is
started a second time
during the installation-chain, showing the startup-screen once more erroneously
30 matches
Mail list logo
