Re: [WiX-users] Calling functions in standard dlls

2008-09-08 Thread Gendelman, Yuri

You can create a simple proxy DLL which:
- will be compatible with WiX
- will redirect the custom action call to a standard DLL.




-Original Message-
Date: Sun, 07 Sep 2008 13:32:44 -0700
From: Bob Arnson [EMAIL PROTECTED]
Subject: Re: [WiX-users] Calling functions in standard dlls
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Sean Farrow wrote:
 Is there a custom action with in windows installer to call a function
 within a standard win32 dll?
   

No, that's not supported by MSI or supplemented by WiX.

-- 
sig://boB
http://joyofsetup.com/





--

Message: 3
Date: Mon, 08 Sep 2008 10:44:33 +1200
From: Ewart MacLucas [EMAIL PROTECTED]
Subject: Re: [WiX-users] launch webpage on uninstall
To: 'General discussion for Windows Installer XML toolset.'
wix-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii

Palbinder - thanks very much for that feedback, sounds like Wix 3.0 is
perhaps the way to go.  I was a little concerned about using a 'beta'
labelled open source solution for a commercial product but it sounds
like
it's perhaps stable enough to deploy on a large scale.

regards
  ewart


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pally
Sandher
Sent: Monday, 1 September 2008 11:18 p.m.
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] launch webpage on uninstall

 
WiX 3.0 does have 2-3 lines of code to implement this.
WiX 2.0 doesn't.

In WiX 3.0 I would do it thus:

UI
  Publish Dialog=ExitDialog Control=Finish Event=DoAction
Value=LaunchApplicationWIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 AND
(Installed AND NOT REINSTALL)/Publish
/UI

Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT Value=Launch My
Uninstall Web Page /
Property Id=WixShellExecTarget Value=http://www.iesve.com/; /

CustomAction Id=LaunchApplication BinaryKey=WixCA
DllEntry=WixShellExec Impersonate=yes /

Which would add a checkbox on the ExitDialog when Uninstalling allowing
the user to choose whether to see your web page or not. If you wanted to
be more draconian you could force the website to show up always on
Uninstall  remove the code to show the checkbox by removing the first
Property tag  modifying the inner text of the Publish tag accordingly.
This is all thanks to the ShellExecute CustomAction which is part of the
WiXUtilExtension.dll in WiX 3.0.

In WiX 2.0 you would need to write your own CustomAction to do this. Or
alternatively use one someone else has written for you -
http://blogs.msdn.com/noahc/archive/2007/05/09/shellexec-a-tiny-tool.asp
x
You could add that application in a Binary tag so that it's embedded
inside your MSI  call it in a Type 17 CustomAction on the Finish button
using a Publish tag as above. I'm not very familiar with the WiX 2.0
stock UI's anymore but I think you'd have to do some modification of the
ExitDialog if you want to add a CheckBox to conditionally show your
webpage (as before, being draconian  always forcing it is your choice).


WiX 3.0 is by far more complete than WiX 2.0. I'm honestly amazed that
I struggled by using v2.0 for so long. I only upgraded to v3.0 in May
this year  have shipped 6 releases already after using v2.0 since March
2007 having shipped 12 releases, 8 of them with upgrade patches as well
as full installers in that time. I honestly would never recommend using
v2.0 when v3.0 is available.

Palbinder Sandher 
Software Deployment and IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
http://www.iesve.com 

**Design, Simulate + Innovate with the Virtual Environment**

Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP

Email Disclaimer


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ewart
MacLucas
Sent: 30 August 2008 00:13
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] launch webpage on uninstall

Thanks Brian I did miss that however I was looking for someone with a
sample or a tutorial rather than downloading the source code to wix and
pawing through it.  

I imagined Wix 2.0 would have 2-3 lines of script to implement this, but
reading between the lines it sounds like your saying to your knowledge
wix 2.0 doesn't support the scripted launching of a url without
significantly more work?



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Rogers
Sent: Saturday, 30 August 2008 5:32 a.m.
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] launch webpage on uninstall

Hey Ewart,

I think you are missing what I am saying. This is already in WIX 3.0.
Since it is open 

Re: [WiX-users] finding .net 3.5 or greater

2008-05-20 Thread Gendelman, Yuri
Don,

You can use an approach from the article
How to determine which versions of the .NET Framework are installed and
whether service packs have been applied:
http://support.microsoft.com/kb/318785

Just enumerate and analyze subfolder names from the folder
%systemroot%\Microsoft.NET\Framework

It can be implemented as a Custom Action.


WBR,
Yuri

-Original Message-
Date: Mon, 19 May 2008 15:26:43 -0700
From: Don Tasanasanta (Volt) [EMAIL PROTECTED]
Subject: [WiX-users] finding .net 3.5 or greater
To: wix-users@lists.sourceforge.net
wix-users@lists.sourceforge.net
Message-ID:

[EMAIL PROTECTED]
icrosoft.com

Content-Type: text/plain; charset=us-ascii

How do you determine whether or not the version of .NET Framework on the
machine is greater than 3.5?

