thanks Jacob, that's got me thinking.
So, right now I have:
This gives the error:
Wei,
Just adding the DLL as a file in a component will install the file but
not register it as a COM component.
The use of the word "harvest" implies the use of Wix's "Heat" tool. A
quick look in the WiX help and a search online should give you all the
information you need to know about using
Run heat.exe on the DLL *as well* not *just* the TypeLib.
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 **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Thanks for your reply. But I tried to put myLib.dll into the same Component
as TypeLib element (I assume this is what you mean), but the result is the
same.
Plus, what's the difference between "harvest" and what I do now: just make
the dll as another component?
Like I mentioned, I originally put m
If you are building the .wixproj directly then the defaults specified in the
.wixproj should be true but the environment might have a say.
If you are building the .sln that contains the .wixproj then MSBuild will
choose a Configuration|Platform dependent on the .sln. You'll want to
investigate
You need to harvest the DLL as well as the TypeLib.
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 **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Regis
I need to create a WIX installer which will register one of our COM
libraries. As a fresh user in WIX as well as in COM, I couldn't find a
standard way to do it. I am using WIX 3.6
Here is how I do it. Firstly, I have one class library which is marked as
"Register for COM interop" in VS2010, so no
One option would be to create a custom action that would create
temporary records on install if the file exists on the installation
media. This would allow you to avoid the prompt, but it would mean you
would need to handle all the scenarios (install, upgrade, remove,
repair, etc) with temporary re
Ok a couple of things I've noticed, all your commands are exactly the
same for install, repair and uninstall, not sure if that will cause
any issues (I only ever set the InstallCommand). Also I set the LCID
in the InstallCommand as I had an issue where dotNet wasn't installing
correctly without it
1 - Slipstreaming MSP's doesn't work
Code:
[snip]
[snip]
What's meant to happen:
On a machine which has an existing v2.0 or later MSI installation, the MSP
should be applied to update to v2.2
On a machine which has nothing installed, v2.2 should be insta
I need to reboot, because I have to install a third party setup which fails, if
I do not reboot after installing dotnet.
Omitting the value attribute, has been the first thing I tried, but that led
to a weird behavior.
It seems that the dotnet setup is returning an exitcode after each step it
s
I would assume that the exitcode values are not working correctly as I
force a reboot when installing Windows Installer 4.5 but I don't
bother checking the exit codes (omit the value attribute). Do you
really need to reboot after installing dotnet?
Richard Mayes
On 22 May 2012 08:17, Simon Chrom
Hello everyone,
Has anyone done something like that? I need to force the reboot after Framework
has been installed.
This where I got.
What am I doing wrong?
Thanks for your efforts,
Simon
-
Hrm, alright - suppressing the GUI prompt itself is out of the question,
then.
Can anyone give any advice on what the best way to do this would be?
- optional file might be placed in the distribution directory (eg. a logo
file), with a specific name and location
- at MSI runtime if the file exis
14 matches
Mail list logo
