Hi,
One user gets the errors below when trying to build an installer. The same
scripts work fine for other users. The link in the error message does not
work, but I have searched quite a bit for an explanation or solution (other
than disable validations). So far all references talk about
Hi,
I would like to install a driver via a provided setup.exe with burn. It
seems like .cat, .inf and .sys files are not properly handled. I guess
the Error 0x8007002 is the problem but I'm not sure. Tried to debug, but
could only find that something happens when burn tries to elevate while
Hi,
I don't need to modfiy MsiPackage/@DownloadUrl at runtime.
I would like to modify the downloaded MSI resides location.
In Default,downloaded MSI was stored in %programdata%\Package Cache
location. How to set the customized path for downloading MSI?
Please share any idea on this.
Regards,
Dear all,
I upgraded our project from WiX 3.7 to the latest 3.9 version.
I do have a problem however.
Although the msi is created correctly I do get the installation failing with
the following error in the log:
Error 1723. There is a problem with this Windows Installer package. A DLL
required
Yes, you could do that. Or you could put them in wixlibs and link those in.
All of my custom actions live in two wixlibs.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext:
Yes, but something in that Fragment needs to be referenced back in the
Product (or Bundle in the case of a bootstrapper).
If you have the CustomAction elements i separate Fragments (with the related
XxxxSequence elements) then you could group the CustomActionRef(s) in a
Fragment (or Fragments)
I install the CP210x driver. The approach I take is to create a msi package
and use WixDifxAppExtension. I use a single project to build both x86 and
x64 packages. This is one example (although I would revise several details,
like using InstallerPlatform):
Phill, all,
thanks for your immediate and indepth answer!
I also tried using DifxApp and was even successfull on x64 Plattform.
However, I
wasn't sure about the behaviour during uninstall. How can I ensure that
the driver
does not get uninstalled (maybe another application uses it)? Are there
Okay. Thanks John and Phill. I am new to WiX. So i will start looking at the
WixLib now.
Thanks for the Dummy Property and PropertyRef Phill. I will try it today.
Could you please have a look at my other post on Harvesting all dll files
in a folder using heat. I am really confused. Your
I use MsiPackage/@Permanent='yes'
When my bundle is uninstalled, the CP210x ARP entry created by the SiLab
installer is still there and can be uninstalled by a user at a later time if
they want too.
--
View this message in context:
My suggestion is simple: don't use Heat for production work. It's great for
prototyping, but when it comes time to patch your product, you'll wish you
hadn't. It also tends to hide versioning errors that will come back to bite
you on upgrades.
--
John Merryweather Cooper
Senior Software
I looked at it earlier but don't have any experience in that area, so don't
want to give missinformation.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallUISequence-not-working-when-kept-out-of-product-tp7597976p7597994.html
Sent from the
See this thread for example of harvesting a folder:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatically-harvest-files-in-VS-2013-td7597592.html#a7597939
I don't have any experience with GAC or Com+, but I assume that the above
code could be modified to not set the
okay.
John, From your suggestion, what i understand is, i may have not to use heat
in pre-build events. It has to be used only once to harvest a file through
cmd . So, I have to harvest each dll (could be registering what regsvr32
does or GACing wat regasm does) seperately first, then include
Pre- and Post-BuildEvents are for people that are afraid of XML. You have far
better control, and it will be ultimately much more reliable, if you use a
BeforeBuild target and just build it in to your csproj. The main thing you
have to be careful of is that the exact timing when two given
Hi,
We have a package that install a network driver.
the network driver start type is boot_start_type.
during upgrade in case the driver file is in use the installer ask for
reboot.
after reboot the old driver is loaded but the sys file in the system folder
is the new one, if we reload the file
Just to be clear. You create a single MSI for the x64 and x86 driver
(based on inf-File / DifxAppExtension) and
use this together with other MSIs from burn or similar?
Will read the article referenced by you right now to understand how to
handle the dependency to the different
versions of
Hi Sir,
I had gone through that thread before.It says how to automate the task of
generating components for all files in a folder/sub folder as a whole. But
it does not tell about how push a dll file to GAC/DllRegisterServer.
So My question is,
For every file we include in the component we have
Hmmm. You shouldn't have to harvest file by file for heat. The usual practice
is to harvest part or all of a tree. You can use an XSLT transform passed to
Heat to add the assembly attribute if this is necessary.
That being said, it is very unusual to push the majority of a product's
Okay John.
That really sounds nice and suitable for my requirement. Thank you very
much. I am not finding much documentation on using xslt transforms with
heat. Could you please suggest me some links for this.
Since am learning wix in comparison with Installshield I am going little
okay.
Google is your friend . . .
Although what is being done with the transform is the height of silly (setting
KeyPath=no), the principles are the same:
http://stackoverflow.com/questions/8034798/wix-installer-using-xslt-with-heat-exe-to-update-attributes
--
John Merryweather Cooper
Senior
You'd only need one reference to an object inside the fragment for the entire
fragment to be included.
A more common approach I've used is to have a fragment per CA, and then use a
property ref to pull it into the product.
Ex:
Fragment
Condition Message=This application requires
The problem is with your custom action. The DLL which exports ExportTempHxDs,
does it have any dependencies (ex: VC runtime)?
-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: Monday, November 17, 2014 6:44 AM
To: wix-users@lists.sourceforge.net
I have a single MSI project, which get built twice to produce a x86 package
and a x64 package (with different names).
In the msi project I have something like this:
lt;?if $(var.Platform) = x64 ?
lt;?define RmProgramFiles6432Folder = ProgramFiles64Folder ?
lt;?define
Yeah!! its very clear now!!
If we have 10 CAs(if all are defered, then 10 install C.As, then 10
un-install CAs and then 10 RollBack C.A ) so it comes to 30 C.As in total.
So if i keep each C.A in separate .wxs (Eg. *VC2010SP1InstalledCA.wxs* in ur
case) then i have to include *3 * N
I'd have all 3 CA's in a fragment, one for install, one for uninstall, and one
for rollback. Schedule them in the fragment. (If you have multiple CA's for
the same purpose, then it would make sense to have them in the same fragment.)
You'd only need one property ref to pull in all 3.
I do
Phil,
you absolutely made my day! Thanks a lot for sharing this! Tomorrow
morning I'll try
it right away and will report whether it works for me.
Jan
Phill Hogland phogl...@rimage.com 17.11.2014 18:01
I have a single MSI project, which get built twice to produce a x86
package
and a x64
Ha ha ha.
I have already converted all of our Client Tools which have got very less
files and CAs , from InstallShield to WiX, along the learning path.
But,today what made me sick is the 150+ CAs ,all are horrible VBScript,
JavaScripts ,present in the Main Product installers. I heard like
No, if you have a deferred custom action (and all your custom actions that
modify machine state should be deferred), then you only need to provide a
matching rollback custom action (and proper scheduling) to provide that
functionality.
--
John Merryweather Cooper
Senior Software Engineer |
You need to define the folder tree based on those tow root folders.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Payload-not-copying-inf-tp7597985p7598013.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi John,
A small confusion here again.
if i provide install and a rollback, who will revert the system changes,
that were made during install, while un-installing?
How will WiX come to know to about system changes, made by a specific CA,
during un-install. ?
(Un-install C.A is nothing but the
Thaks for the S.O link. I am going through it.
Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-register-all-the-dlls-in-a-folder-and-sub-folder-to-GAC-using-heat-exe-tp7597977p7598015.html
Sent from the wix-users mailing
When installing the MSI Windows keeps track of everything being done
that is in the MSI - it's basically a single transaction with a
rollback script to undo everything. Windows has no idea what *your*
code did during an install so it's up to you to provide code to undo
what your CA did, and yes,
You might read through the WiX custom action source code as you read the MSI
SDK on creating custom actions. Writing custom actions is hard, there is lots
to learn to do it correctly.
_
Short replies here. Complete answers over there:
As I was/am learning wix, particularly as I converted from IS to wix and
needed to write a CAs for some printer driver configuration, I found it
helpful to study the WixExtensions, and particularly the WixGamingExtension
was helpful. These also demonstrate using an immeadiate custom action to
I'd also vote for using a semi-custom action where possible, in which at
runtime you modify the MSI DB to schedule changes. With this approach, the
existing transactional behaviors come for free. Ref:
http://www.joyofsetup.com/2007/07/01/semi-custom-actions/
-Original Message-
From:
if i provide install and a rollback, who will revert the system changes,
that were made during install, while un-installing?
When I've had to do this, usually only 2 CAs are needed: install and uninstall.
Rollback during an install is an uninstall.
Similarly, rollback during uninstall is an
Hi,
I have a similar scenario in which I would like to show progress in a more
meaningful way inside my installation package which tries to install another
burn installation using Exepackage.
Example: I would like to install a .NET framework or a isolated shell which
are both exe packages, I
I have an .msi package with 5 external .cab files in my bootstrapper
application(not being compressed in my bootstrapper application, external)
which installs well locally, and has DownloadUrl attribute for web-based
installation.
But, when I execute my bootstrapper application without its .msi
But to download .cab files of an .msi package from the web it seems to be
necessary to specify Payload elements for each .cab file under
MsiPackage element. Please see this
40 matches
Mail list logo
