Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Custom-Action-which-call-win-32-dll-possible-tp7590295p7590335.html
Sent from the wix-users mailing list archive at Nabble.com.
--
yload.
> Date: Tue, 5 Nov 2013 12:02:21 -0800
> From: tomer.d...@intergraph.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Managed Custom Action which call win 32 dll,possible?
>
>
> Hi,
>
> Is it possible to use MakeSfxCA.exe to add a window 32
Hi,
Is it possible to use MakeSfxCA.exe to add a window 32 dll called by the
managed custom action?
Thanks in advance
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Custom-Action-which-call-win-32-dll-possible-tp7590295.html
Sent from t
ugust 28, 2012 7:30 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Custom Action using CAS
I've never done one of those myself, but a bit of search engine foo shows a few
potential links
http://social.msdn.microsoft.com/Forums/eu/vsto/thread/f46
stoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: Tuesday, August 28, 2012 9:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Custom Action using CAS
Hi Jacob,
Thanks for the reply, I'm installing an office 2003 VSTO project and usin
Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, August 28, 2012 4:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Custom Action using CAS
I guess the real question would be do you even need this in .Net 4?
http://blogs.msdn.com/b/shawnfa/archive/20
...@tech.flowcentric.com]
Sent: Tuesday, August 28, 2012 9:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed Custom Action using CAS
Hi, I have upgraded an old installer to a wix 3.7 custom action project that
uses the old CAS policy methods. I've upgraded the solution to runtime
Hi, I have upgraded an old installer to a wix 3.7 custom action project that
uses the old CAS policy methods. I've upgraded the solution to runtime 4 and
resulted receiving the exception
This method explicitly uses CAS policy, which has been obsoleted by the .NET
Framework.
// Get the policy l
ang...@winscribe.com]
Sent: Wednesday, May 05, 2010 11:28 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] managed custom action cannot access target directory
I have written a deferred CA which I need to manipulate a file that is
placed in the target-director
From: Adam Langley [mailto:alang...@winscribe.com]
Sent: Thursday, 6 May 2010 3:35 p.m.
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] managed custom action cannot access target directory
I have written a deferred CA which I need to manipulate a file that is placed
in
I have written a deferred CA which I need to manipulate a file that is placed
in the target-directory, at the end of the install.
What is weird is that the path is correctly evaluated in my logging messages,
but when I use the path to open a file, it says FILE NOT FOUND, even though I
KNOW the
I have written a deferred CA which I need to manipulate a file that is
placed in the target-directory, at the end of the install.
What is weird is that the path is correctly evaluated in my logging
messages, but when I use the path to open a file, it says FILE NOT
FOUND, even though I KNOW the
In article <[EMAIL PROTECTED]>,
"Aris Green" <[EMAIL PROTECTED]> writes:
> I have been using managec C++ CA's coded in Visual Studio 2003 for
> installs.
IMO, you might as well just use native C++ at that point.
> Well, you get the picture. One wrinkle, the VC 2005 requires linking to the
I have been using managec C++ CA's coded in Visual Studio 2003 for
installs. You create a .NET dll and use unmanaged exports .e.g
__declspec(dllexport) int __stdcall MyCustomAction(MSIHANDLE hInstall);
All your logic is in the installation package and you don't have to leave a
carcass behind with
MAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sankaranarayanan
Sent: 30 October 2007 18:36
To: Richard; WiX Users
Subject: Re: [WiX-users] Managed Custom Action using InstallUtilLib.dll
I use custom action for the following operations
1) Read XML Config file and set installer properties
2)
o: WiX Users
Cc: [EMAIL PROTECTED]
Sent: Tuesday, 30 October, 2007 10:03:10 AM
Subject: Re: [WiX-users] Managed Custom Action using InstallUtilLib.dll
In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]> writes:
> I am using Managed Custom Action [...]
What is
In article <[EMAIL PROTECTED]>,
Sankaranarayanan <[EMAIL PROTECTED]> writes:
> I am using Managed Custom Action [...]
What is your custom action doing? The MSDN documentation leads people
to believe that they need managed custom actions for all sorts of
things that the standard actions and
Hi All,
I am using Managed Custom Action as details in
http://blogs.msdn.com/josealmeida/archive/2004/11/08/253831.aspx
This approach works like a charm but I didn't quite like the idea of packaging
InstallUtilLib.dll file in MSI.
Is there a way to use the InstallUtilLib.dll present in the cl
ve to sign your managed code,
otherwise it surely won't run on the target system.
Oliver
From: Friedrich, Oliver [mailto:[EMAIL PROTECTED] On Behalf Of Mailinglist
Sent: Tuesday, September 11, 2007 12:41 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Manage
e executable.
Phil Wilson
From: Friedrich, Oliver [mailto:[EMAIL PROTECTED] On Behalf Of
Mailinglist
Sent: Tuesday, September 11, 2007 12:41 AM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Managed custom action return values
Hi,
>To say "
Hi,
>To say "writing managed custom actions is not supported" is a rather broad
>brush statement.
>There's nothing wrong with running managed code executables that run in their
>own process space.
>It's the installer class >custom actions that are not supported by WiX - I
>don't believe WiX ca
ble as a custom action.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rachna
Khune
Sent: Monday, September 10, 2007 8:43 AM
To: Mailinglist
Cc: (wix-users@lists.sourceforge.net)
Subject: Re: [WiX-users] Managed custom action return values
Thanks so much Olive
Subject: Re: [WiX-users] Managed custom action return values
Hello,
Writing managed custom actions is not supported. A standalone executable will
not see anything of the setup around.
I took two half ready projects and used them, to build up something that gives
you the possibility to write
re in English though.
If you need help in using this, feel free to ask back to me.
Oliver
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rachna Khune
Sent: Sonntag, 9. September 2007 04:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed custom action return value
Hi there
My custom action is a managed exe and I am attempting to do one of the two
choices below:
1) Show the exception messages from the custom action or be able to return
some error codes which I can log
2) Change the message that pops up when the custom action fails. The
default
Hi there
My custom action is a managed exe and I am attempting to do one of the two
choices below:
1) Show the exception messages from the custom action or be able to return
some error codes which I can log
2) Change the message that pops up when the custom action fails. The
default
t 14, 2007 4:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed Custom Action
I've been attempting to add a managed custom action following instructions that
I found on various blogs and by using dark on Visual Studio created MSI.
The gist of it is I use installut
These are all problems that can be solved if only the MSI team would just do
it. I've read the tactical/strategic arguments and I just don't buy it. (
Nor did anyone else who commented on that blog. )
John Hall <[EMAIL PROTECTED]> wrote: Alexei wrote:
> Have a look
> http://msdn2.microsoft
Alexei wrote:
> Have a look
> http://msdn2.microsoft.com/en-us/library/ms681383.aspx here
> - its the first one on the list. Course that's if it was an
> error from Windows Installer. If it was from your DLL then I
> got nothin'.
> However I believe the conventional wisdom is not to use
> m
Have a look http://msdn2.microsoft.com/en-us/library/ms681383.aspx here -
its the first one on the list. Course that's if it was an error from Windows
Installer. If it was from your DLL then I got nothin'.
However I believe the conventional wisdom is not to use managed CAs since
they place too m
I've been attempting to add a managed custom action following
instructions that I found on various blogs and by using dark on Visual
Studio created MSI.
The gist of it is I use installutillib.dll using ManagedInstall as the
DLLEntry. I also created custom action that sets a property for the
ma
31 matches
Mail list logo
