Light has the "default" Binder extension built in. Take a look at that for the
current implementation. I'm not aware of any other public implementations.
From: Thomas S. Trias [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 13:23
To: Rob Mensching
Cc: Windows Installer XML toolset developer mailing list; [EMAIL PROTECTED]
Subject: Re: [WiX-devs] Use URI's for file source
I realized I'd have to clean up the temporary files; I figured I would perform
the clean-up step upon termination. I'll look into the other places that use
the source path (such as the pdb generation).
I like the idea of using the extension framework, especially since the URI's I
want to use require an SVN protocol handler anyway. The extensions to the
compiler and extractor are pretty straightforward; are there already extensions
for the binder / linker that I could look at?
Thomas S. Trias
Senior Developer
Artizan Internet Services
http://www.artizan.com/
-------- Original Message --------
Subject: Re: [WiX-devs] Use URI's for file source
From: Rob Mensching <[EMAIL PROTECTED]><mailto:[EMAIL PROTECTED]>
To: Windows Installer XML toolset developer mailing list
<[email protected]><mailto:[email protected]>, [EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]><mailto:[EMAIL
PROTECTED]>
Date: 11/5/2008 12:46 PM
I'm not sure this is something the core toolset should do. We really need to
stabilize the core. What about building this as a Binder extension? I'd
rather make changes in the core toolset to enable these scenarios via
extensions rather than continue to grow the core toolset.
Thoughts?
-----Original Message-----
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 10:39
To: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>; Windows Installer XML toolset
developer mailing list
Subject: Re: [WiX-devs] Use URI's for file source
Thomas S. Trias wrote:
I am considering adding support for arbitrary URI's as the Source of
WixFile elements to Candle.exe. Besides the section around line 2956 of
Binder.cs (inside UpdateFileInformation), are there any other areas that
may be affected? I figure if I perform the download at that point to a
temporary location, I can build the FileInfo from the temporary file and
rewrite the in-memory records to reflect the temporary file location so
as not to break subsequent logic.
You'd also have to clean up the temporary files and maintain the
original source path, so the .wixpdb points to the real sources.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-devs mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wix-devs
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
