You could use ProcessMonitor from
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx and
run the COM server registration process ( the command line is probably
{yourexename} /regserver ).
The ProcessMonitor will give you the registry keys accessed by the
process.
Hello,
140% Full Ack :-)
The whole business around "setup" is painfully boring - for most developers and
IT pros. Finding someone who is not only willing to get the job done, but also
interested in the area of setups or even passionate about the whole process is
nearly impossible. If you find s
Unfortunately, the way heat.exe works right now, it cannot capture
registration from an executable. I've heard of a tool out there called
regcap.exe that can get you a .reg file.
On Sun, Jan 31, 2010 at 10:17 PM, sean farrow
wrote:
> Hi:
>
> I have a com server (a .exe file). How do I go about re
Hi:
I have a com server (a .exe file). How do I go about registering this file
within an installation. Can I use heat to give me the wix source code?
Any help appreciated.
Sean.
--
The Planet: dedicated and managed hos
I'm not sure we have any lawyers on this list and I definitely am not one...
but, the WiX toolset license (CPL) was picked to enable exactly the scenario
below. My interpretation of the license (which is essentially useless when
it comes to legal things) is that if you make changes to the code, you
Back in 2003 I was living in Virginia. I had about 5 years of InstallScript and
build automation under my belt.
I was really busy doing a build when I received an unexpected phone screen. I
was really distracted when the interviewer asked how InsallShield handled
locked files. Now I knew al
sorry, I was concerned with the WIX dll/s that might be included within my
MSI/s.
I have used the WIX custom actions for IIS configurations. But its not clear
to me is what are the repercussions from the licensing aspect of things.
--
View this message in context:
http://n2.nabble.com/Licensing
You're not clear if you're referring to WiX DLLs, your own DLLs or 3rd
party DLLs.
WiX itself is licensed under the CPL, see CPL.TXT where you installed
WiX for more information.
Generally I follow the rule of thumb that if a Merge Module is
available, use that. Licensing is usually pretty clear
When I interviewed for my current position I was asked about
familiarity with InstallShield, no questions about MSI itself. I
responded honestly that I had no idea, had used it once many moons ago
and found it complex, horrible and a pain to understand. What I didn't
realize for another 6+ months w
I have a small VBScript that uses
Scripting.FileSystemObject.GetFileVersion to retrieve the version of
my 'main' EXE. As part of my Nant script, I run the VBS, output to a
file, read it back in as a variable and then pass it as a command line
variable to WiX.
In my particular environment compilati
>> I don't want to use cmd.exe and do it indirectly. I am sure that there is a
>> way to do that in WIX.
Not that I could find ;) Custom actions seem to launch from some
folder ... I never bothered trying to figure out which but it seemed
to be either system32, %temp% or the folder of the MSI dep
What about writing a registry key (or keys) to indicate "Dependencies
of Product A are installed" ?
This could be a reference count that you increment when B, C, etc are
installed, or a more detailed description that indicates exactly what
products are installed. If you are using a bootstrapper yo
hi all,
I have developed our Installer using WIX. We are now ready to sell our
product.
What i am concerned is about Licensing issues that might relate to WIX as
there are some dll/s that might be contained within our MSI/s.
Anyone out there who has had similar issues that know what i might ha
There is some internal work in my team on creating such a framework. We hope
to have something out in the next couple of months. Not sure, as of yet,
where the tests will be loaded and executed from. The concept is to allow
for a pipeline which can execute on evaluations on an MSI and another
pipel
14 matches
Mail list logo
