You can do a /layout to get the contents of the bundle, then you would need to
do an admin install with the msi.
Don't know if there is a /admin on the bundle, you could make one if not that
calls each msi in turn with admin parameters.
-Original Message-
From: Bruce Cran [mailto:br...@
Hi,
I have a main installer which is around 200 mb, created a Patch which is
around 1 mb
When running the patch it takes around 8 minutes of out which
WriteRegistryValues is taking 5 minutes
Is there any way possible to reduce the time taken by WriteRegistryValues?
Thanks and Regards
Ravi Shank
MSI package always tries to reboot even if I set REBOOT=ReallySuppress
flag.
What else could be wrong with my MSI ?
My app is really nothing complex for reboot. I wan't to avoid it all cost.
I'm using a custom burn bootstrapper. The MSI package always sends a
restart request to the burn bootstrapp
Sorry for this repost... but does anyone have a solution for this?
I'm close to write my own CA...
Cheers,
Davide
2014-04-04 8:22 GMT+02:00 Davide :
> Hi all,
>
> I spent a whole day with this problem now and would appreciate any help!
>
> To make it really easy I picked a sample COM+ Applicat
Is there anything here that helps
http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/com-
applications - I wrote it a long time ago and am not sure if it is still
valid but it might be a good starting point.
Neil
>Sorry for this repost... but does anyone have a solution for t
Hello!
Are there any possibilities to avoid creating system restore point before
running 3rd party exepackage via WiX bootstrapper?
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Con
You can set the Chain/@DisableSystemRestore attribute to "yes".
-Original Message-
From: Valentine Vinogradov [mailto:wallenw...@gmail.com]
Sent: 10 April 2014 14:09
To: General discussion about the WiX toolset.
Subject: [WiX-users] Avoid creating system restore point
Hello!
Are there an
Wow, sorry for my question then, haven't found it if the documentation
2014-04-10 16:29 GMT+03:00 Neil Sleightholm :
> You can set the Chain/@DisableSystemRestore attribute to "yes".
>
> -Original Message-
> From: Valentine Vinogradov [mailto:wallenw...@gmail.com]
> Sent: 10 April 2014 1
Hi Neil,
thanks for your reply.
All in all my code is from your tutorial and it works fine for native
assemblys... but not for COM+ assemblys.
Any ideas why? Something wrong in my code? Does anyone have a working
example?
Regards,
Davide
2014-04-10 14:44 GMT+02:00 Neil Sleightholm :
> Is th
Is your code .NET 4.0? If so I was able to reproduce the problem, it appears
that the COM+ CA doesn't work with .NET 4.0 assemblies. Can you use .NET 3.5?
Have you tried manually installing a .NET 4.0 assembly into COM+?
Neil
-Original Message-
From: Davide [mailto:spamform...@gmail.com
On 4/10/2014 3:13 AM, David Watson wrote:
> You can do a /layout to get the contents of the bundle, then you would need
> to do an admin install with the msi.
>
> Don't know if there is a /admin on the bundle, you could make one if not that
> calls each msi in turn with admin parameters.
Unfortu
Get a verbose log and look for "in use" messages or other stuff that
refers to a reboot - you'll need to see what's going on. Keep in mind
that suppressing the reboot doesn't automatically get rid of all the
reasons a reboot might be necessary, and the MSI is returning the
result (probably the 3010
These may Help:
http://stackoverflow.com/questions/17940364/wix-how-to-delete-non-empty-folder
and:
http://wixtoolset.org/documentation/manual/v3/xsd/util/removefolderex.html
Carter
Quoting "Harold Wood (H10 Capital)" :
> Within the createfolder item I have the following element
> , and it
Yes, you need to define custom action "Execute". Here is what works for me:
(1)define custom action that executes RegAsm.exe; example:
(2)schedule the action (1) in your , something like
this:
Few notes:
(a)the example uses RegAsm from framework v4 but you can modify to
Thanks for the info. I have been spinning wheels on this issue also.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Environment-variable-ProjectPath-is-expanded-possible-to-turn-off-tp7587463p7594051.html
Sent from the wix-users mailing list arch
Thanks!
-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net]
Sent: Thursday, April 10, 2014 11:41 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] not removing files after install
These may Help:
http://stackoverflow.com/questions/17940364/wix-how-to-delet
I believe RegAsm registers for COM not COM+ I believe. Also, I wouldn't
recommend registering COM that way, it is better to use the built-in COM
elements (Class, ProgId etc.) or write the registry keys directly.
-Original Message-
From: Marek Mielcarek [mailto:mmielca...@actuate.com]
Se
Use the built in registry elements, they are far more robust than RegAsm. As
long as the component rules are followed, you can have two applications
installing this same COM object and the registry keys will be properly
reference counted. In your existing install, if you installed two instance
I have a wixlib project that now needs to install files that are within a
merge module. I thought that just adding the Merge Id to the wixlib fragment
DirectoryRef and the MergeRef Id to the fragment Feature Id that it would
just work, but it did not.
The wixlib built without errors and during the
That should work. Best guess: Check that the Fragment(s) with the MergeXxx
elements are referenced.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: TimM [mailto:ti
Hi, Is there anyway burn can handle installing/uninstalling exe/msi packages
which are not part of the chain. In other words these msi/exe packages will be
added later at runtime.
Currently, I have bunch of MSIs I run part of my burn chain, but the
requirement is that burn should be able to pic
I have a bundle with a number of msi pacakges, one of which has a feature
which is advertised. Recently (probably because I changed something in the
authoring) I am noticing a behavior where if I install the bundle, then
after that completes successfully, click on the advertised shortcut, then
the
How Can I change RuntimeVersion = 0 into a version check as in
RuntimeVersion <= x.x.x.x when <= is not allowed??
http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_64bit_13_0_9.zip";
InstallCondition="RuntimeVersion = 0" />
I think I have used something like this in the past?
InstallCondition="RuntimeVersion <=vx.x.x.x"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Testing-for-Version-Numbers-tp7594059p7594060.html
Sent from the wix-users mailing list archive at Na
In the prior post I meant to have the entity display:
InstallCondition="RuntimeVersion <=vx.x.x.x"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Testing-for-Version-Numbers-tp7594059p7594061.html
Sent from the wix-users mailing list archive at
I'm aiming for RuntimeVersion <=13.0.8, I'll give this a try tomorrow...
Carter
On Thursday, April 10, 2014 04:49:47 PM Phill Hogland wrote:
>In the prior post I meant to have the entity display:
>InstallCondition="RuntimeVersion <=vx.x.x.x"
>
>
>
>--
>View this message in context:
>http://w
No. Burn provides a very strong security statement for the contained packages.
If you add packages, you'll want to update the bundle to include them in the
chain or include the additional packages in a related bundle and launch them in
succession.
___
Is your MSI per-machine?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Thursday, April 10, 2014 4:21 PM
To: wix-
28 matches
Mail list logo
