I happen to find a link on the internet that states:
If you download a .ZIP and unzip it, the individual files will be marked as
the same zone as the .ZIP. Almost every time I have a folder full of
"blocked" files, this is how I got them.
Before unzipping, click the Unblock button on the .ZIP.
Re
Has anyone experience this following error below?
I've tried to unblock the WixBA.project and also added
in
Error 1 Unable to load the metadata for assembly 'WixBA'. This assembly
may
have been downloaded from the web. See
http://go.microsoft.com/fwlink/?LinkId=179545. The foll
Well that didn't take long. I have been able to isolate the offending
Windows Update that breaks my WiX bundle:
Security Update for the Windows Installer Service: August 12, 2014 (
http://support.microsoft.com/kb/2918614)
After installing this update I can no longer update from one bundle to the
I am having the EXACT same issue as described by Vikas, but I have reason
to believe that this breakage is caused by a recent Windows Update released
by Microsoft, because I tested packages that used to upgrade fine from one
version to the next (they are released in production and have been used by
Rob,
Thank You for the insight.
Just curious, does the BA suppress the dialog progress UI?
The only reason I ask is simply after installing software via MSI and then
uninstalling the MSI the uninstall progress bar is visible.
Lino
--
View this message in context:
http://windows-installer-x
My opinion is to not display an internal UI. Then this is a non-issue because
the BA will display progress.
A custom BA can be a little scary at first, but once you take the leap it's
nothing but "pure awesome" on the other side.
-Original Message-
From: Rob Mensching [mailto:r...@fire
If the MSI is already installed a Bundle will not install it again (unless the
BA requests a repair).
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Spud [mailto:
Note: I submitted the Burn engine to the major AV vendors about a year ago so
they could avoid false positives. Submitting your own Bundle to the AV vendors
may help them better recognize Burn as non-malware.
___
FireGiant | Dedicate
Don't use the MSI UI. Pass in a Bundle Variable to the MsiProperty.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: krupeshdhruv [mailto:krupeshdh...@gmail.com]
Se
There is a feature request open about trying to figure out how to do this
correctly.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: linos [mailto:lino...@hotmail
Hello Everyone,
I am creating installer in wix 3.8
I have two msi created (32 and 64 bit each)
I am using standard bootstrapper application to run them depending on
platform.
Problem:
I have one custom action which is invoked in un installation.
It checks the UI level and if it is >=5 then it wi
Thanks Everyone for your help.
I will make my executable signed and check.
Thanks and regards,
KD
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Antivirus-is-blocking-execution-of-standard-bootstrapper-application-tp7596457p7596483.html
Sent from
About a year ago, while using Wix 3.8 RTM and VS2010, building the default
bootstrapper project with minimal changes to define the manufacture and add
a MsiPackage to the chain, resulted in the Bundle.exe being deleted within
seconds of being compiled by Samantec Endpoint Connection. A False-posit
Mr Cooper,
Thank you for your response. It worked as described.
All I needed to do was reference the MsiProperty Name in my MSI package with
[].
So for example, my MsiPackage name is VersionA, then I would reference it in
my MSI where ever in my as [VersionA].
Thanks Again.
Lino
--
View thi
Hi,
I am facing the same issue mentioned above.
Is anyone has update regarding last question asked:
While I was able to access it via a custom BA, I didn't see that there was a
way to access it when using the
"WixStandardBootstrapperApplication.RtfLicense" bootstrapper in the
Bundle.wxs. Is it c
thanks John, I will try that out
steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/create-registry-value-with-product-code-tp7596476p7596479.html
Sent from the wix-users mailing list archive at Nabble.com.
$(var. ---) constructs are static, so all you're getting back is what you put
in, which is the '*' in this place. What you want is the generated product
code, which is stored in the ProductCode property in the Property Table.
You should save [ProductCode] in you Registry element to get the effe
Hi all,
I require to create a registry key with the product code, which I have set
up like so:
in a Variable.wxi file:
in my product.wxs I have:
but after the install runs that registry value shows up as:
"msiexec /x * /q"
if I use:
it shows up as "msiexec /x /q"
What am I doing wrong?
t
Pass them as public properties to the MSI. From one of my bundles:
* * *
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original
How can I reference in my MSI a variable that I'm passing in from my
bootstrapper. For example, I have the following text in my bundle.wxs file:
within Bundle
within MsiPackage
In my MSI where ever I have $(var.msiVersion) I would like to use the
Msiproperty variable baVersion from my BA bundle
Hello,
I have a bootstrapper application (BA) that installs an MSI. Upon
installation, I have DisplayInternalUI="yes", which seems to work by
displaying the msi dialog. Now, when I perform an uninstall, through the
BA, I do not see the progress bar displaying the uninstallation. Can this
be ach
Hi Rob,
Thanks for the help. It works! I have changed the RequestState to None, if
the package not selected for installation.
Is the same concept work for unisntallation? If launch from ARP, I would
like to uninstall only the selected packages and ARP entry don't get remove
untill I will uninstal
Thanks,
It's work great. You are save my lot's time. Thanks a lot.
Mrugesh Patel
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-not-show-installed-prerequisites-LocalDB-MSI-in-Program-and-Features-tp7596466p7596471.html
Sent from the wix-us
Which AV software is doing this?
We're currently not signing, so by the sounds of things may be lucky to have
not come across this.
Knowing which AV has this behaviour would be very handy.
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ant
If I understand your situation correctly, the MsiPackage element in your
chain should have a Visible property. simply set this to "yes".
>From the docs:
Specifies whether the MSI will be displayed in Programs and Features (also
known as Add/Remove Programs). If "yes" is specified the MSI package
i
Thanks for the reply (Schedule major upgrade late and ensure Component Rules
are followed. ) Rob.
I'm not sure I follow.
Hopefully I'm following the component rules as all resources used more than
once are only installed via one MSI in the GAC - lets call it
SharedComponents.msi.
In my (simplifi
26 matches
Mail list logo