-
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Generate MSI during install

2008-05-16 Thread Gendelman, Yuri
Hello Phil,

You can create 2 separate WiX projects, for a server, and for a client.
Than add a Custom Action to the first one (server), which will launch a
batch file for compiling and linking the second one (client).

MBR,
Yuri


-Original Message-
Date: Fri, 16 May 2008 10:05:47 -0400
From: Phil Sayers [EMAIL PROTECTED]
Subject: [WiX-users] Generate MSI during install
To: wix-users@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1

I'm doing some planning for moving from our existing xcopy based
deployment
to msi (hopefully with wix) based installs.
Our application is written in .net framework 2.0
We have a client  server that need to be deployed with separate MSI's.

The server side of the application consists of a bunch of dll files and
an
IIS hosted remoting server.

I'd love to be able to touch or generate the client MSI as part of
the
server installation, based on information entered by a network admin as
part
of the server MSI install.

This way the client side of the application would already have server
name,
ip address, remoting endpoints written into it's config file and the end
user woudln't need to enter that info as part of the client install.

I'm new to Wix, but I have been lurking on this list for the last 6
months
or so.
Is this something i can do with Wix?  Has anyone done something like
this?

Thanks
Phil


-
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX-users Digest, Vol 23, Issue 180

2008-04-25 Thread Gendelman, Yuri
Hi,

This is the link you asked about. Just a hint: DIFx is part of DDK.

MSDN | MSDN Library | Win32 and COM Development |
 Windows Driver Kit | Device Installation | Design Guide }
 Using Driver Install Frameworks (DIFx)
 Driver Install Frameworks for Applications (DIFxApp):
http://msdn2.microsoft.com/en-us/library/ms790295.aspx


BR
Yuri Gendelman


-Original Message-
Message: 1
Date: Thu, 24 Apr 2008 22:45:36 -0500
From: Anthony Mahieu [EMAIL PROTECTED]
Subject: [WiX-users] Device Driver Installation
To: wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1

Hey guys, this is my first post.  I've got this relatively simple
project
(WiX v3, using Votive w/ VS2005) that I now need to add device driver
installation to.  I need to install two drivers if a specific feature is
selected to be installed.

From everything I'm reading, I need to use DIFxApp.  Unfortunately,
this is
where all helpful information I've found on the web stops.  I read in
previous questions that DIFxApp won't work with WiX 3.  Is this still
the
case?  If so, how would one recommend going about installing drivers in
WiX
3?  If the issue has been resolved and DIFxApp now works with WiX 3,
does
anyone have a tutorial on what needs to be done to install the drivers?

I know I should be looking into the DDK for some help, but I couldn't
even
find that (anyone have a link?).  Any help someone can give me would be
greatly appreciated, as I'm rather new to all this.

Thanks!

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Votive error

2008-04-22 Thread Gendelman, Yuri
Yes, it seems to be a bug.

The source of troubles seems to be the non-alphanumeric dot.
I know two ways to bypass:
- Rename file License.rtf to License_rtf and use
WixUILicenseRtf=License_rtf
- Move this definition into the .wxs:
WixVariable Id=WixUILicenseRtf Value=License.rtf /

I myself prefer the 2nd.


BR

Yuri Gendelman


-Original Message-
Date: Tue, 22 Apr 2008 11:59:05 +0100
From: Neil Sleightholm [EMAIL PROTECTED]
Subject: [WiX-users] Votive error
To: wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii

I am getting the following error in the properties page with the latest
build of Votive (3.0.4014.0):

 

WiX variable: The Wix variables you entered is not in a valid format.
Etc

 

The variable I am entering is WixUILicenseRtf=License.rtf which I
think is valid (it was in previous versions). Is anyone else seeing
this? Should I raise a bug?

 

Regards

 

Neil

 

Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 


-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX-users Digest, Vol 23, Issue 153

2008-04-22 Thread Gendelman, Yuri
I played with the 1st sample (SampleFirst.zip) from this tutorial:
http://www.tramontana.co.hu/wix/ and got the same message.

After removing some stuff from the .wxs:
- Vital='yes' from File ...
- DiskId='1' from File ...
- RemoveFolder ... / from Component ...
- empty directories
- Icon ...
and renewing Wix xmlns= ...

I got the project compiled and the MSI valid.
I strongly believe this is a bug.


Best Regards,

Yuri Gendelman


-Original Message-
Date: Tue, 22 Apr 2008 12:41:16 +0100
From: Neil Sleightholm [EMAIL PROTECTED]
Subject: [WiX-users] CNDL0001 : Culture 'en' is a neutral culture.
To: wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii

I am getting the following error from candle 

Microsoft (R) Windows Installer Xml Compiler version 3.0.4014.0

Copyright (C) Microsoft Corporation 2003. All rights reserved.

 

Access Control.wxs

candle.exe : error CNDL0001 : Culture 'en' is a neutral culture. It
cannot be used in formatting and parsing and therefore cannot be set as
the thread's current culture.

...

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users