Re: [WiX-users] can I use MD5 of file/dir for Id values?
Hi Chris, Thats interesting. Wow it's been a while since I thought of tcl/tk (which I loved actually :-) ) ... While on the autogeneration subject how do you deal with shortcut creation? do you exclude files to which you want to create shortcuts in the auto generated step and then add then in manually hand rolled components? Also do you get any validation errors when you have hex id values? I saw some errors where it complained that the file had a version but didn't have a language field (not 100% sure if it was ID related or name) but just wondering if the hex id results in clean validation or gives errors? thanks in advance + kind regards, Kaveh. Chris Ridd wrote: On Thursday, September 27, 2007, at 12:35PM, Kaveh Goudarzi [EMAIL PROTECTED] wrote: Hi Chris, Thanks for the advice :-) ... when you say with AUTO_ as documented ... where do you mean? I'm wondering if I missed some guidance doc which I need to look at before I make this change. It is just for me own personal use/documentation, so that when I'm looking at an enormous WXS file and I see some reference to AUTO_lots_of_hex then I know it got generated by my tools. Also what is the nature of your frag gen code/script? I found tallow in its current form (wix2.0) did not do what we needed but I'm very interested in combining what I have done (tallow ant custom task) with other code out there so that we can pool dev efforts and hopefully contribute to the WiX project as a whole. Our packaging infrastructure is written in Tcl, and it uses a flat file listing what files are expected to be installed in what target directories, and then it writes the WXS file using the directory structure implied by that file. It actually seems to work :-) Cheers, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
[WiX-users] can I use MD5 of file/dir for Id values?
Hi All, I want see if it's ok to use the md5 of a dir name relative to INSTALL dir as its ID? I have written a tallow equivalent ant task which automatically creates my fragment for me as part of my source build however I find I need to be able to refer to directories which were created as part of the auto-generated fragments. My thinking is that MD5 is a 32-character hexadecimal string so it should fit happily within the 72 chars that id has allocated in the db column and since its a deterministic derivative of the dir name I can always work out and refer to the id of any directory in the autogenerated fragements from within my hand rolles wxs files. Are there any downsides to this approach? what are the alternatives? thanks in advance + kind regards, Kaveh. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] can I use MD5 of file/dir for Id values?
Hi Chris, Thanks for the advice :-) ... when you say with AUTO_ as documented ... where do you mean? I'm wondering if I missed some guidance doc which I need to look at before I make this change. Also what is the nature of your frag gen code/script? I found tallow in its current form (wix2.0) did not do what we needed but I'm very interested in combining what I have done (tallow ant custom task) with other code out there so that we can pool dev efforts and hopefully contribute to the WiX project as a whole. thanks again + kind regards, Kaveh. Chris Ridd wrote: On Thursday, September 27, 2007, at 11:00AM, Kaveh Goudarzi [EMAIL PROTECTED] wrote: Hi All, I want see if it's ok to use the md5 of a dir name relative to INSTALL dir as its ID? I have written a tallow equivalent ant task which automatically creates my fragment for me as part of my source build however I find I need to be able to refer to directories which were created as part of the auto-generated fragments. That's pretty much what I do. I prefix them with AUTO_ partly as documentation, and partly because there's also a requirement that the first char in the Id is alphabetic. My thinking is that MD5 is a 32-character hexadecimal string so it should fit happily within the 72 chars that id has allocated in the db column and since its a deterministic derivative of the dir name I can always work out and refer to the id of any directory in the autogenerated fragements from within my hand rolles wxs files. Are there any downsides to this approach? what are the alternatives? It makes reading the wxs files a bit of a pain, but I can't think of any other downsides. Writing out the complete directory path in an XML comment before the Directory helps a little here. Cheers, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
[WiX-users] automatc dir / component fragment generation
Hi All, I'm working on a project to try to automate the generation of the installers for a project as much as possible. I tried to use tallow to generate the component fragments for the file assets which need to go in to the installer but its missing GUID's and hard codes the root dir. I'm in the process of writing an ant task to do this for me however I would really appreciate advice on the pitfalls if any of automating this. My plan is to create a component per directory (as with tallow -d option) but automatically generate and substitute the GUID's needed. -- Dr. Kaveh Goudarzi www: http://www.arkasoft.comEMail: [EMAIL PROTECTED] UK | Tel: +44-(0)20-8348-4704 Mob : +44-(0)7989-57-4849 US | Tel: +1-(408)-884-3936 Cell : +1-(408)-580-4812 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
[WiX-users] Id column size?
Hi All, What is the max column size of the Id e.g. File Id=?? .. or Component Id=??? ... I looked at the Component column in orca and it looks like it's 72 chars but I just wanted to confirm ... many thanks in advance for your help. kind regards, Kaveh. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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/VS+Votive - adding all files in a directory to a project?
Hi Sergie,
I'm just starting out on WiX as well so take what I say with a pinch
of salt but ... You can use tallow
(http://www.tramontana.co.hu/wix/lesson5.php#5.2) However IMHO it's
not pretty as you have to do a fair bit of manual fixing.
I was surprised that this was missing as well and asked if there were
any plans / requirements docs etc. for writing/completing tallow but
didn't get a response when I posted to the wix-users
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg11554.html
I'm in the process of writing an ant task so I can use it to generate
fragements from dir sets ... I'm literally writing it as we speak so
far it's following the pattern below
tallow guidCommand=guidgen.exe dir=. componentGroup=Core
fragmentFileName=Core_frag.wxa fragmentRoot=INSTALLDIR
!-- specify files under the same directory hierarchies --
!-- j15 mapped to jre15 --
dirGroup dir=${stage.dir}/j15 prefix=jre15
resourceSet location=${stage.dir}/j15
fileset dir=${stage.dir}/j15 casesensitive=yes
include name=**/*/
/fileset
/resourceSet
/dirGroup
...
/tallow
Idea being that you create you fragment Core_fraq.wxa by listing
dirGroup and specifying the files you need. The result should be a
component group called Core which contains refs to all the Components
specified in the dirGroup elements. One component per directory.
kind regards,
Kaveh.
Sergei Shelukhin wrote:
Hi.
I wonder if there's something similar to Project output concept for
Wix setup projects created using Votive.
We are currently using Web setup project followed by Custom Action that
is used to do most of the work to deploy a big ASP.NET http://ASP.NET
application. We are considering moving the deployment to either WiX or a
completely custom tool because of the utter lack of functionality in Web
Setup projects.
The problem is that the project has hundreds of files in a complicated
subdirectory tree in several separate projects and files are constantly
added, removed and moved around from version to version. Web setup has
the advantage of packaging all the required files easily, I wonder if
this is available for WiX.
Application is basically a monolithic entity and the update includes the
removal of most files (apart from maybe 3-5 files and 1-2
subdirectories) and redeployment of the new ones so we don't care about
component versioning problems.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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
