I have seen several messages about the licensing of Wix (e.g.
http://sourceforge.net/mailarchive/message.php?msg_id=29679148) but I am still
unsure of what I can do
I want to add one new, simplistic dialog to a Wix predefined UI sequence
(WixUI_FeatureTree.wxs). I followed instructions/e
Aha, thanks to Bill, Jacob, and Germano for the suggestions. "-scom -sreg"
seems to do the trick.
Regarding the original question, what is -scom useful for? Are there
situations where Class and ProgID elements are not desirable? I'm wondering
if the usage statement for that flag should be clari
Use -scom -sreg to suppress all COM and registry info if you are only
after file information.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, January 08, 2013 4:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-user
While it may not be optimal, you could use an XSLT to remove the unwanted
elements. If I had to guess, the scom element simply tells heat to use the MSI
Registry table instead of the TypeLib (and related) tables. I seem to remember
a post by Rob and maybe an ICE saying not to use the TypeLib du
I'm harvesting a directory/file structure. I do not want COM visible files
to be COM registered - this is for a server-side product that doesn't use
registry-based COM. Some of the assemblies are COM visible, so heat
harvests registry information. I tried adding the "suppress COM" (-scom)
option
The verbose log file will be your friend. It tells everything that the
installer is doing. Then you just need to figure out from the symptoms what is
wrong with your authoring. Sounds like you have something fundamentally wrong,
but sounds easy to overcome.
I don't use Wix_Mondo or Wix_UIInstal
What do you mean by "machine path"?
You probably mean I call the DPInst64.exe from system path, not from the
installed folder.
Yes, I checked and there really is one such file in DIFX folder. That could be
it.
--
Master
What's wrong? You're DPInst. Use DIFxApp, not DPInst. DIFxApp was
designed for MSI; you're trying to fit a square peg into a round hole using
DPInst.
For example, have you considered whether your MSI works correctly in a
rollback situation? Uninstall? Repair? Situations where the user
interf
I'm posting this back to the list. I prefer my Wix discussions to be shared.
I am aware of them, but I have not had a scenario where I have chosen to use
them, yet.
Conceptually, it requires carefully embedding debug code in your working
immediate custom actions that is triggered only when the
Rob, I agree with you that all can be made with custom actions, but we have
implemented a custom installer which drives the MSI MSP installation with the
WiX Engine, and drives our custom installation Task with specific actions which
fits better our specific needs:
The reason why we don't use C
I don't understand why you can't put the operations that modify the machine
in a package in the Chain. You say you have to do it in the BA but not why.
On Tue, Jan 8, 2013 at 6:41 AM, Raphael DUCOM wrote:
> Rob, that's why I said : " I'm working on a boostrapper which really needs
> elevated pr
Rob, that's why I said : " I'm working on a boostrapper which really needs
elevated privileges in order to completely install our solution. ( I know I
normally shouldn't do that, but we don't have choice because of the specific
components needed to be install ). "
So, is there a way to alter /
Is DPInst.exe in the machine's PATH? If not, that is the problem.
On Tue, Jan 8, 2013 at 3:19 AM, Branko Horvat wrote:
> I'm trying to make an installer using DPInst.exe as a CustomAction.
> Although there are some solutions provided, it fails.
> I can install the driver using rightclick on .inf
Your BootstrapperApplication should not be modifying machine state at all.
Machine state changes should be in "packages" (MSI, EXE, MSP, etc.) that
are listed in the Bundle/Chain element. Your BA can then control which
packages are installed.
On Tue, Jan 8, 2013 at 12:58 AM, Raphael DUCOM wrote:
I suspected that, thanks for the confirmation :-)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cleaning-the-cache-tp7582665p7582722.html
Sent from the wix-users mailing list archive at Nabble.com.
---
I'm trying to make an installer using DPInst.exe as a CustomAction. Although
there are some solutions provided, it fails.
I can install the driver using rightclick on .inf and Install. I can even use
manually DPInst.exe on installed folder.
When I use Notepad.exe instead of DPInst.exe it works.
The extended BA in my email is the only work around I know.
Neil
-Original Message-
From: Kannan24 [mailto:skan...@syncfusion.com]
Sent: 08 January 2013 11:05
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn with Progress bar
Hi Neil,
Thanks for your quick update.
Cou
Hi Neil,
Thanks for your quick update.
Could you please provide any workaround for the progress bar. I saw wix
build installing progress frequently, so like that we need to implement.
Please help me.
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.68
Hi Rob,
Many Thanks for your answer, but I believe I didn't give a good explanation...
When you say "put stuff that modifies the machine in the Chain and elevate", I
think you mean "using a custom action which elevates" like
isn't it ?
My scenario is different, I use the BootstrapperApplication
Hi Natalie,
I have the following function for extracting a release note out of my
MSI's binary table. Hopefully this is of some use to you. Once you've
got the file out, I expect executing it should be fairly simple, but let
me know if you're having issues with it.
void CMsiFile::ExtractOneR
20 matches
Mail list logo
