any workaround?
On Fri, Dec 10, 2010 at 11:31 PM, Blair wrote:
> Built-in Windows Installer can append or prepend values to MULTI_SZ during
> install, and (I suppose) remove those specific values on uninstall. I don't
> think it natively supports removing arbitrary values, though.
>
> -Orig
Hi,
I would like to check if a user exists in AD domain when username, domain,
password are entered in input dialog fields.
Can (and how) I use to check if a user exists or will I have to
write managed custom action to search for directoryEntry in AD? Can some one
provide pointers on how to ch
Did you find an example for the custom file open dialog? I am looking for
one too.
I read in one of the posts to create a custom C++ CA for fileopen. I dont
really know much about writing custom actions in native code and would like
an example to start with.
thanks.
On Fri, Dec 10, 2010 at 3:08 PM
If you are using VSTO then these two Office add-in articles on MSDN will
help you.
1. Registry Entries for Application-Level Add-Ins
http://msdn.microsoft.com/en-us/library/bb386106.aspx
2. Deploy add-ins that use VSTO3:
http://msdn.microsoft.com/en-us/library/cc563937.aspx
The second article
IIRC, you don't need a custom action at all. You just need to get the right
registry keys set. There is (or was) documentation somewhere in MSDN that
details all the configuration requried.
On Sun, Dec 12, 2010 at 11:31 AM, Sean Farrow
wrote:
> Hi:
> You may not need a custom action, is the addin
Hi Rob:
That now makes sense, having read the .cs code for the netfx extension.
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 12 December 2010 19:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] issues when using a c
Hi:
You may not need a custom action, is the addin written in native (unmanaged)
code, if so you should be able to use heat to extract a fragment with
registration information.
Hth
Sean.
-Original Message-
From: Janez Oman [mailto:janez.o...@gmail.com]
Sent: 12 December 2010 18:36
To:
The linker (light.exe) starts at your Product and starts pulling in code
referenced from there. So you need to somehow have a reference to the
Fragment below. The WiX Extensions typcially do this by adding a
CustomActionRef automatcially for you.
Since you don't have an Extension to automatically
Hi,
I'm looking for example of custom action written in VB or C#, which can
register and unregister MS Outlook Add-in.
I've found only Foke Post's post on the web, but I can't translate his
example.
Thanks in advance
Janez
--
Thank for the reply, works like a charm.
btw, The reason there is no GUI is because this msi and many others are
embedded in a larger installer that has GUI, it will never really be lunched
by a user, it was just simpler to explain...
On Sun, Dec 12, 2010 at 4:52 PM, Christopher Painter <
chr...@d
You'd have to change ProductFolder to PRODUCTFOLDER and then pass msiexec /i
foo.msi PRODUCTFOLDER=
BTW, I disagree strongly with installers that have no UI by design. It's
trivial for you to put a reference to WiXUI in your installer and then add /QN
at the command line if you really want
Hi:
I've written a custom action.
It appears from checking the binary table with orca that the ca dll is not been
added to the database.
The following is the fragment in a .wixlib file:
I've based this on the .wixlib that comes with the net
Hi,
My installer is not supposed to have any gui, instead, I would like to
install to program files by default or to a location selected by the user
when he is lunching my installer from the command line using msiexec.
I tried defining my directories like this:
...
and overriding by
13 matches
Mail list logo
