Hello everyone.
Recently I have faced some very weird issue. Not sure if it is some kind of
defect or just my lack of knowledge (which is most probably the case). Here
it is:
I have naked installer with one single component which contains:
RegistryValue Root=HKLM Key=Software\MegaProduct
-The Registry table uses # as the prefix to say you want an integer number,
-and your string is not a number.
-http://msdn.microsoft.com/en-us/library/windows/desktop/aa371168(v=vs.85).as
px
-The docs say two # characters should be used, the first will be ignored and
-the rest treated as the
For clean installation it really doesn't matter if you have new GUIDs for
each build.
As you said, patching ability will be lost. In terms of patch new GUIDs are
classified as new Components to be installed instead of old ones and patch
does not support component uninstallation.
About upgrade:
Hey, there.
I have a tricky situation. In a new product version we decided to mark one
config file as permanent and neverOverwrite. Also we have
RemoveExistingProducts scheduled after InstallInitialize to support upgrade
from very old versions, where components' guids were differ.
The problem is
Burn engine does not help with that today. Your BA can do it.
How? ^^ I don't see any API in BA to extract data about size from packages in
bundle.
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without
Hello.
I have a question: my BA shows feature selection screen, where user can
choose what features of what packages he wants to install, and I wonder is
there any mechanism in BA that I can use to validate if there is enough disk
space for installation? For simple msi launch there are
If the user renames the executable, then the default prompt for the
executable will be incorrect but he or she can still browse to it with the
old name.
Thanks for pointing me to the right direction). For those who might have
problems with source prompt in BA here is solution:
1) Subscribe on
Hello.
Recently we have some problem with bundle maintaining. Here is use case:
1. Customer gets cd-layout and renames bundle from OldName to NewName.
2. Then he installs some 2 products from bundle.
3. Then he deletes one and tries to install it again.
Boom! Bundle failed
Very mysterious. The next build of the WiX toolset (Monday) will have even
more logging around restart. Can you retry your scenarios with that and
share the log file to diagnose further?
Wix 3.6.2719
OS 2003 SP2 x86, 2008 SP2 x86:
Apply complete, result: 0x0, restart: Required, ba
Hello.
I spend a lot of time in attempt to make my C# BA to restart computer after
installation, but without any success. Native
'WixStandardBootstrapperApplication.RtfLicense' seems to work fine, and I
didn't find in Wix sources any reasons why it doesn't work with my BA. I'm
sure I missed
Good day (I hope!).
I think we found some workaround for updating old bundle, but now we have
another problem with patch implementing via RelatedBundle element. I did as
you said:
Added RelatedBundle Id={GUID} Action=Detect/ to main bundle, and
RelatedBundle Id={GUID} Action=Patch/ to patch
I double checked everything again...
1. You were right ) it does show up in ARP Updates
2. You were right ) There is also the same key in CurrentUser
3. I was wrong ) It was some kind of resource conflict: new file in
patched package had the same component name as another file
Hey there.
Thx for your reply. I really looked forward to). I read on Hearth's blog
about Patching and Add-ons, and tried some. It does work as described). So
thx for that to! One thing I noticed is that Patch bundle is not displayed
in ARP, so there are no normal ways to delete it. Is it by
Hey again.
I know I'm probably the most annoying person, but we have a problem with
released bundle here and we are out of options how to update/patch it
properly. I think I understood how BA should handle detected patches, but it
has been already released.
Please tell me is there any possibility
to previous case.
So could you, guys (Burn creators), describe how do you see the Bundle
Patching scenario?
--
On 25-Jan-12 04:15, Vadym Verba wrote:
Here is usecase: I have old v1.0 bundle installed and new patch bundle
with
patches only (totally new bundle with new
; charset=ISO-8859-1; format=flowed
On 24-Jan-12 10:02, Vadym Verba wrote:
I have a small but a very vital question: how to patch bundle?
Build a new bundle that contains the patches, either by themselves or
with the original packages.
--
sig://boB
http://joyofsetup.com/
/pre
BR style
Hello.
I have a small but a very vital question: how to patch bundle? I mean, let
say I have some bundle of 1.0 version with few products inside of 1.0 version
as well. If I just install patches for products themselves they will be of
1.1 version and if I launch bundle it will detect downgrade,
Sorry for repeating, but does anyone have any clues?
-Original Message-
From: Vadym Verba
Sent: Friday, November 11, 2011 11:37
To: 'wix-users@lists.sourceforge.net'
Subject: Burn: disk space usage calculation
Hello.
I have a bundle with several packages of .msi and .exe types, plus
Hello.
I have a bundle with several packages of .msi and .exe types, plus additional
.exes to install some Windows roles. I also know all their features and can
gather information from user which one should be installed. So now I have a
problem to calculate how much space installation will take.
Hey there.
I created custom wpf window that displays messages for my BA. It is shown as
modal using ShowDialog() method. It does block BA thread, but not Engine
thread when pop-ups during, for instance, applying, so if user decides to
cancel installation he will see pop-up windows, but also
Hello.
Recently I ran against the same problem to launch my bundle exe elevated from
the beginning. I saw your discussion with some tips what to do, but even more
issues appeared.
1)You can embed a custom manifest to a pre-built executable using the
MT.exe tool.
mt.exe -manifest
Now this defect is reproducible on all our tester machines.
The weirdest thing it that simple verification of any file, signed with
company certificate, on the problem computer repels defect ^^ (signtool.exe
verify /pa anySignedFile.exe). I added comment to the defect
the computer clock on the correct date in 2011. After
you install this item, you may have to restart your computer.
More information: http://support.microsoft.com/kb/2570791
Makes defect reproducible again.
From: Vadym Verba
Sent: Thursday, August 18, 2011 10:46
To: 'wix-users
-8
Are you signing with a certficiate that is from a trusted root?
On Tue, Aug 16, 2011 at 7:51 AM, Vadym Verba vve...@sdl.com wrote:
Had same problem with any signed msi. In my case defect reproduced ONLY on
2008 SP2 (x32 and x64). Tested on 2003 and 2008 R2 - worked fine
Had same problem with any signed msi. In my case defect reproduced ONLY on
2008 SP2 (x32 and x64). Tested on 2003 and 2008 R2 - worked fine.
Workaround was found accidently: import certificate of publisher, the msi was
sign which's key.
Import certificate:
1) go to file (msi in my case) property
Hey there.
I have some service declarations in my wix project like this:
Component Id=service_component_id Guid=*
File Id=service.exe KeyPath=yes Source=$(var.Binaries)\service.exe
ServiceInstall Id=service_id Name=service_name DisplayName=!(loc.
service_displayname) Start=auto
Hey, Alexander.
Try to use DetectRelatedMsiPackage. It detects installed products based on
Upgrade Code, but not on Product Code.
Best regards,
Vadym
--
Date: Mon, 4 Jul 2011 10:52:50 +0200
From: Alexander Kriv?cs Schr?der
On this machine, both Headline.Agent and Headline.Player are installed.
However, only the features (and consequently package) for Headline.Player get
detected as present. What decides whether or not a package is detected?
Hey, Alexander.
I had the similar issue. Apparently Burn engine does
On this machine, both Headline.Agent and Headline.Player are installed.
However, only the features (and consequently package) for Headline.Player get
detected as present. What decides whether or not a package is detected?
Hey, Alexander.
I had the similar issue. Apparently Burn engine does
Check the log; as long as MSI returns 3010, Burn will indicate to the BA
that a reboot is required at the end of the chain.
Finally I figured out how it works. ApplyCompleted event has data e.Restart
that indicates if restart is required and Shutdown event allows actual
restart to be scheduled
Hello.
When web site is installed by installer and it crashes later, the rollback
doesn't delete created web site at all. Logs show that there are no any
Rollback CAs for ConfirugeIIs, just StartMetabaseTransaction,
RollbackMetabaseTransaction and CommitMetabaseTransaction inside one
Hello.
I have a problem with pending machine reboot after bundle applying completed.
I have one msi package with ScheduleReboot After='InstallFinalize' /, but
Burn always install package with argument in command line REBOOT=
ReallySuppress and the one before last line in log file is Apply
Hello.
I wonder if there any possibility to declare IIS6, WindowsRoles, MSDTC
installation inside Bundle chain? They use Windows executables from System32
folder, so theoretically it should not be embedded in a container
(Compressed=no):
ExePackage
Id='MSDTC_Id'
Hello.
I want to gather user password using BA and pass it to msi package, so I
create Bundle variable and use it in MsiPackage:
Variable Name=my_password Value=blablabla Type=string/
MsiPackage Id='my' SourceFile=my.msi Cache=no Vital=yes
MsiProperty Name=MY_PASSWORD
Hello.
I have several questions about detecting mechanism in Burn.
1) DetectPackageCompleteEventArgs contains PackageId. Where could I
use this information? Could I somehow get access to .msi itself, described in
Chain with detected PackageId?
2) DetectMsiFeatureEventArgs contains
Hey, Simon.
I had the same problems when first try to write BA on managed code. Rob
Mensching suggested me to see sources of Wix 3.6 installer itself.
wix36-sources\src\Setup\Bundle - location of Wix bootstrapper project
wix36-sources\src\Setup\UX - location of BoostrapperApplication project. It
Actually Bob Arnson was right.
I have the following code works:
1) In Bundle.wxs:
Variable Name=db_name Value=old_db_name/
Chain
MsiPackage Id=SomeMsiId SourceFile=some.msi
MsiProperty Name=DB_NAME Value=db_name/
/MsiPackage
/Chain
2) In BA managed code:
Hello.
I want to write Bootstrapper Application that gathers information about
DataBase, COM+ user etc. so I need to pass this data to appropriate package
(.msi) when it actually executes. I could find MsiProperty child node
nested into MsiPackage which allows pass data and it couldn't be
Hello.
There is an example of declaring BootstrapperApplicationCreate method in
Documentation:
extern C HRESULT WINAPI BootstrapperApplicationCreate(
__in IBootstrapperEngine* pEngine,
__in const BOOTSTRAPPER_COMMAND* pCommand,
__out IBootstrapperApplication** ppApplication
)
39 matches
Mail list logo
