I'm new too, so I'm gonna be verbose. Here's the steps I took using VS2008.
Create a new WiX installer project.
Add a new project to the solution - C#/VB/C++ custom action project.
Add the code to the custom action project to generate the file you want.
Compile the custom action project.
Referenc
Do you mean create as in generate a file (you could use a custom action to
do that) or create as in "here is my file, put it in that directory" which
is much simpler and just requires a reference to a file.
To dump, add something like this to a directory, but I think it's all in the
.chm so you p
tion. Then I go make sure all
the registration is correct. COM can get complex quickly, but if you keep it
simple the Class, ProgId, TypeLib and Interface elements make it look really
pretty (better than tons of RegistryX elements ).
On Mon, Oct 3, 2011 at 2:13 AM, David Birch (XStream Softw
Hi all.
I have one very old installer file and 2 patches created with vb6 and
InstallShield. My task is to form a single, shiny new installer, without
using any of the original source code (which is AWOL).
I've started with a fresh XP virtual machine, using DefenseWall (a host
intrusion protectio
4 matches
Mail list logo