Thanks Chris. I am not sure if I misunderstood the functionality of heat, but
I thought all it does was to declare the file structure in the target
machine. And the new output somehow indicates that: I tried to run heat on
both of my myLib.tlb file as well as myLib.dll files, the first wxs output
Does your DLL expose the DLLRegisterServer function? If so are all its
dependencies available to heat when you're trying to harvest it? Both are easy
enough to check using dependency walker.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
Thanks Pally! That's exactly why it went wrong in the first place: I only
copied the myLib.dll and myLib.tlb to another folder and ran heat there. Now
when I run heat in the project output folder, where all of the dependencies
are located, the COM information is finally harvested in the wxs file.
Yes, the file would have to exist at compile time if you are going to
use a File element. On the media tag for the file, ensure it isn't in an
embedded CAB. I believe a Media Tag with no Cabinet attribute would
result in the file being expected to be located alongside the source.
Since this is
Hi,
I need to copy files from the current directory of the user.
I use the registrySearch to get the variable environement HOMEPATH
Property Id=HOMEPATH
RegistrySearch Id=HomePathRegistrySearch Type=raw
Root=HKCU
Key=Volatile Environment Name=HOMEPATH /
/Property
Hello All,
I'm using Heat.exe to get registration information for my libraries and include
this info in my Wix code.
The registration works fine on machines when UAC is off, but it doesn't work on
machines where UAC is on. This happens even if I run my msi as
administrator(from bootstrapper
Is your MSI per-machine or per-user?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Remove the registrysearch and add
SetDirectory Id=HOMEPATH Value=[%HOMEDRIVE][%HOMEPATH] /
-Original Message-
From: Daniel DA COSTA [mailto:d.daco...@eca-assurances.com]
Sent: 23 May 2012 16:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question : Copy file to current user
And be prepared for domain users to have paths like N:\
(HOMEDRIVE=N: HOMEPATH=\)
Dave
On 5/23/2012 9:31 AM, Peter Shirtcliffe wrote:
Remove the registrysearch and add
SetDirectory Id=HOMEPATH Value=[%HOMEDRIVE][%HOMEPATH] /
-Original Message-
From: Daniel DA COSTA
It is per-user
23.05.2012 19:07, Pally Sandher pally.sand...@iesve.com
Is your MSI per-machine or per-user?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
hmm , Is there nobody interested in?
It could even speed up translating Wix's own localizations of the Wix v3 UI
and v3 Extensions ( http://wix.tramontana.co.hu/tutorial/localization ), if
WiX itself would be registered at Transifex and if a patch for adding wxl
support would be sent to Transifex
Thanks for correct question Pally, tried per-machine MSI version and it works
fine.
Do you know how to make it works for per-user installation?
Thanks
23.05.2012 19:07, Pally Sandher pally.sand...@iesve.com
Is your MSI per-machine or per-user?
Palbinder Sandher
Software Platform
Hello all I am currently working on an installer which works for Windows
Vista and Windows 7. When it comes to Windows XP on the other hand I
receive the error code 1722. I logged the installation process and found
that the error occurred when the command regsvr32 is ran for a particular
dll (the
It might actually be working for per-user...
A genuine per-user COM registration will be in HKCU for the installing user -
it won't be exposed to the entire system. In what sense is it not working?
Phil W
-Original Message-
From: vasjko [mailto:vas...@ua.fm]
Sent: Wednesday, May 23,
WiX has a tool for extracting COM information, it's harvested using heat.exe.
Even if you wanted to have the Dll self-register you don't need to do that by
running regsvr32 because Windows Installer has a SelfReg table, just get your
Dll in there.
Developers often think that installs work
On 22-May-12 08:22, Pally Sandher wrote:
1 - Slipstreaming MSP's doesn't work
Likely a bug. Need logs to know for sure.
Obviously Install isn't what should be happening here. Using the MSI
directly (circumventing Burn) will bring up the Uninstall process as expected.
What happens if you click
On 23-May-12 13:19, chefkoch wrote:
hmm , Is there nobody interested in?
I wouldn't say that but it doesn't look easy to get into, even if you
know Python, since you need a bunch of dependencies related to Django.
Plus, of course, it's not exactly geared for Windows developers since
they run
Hello,
I have 3 problems that i need some help.
1- Considering my App is installed and i generate a new installer with a
newer version, if i open it i get this screen:
http://img526.imageshack.us/img526/8471/screenshot20120523at457.png
2- After removing the installed App in Control Panel, i run
Thank you for the feedback. I'm not necessarily certain how to go about
doing that since I am developing the wix installer with visual studio. Also
here is the error that I am getting
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11722
Date: 5/23/2012
Time: 4:17:12
By not working I mean that my application which use component show Runtime
error 429:ActiveX component can't create object
If I register my library using regsvr32, application works fine. This happens
only MSI was installed per-user when UAC is on
23.05.2012 21:58, Wilson, Phil
You should never count on regsvr32.exe running as a deferred custom action from
a MSI. Is this COM component truly a shared component? If so then I would think
it should not be installed as a per user package. If you simply have a one or
more executables in the same install using this
The default WiX setup project template in WiX 3.6 generates a ComponentGroup
element with a Directory attribute on it. An early post by Rob says that
this attribute is meant to be inherited by any child components:
What I was thinking about was the ability to do ComponentGroup/@Directory,
which
Regsvr32 didn't work, that's the point. Maybe it couldn't find your file. :
C:\Program Files\[Product Information]\, looks wrong to me, because [ ] implies
a Windows Installer property, but not with that space in the middle.
The point of the tools like heat is that you don't need to run code
I only put the [] in to take out company information and I is heat only
available by using the command prompt?
Jelani Jackson
Junior Software Developer
jelani.jack...@powerdms.com
(800) 749-5104, x 6035
www.powerdms.com
LEGAL DISCLAIMER
The information transmitted is intended solely for the
Hey,
Cool, atleast some feedback ;)
Yeah, I understand. I also already created a ticket for wxl support at the
Transifex's issue tracker ( https://github.com/transifex/transifex/issues/59).
Do you think it also could be an option to manage the official
translations of the WixUI and WixExtensions
Hello all,
I am seeing a couple different errors on a customers machine when running a
burn based setup. The setup is about as simple as you can get - the
bootstrapper just wraps a single MSI.
Initially the customer was getting the following error: 0x800705ib - This
security ID may not be
Hi Luis
(1) Are you attempting a major upgrade or a minor one?
If its a major upgrade then your upgrade MSI should have an identical
upgrade ID but a different product ID and a different version from the
original MSI. I cant tell if the product code has changed or not as
you have only
Excellent, thanks for your help all. Got it done :)
cheers,
Andrew
On 23 May 2012 23:36, Hoover, Jacob jacob.hoo...@greenheck.com wrote:
Yes, the file would have to exist at compile time if you are going to
use a File element. On the media tag for the file, ensure it isn't in an
embedded
Having the same UpgradeCode (upgrade ID) isn't actually a requirement -
just that your new version has the older version's UpgradeCode in the
Upgrade table (Upgrade element). That's key - having the same UpgradeCode
doesn't mean you have an upgrade. In fact, if you don't schedule
Hi:
I'm trying to move a product I'm involved with to a burn bundle.
I using the non-managed bootstrapper-I'm not actually specifying a bootstrapper
in my bundle.
What I need to do is specify a default installation directory for this bundle.
How do I go about doing this?
When I click options it
30 matches
Mail list logo
