Re: [WiX-users] HI WIX 3.0 FileShare question

2007-10-19 Thread Sebastian Brand
What does your wix file look like?

FileShare uses the component's directory. If you want to use  
different drives for the fileshares your Directory structure must  
be correct. How do you get those E:\.. and D:\.. folders on the  
target system?


Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com


On Oct 19, 2007, at 6:02 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi,



 I am trying to create a FileShare using WIX 3.0, how can I give the  
 folder path dynamically to create different file share. Look like  
 it always creates a folder in the same root. I am trying to do  
 something like below



 Want to create \\computer1\Share1 for E:\root1\Share1



 And \\computer1\Share2 for D:\root\Share2



 I appreciate any help,



 Thank you,

 -Krishna





 image001.jpg Krishna Sapkota | Software Design Engineer |  
 SolutionsIQ | Technical Services  Engineering | v- 
 [EMAIL PROTECTED] | 425.703.7327

  Tell me how TSE can improve here



 image001.jpg
 -- 
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a  
 browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/ 
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Path to MSI?

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
Sebastian Brand [EMAIL PROTECTED]  writes:

 Using the [SourceDir] property? :-)

SourceDir is only correct after you call ResolveSource.

Calling ResolveSource can require that the original media be present.

This is problematic for upgrades and patching, because the source
media isn't likely to be around at those times.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Changing the text in the UI

2007-10-19 Thread 0x001A4

I can't seem to find the area where I can change the various texts in the UI.
For instance, I would like to change the title on some of the screens. This
what I see in the element:

Control Id=Title Type=Text X=135 Y=100 Width=220 Height=60
Transparent=yes NoPrefix=yes Text=$(loc.ExitDialogTitle) /

Where do I find loc.ExitDialogTitle and edit the text? I know I can change
Text= to whatever I want, but I'd rather find the source and change it
there.
-- 
View this message in context: 
http://www.nabble.com/Changing-the-text-in-the-UI-tf4654839.html#a13299735
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] example Wix project

2007-10-19 Thread hina1703

Hi,

Is there any example Wix project available which shows the installation of
an executable e.g. adobe reader
if the registry key is missing? I need to investigate WIX to find out if it
can be our installation tool. Currently we use InstallShield,  I need to
give demo with a sample project to give pros  cons.

So far I have been able build a sample project, but stuck with dependency
installations/ bootstrapper.

Any help, comment is appreciated.
-- 
View this message in context: 
http://www.nabble.com/example-Wix-project-tf4655657.html#a13302644
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Problems with copy file

2007-10-19 Thread Mike Menaker
Hi, 

I can't get copyfile to copy a file.

 

Here is the element I use (PATH is a property set earlier)

 

File Id=FILE1 Name=FILE1 LongName=MovieSearch.gram
Source=$(var.SOURCEPATH)\ \

CopyFile Id=CopyFile DestinationName= FILE1
DestinationLongName=file.txt DestinationProperty=[PATH]\dir\ /

/File

 

If I use DestinationProperty=PATH it works.

 

I have also tried DestinationProperty=PATH\dir\

 

 

What am I doing wrong?

 

Thanks,

Mike

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] example Wix project

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
hina1703 [EMAIL PROTECTED]  writes:

 Yes, I did. It is very helpful. I am trying to find out any bigger WIX
 project available for study including bootstrapper  other functions.

I am working on converting the installer for the sample code for my
book, but I haven't converted it from .vdproj to WiX yet.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] example Wix project

2007-10-19 Thread hina1703

Yes, I did. It is very helpful. I am trying to find out any bigger WIX
project available for study including bootstrapper  other functions.

Hina

Richard-45 wrote:
 
 
 In article [EMAIL PROTECTED],
 hina1703 [EMAIL PROTECTED]  writes:
 
 Is there any example Wix project available which shows the installation
 of
 an executable e.g. adobe reader
 
 Did you look at the tutorial?
 http://www.tramontana.co.hu/wix/
 
 -- 
 The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
   http://www.xmission.com/~legalize/book/download/index.html
 
 Legalize Adulthood! http://blogs.xmission.com/legalize/
 
 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

-- 
View this message in context: 
http://www.nabble.com/example-Wix-project-tf4655657.html#a13303311
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Shortcut Targets and Shared Components

2007-10-19 Thread Robert.Priest
Hello all,

 

I was just wondering if the was a bug or not:

 

So I have a component (in a separate fragment) that installs a file and
adds a shortcut on the Program Menu. That component is used in 2
features.  However, when I open the  compiled msi file in Orca and look
at the Shortcut Table, only ONE feature is listed as the target (what it
looks like is that it is the last feature to include the component). So
what happens is that if the first feature is selected, BUT NOT the
second, the files get installed but the shortcut does not.

 

What I had to do to rectify this is to create two additional components
that install the same shortcut - One that creates the shortcut for the
first feature. And, one that creates the same shortcut for the second
feature.

 

That way I get the two entries in my Shortcut table. One for the first
feature and one for the second.

 

My questions are:

 

1.   Is the a bug or just the way it works?

2.   Is this the best way to solve the problem?

 

Thanks.

 

 

 

 

image001.jpgBEGIN:VCARD
VERSION:2.1
X-MS-SIGNATURE:YES
N;LANGUAGE=en-us:Priest;Robert;S.;;Jr.
FN:Robert S. Priest Jr.
ORG:Bentley Systems
TITLE:Software Developer
TEL;WORK;VOICE:610-458-6270
TEL;WORK;FAX:610-458-1060
ADR;WORK;PREF:;;685 Stockton Drive;Exton;PA;19341;United States of America
LABEL;WORK;PREF;ENCODING=QUOTED-PRINTABLE:685 Stockton Drive=0D=0A=
Exton, PA  19341
X-MS-OL-DEFAULT-POSTAL-ADDRESS:2
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
X-MS-CARDPICTURE;TYPE=JPEG;ENCODING=BASE64:
 /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQY
 GBcUFhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/2wBDAQcHBwoIChMKChMoGhYa
 KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/wAAR
 CACEANMDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAECAwQFBgcICQoL/8QAtRAA
 AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
 FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
 h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQECAwQFBgcICQoL/8QAtREA
 AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
 NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
 hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwCcW8RygQqT1Kfy44P5GpFtCpAU59AeP8/l
 Qiq4AG447JEAKuI21G3BlUDOcEf1r6ycmj4yEE+hWtm3Qq4B2N0OMZ5x/jUV7iOezWMbRNME
 b6YJ4/KrNhzpFg/y/wCqyTjPUk9ifWobwbdQ0oHobgn6/I1czqNw5joVJKXKypNCGOFIyeQQ
 M1nhlj8wM2cMMsV4z9a17lEEnKE89c4qvPCkkZGzCgdF68D9a5qq97QzjotTNufJ8tQQhYnk
 EngevTrWNe2sIQJLPhXfcCwUAjPAJrZmtWCN5LllZM4Vjx7CsnU7eae3SOa0mlbBxhCMe+e1
 cs3ZnRBKSuei/szwpD4t8QpEroqWyDaxyfvevevouvn79mqJY9b1f/R5onFsiEyKBnDeo619
 A1xVPiPewn8JBRRRUHSABRRRQAAABRRRQAAABRRRQB8wwyCR9q+b
 KPUnAH5VYuGWO0mb5crGx+Xnt6n+dU7Z1mbeXaQqdpUggqfQjgg+2BUuqvs0u5Py7vLIwThR
 25r6mtKLjzRelj42kpJ2ktS9ZqV0+yU5P+jp1Oe2eveql5j+1dJUn/lq5/8AHDWMnipPLjRb
 YDairkvjIAwWxjgZ6D1otNTnvtf0zz4xGBIwUAHGSpHU9a4PbR5OVHfyNzudRIuIy0ZAcDPI
 zWTIY1d0TmRj8qjqf/rf/WrXuVYQHam7PH4f1rzzXdTm0yW4zciS8nxsjQDCL2J9Dz0FZ1n7
 1hOK5UzQ1q9hs0Md9cQ7/wDnmqb3/PP+FcidS1C6mMWlG6c+5DHH5cCrVhYJO6PdCSSaYk5U
 h1TjOWq+GurDckT27CXAZJIwpGOhG3g9eprHmSW9xSV3orf11Z6f+zV/aY13WRqcqsPs64UE
 Eg7+elfQdeC/s7hh4g1neio4tkGADnG7Pc+9e9VxVHeR7mEVqSCiiioOkACiiigA
 AACiiigAAACiiigD4ottRv8ARvDul6jqBmvrWdjEkpYCVAM8B+pHH3WBFbUO
 p2+v2KW9rcrJEXDShV2yhR13JyfxXI9dtYniazvJfh34VhtlGxd8khLAEbjkcHr1PSnWfgxp
 /DcM9mzLqAYyLIhO4+3t0z+NepQoVnBuO1vvPIrSoJrmfvX+49A0+2tYIw1nHEEIGGQD5vTk
 dazvFdyLOXSLk87LxOB6f5FcHpPjC/0u6a31hHkKth5VGJPqw6P9Thj/AHq2Nc1yx12G3t4r
 yGKRpFZJHbYinB6lsEfl+J61XtouDi9GZTw1SElLdHfX5kaGVIR5Z5AOea4GPQEXUZ2mIuLt
 8jLNhVJ6kHua9HikR0WRQD5ihg3XIIHOa5PxaJ47aaSNcmM7xjjd2xnseazxUm6aaCjBc7TK
 k1tZ29iqtchsZDJH0XBGCD2rn9RuIghSycD5WjCY3DJ57n9KpB21R7UAvCjgkq/I9u3t+tVb
 Wz8t1jlZnA6sCRkdjzjnkdq85Tmndna8LDkst+57f+zZeXN5r+syXpDTfZIgWEezo2MY9vWv
 oOvm39l6WOXxZ4iMMpkjFrEASB1Dc19I0N3Z04dWgkLRRRSNgAACiiigAAKK
 KKACiiigAAAPhN9RutQfT7FTuaOJIYk7IAACx/LNeg+DNZBuotKuYhb3ykLuB4kT
 1X8P5flwvhC0338sw+Yxrjd6s3AP5ZruU0M6qqPE3lXUTB4pV4Kctjn04FfXVI8tJJaW6Hyv
 OpVbNfPqWPiN4Kt9VcXWny7LxVy7EEh+e+P8/wBfMNV8L6ro0X2m7tGktCD/AKREd6Yx3I6f
 jivaPDeqS3Cmy1KJY9Qj5J7SL/eFW/Ftkr+FdYijXCvZysAP7wUn/CvIrUozV3uerCrOGi2O
 EtfEj6fp/hsvGZLW4sVQkc4aMlD79Av+FbWq3cWo2e2wj82aRNznP+rQHn6k9h7dqd8KND07
 xN4HtYtSjZpLOaWON1YhkyQx/mOtZXjJB4U1a9trC8mFxhWUgKeNuRkHPc/rXLSTqe43oayj
 GL5ktTl3OnLq6W6BHhbKbWSRxHkHlggyCSAPUZz2qkb+LUoW2208TRKsJt2O4phcdwDn37+m
 K9j+EWkW50czXFrLeSytvkkIAVm9SSRuPJ9a29d8P6ePE0GoQ2yRSvatA8ewDgHdu9+mM/Wo
 a9lJ2Sb/AAOhXnBNs5T9lSE2/iPX0AdU+zIQG6/f4z719LVwPw3063tL68lhhSN3jAYqMZ5r
 vq5Iu6ubQVkMoACiiigAAACiiigAAACiiigD5S+HOiKNKinu
 U/16Pc7WO3coGAM+vQ16XpGlQ2YESLnawXOME4EY598k/WsjTYIY4StmfP0/dDapzlgBhmK+
 vB+vFbkM5M0D7t4eQ4f1UzgDd+A617GIxbqS0eh5FHDxir21IL7w9b3ltGw/d3MKqY5V4Kt1
 

Re: [WiX-users] Problems with copy file

2007-10-19 Thread Mike Menaker
According to the Wix Documentation

DestinationProperty String  Set this value to a property
that will have a value that resolves to the full path of the destination
directory. The property does not have to exist in the installer database
at creation time; it could be created at installation time by a custom
action, on the command line, etc. This attribute cannot be specified in
conjunction with DestinationDirectory.

What do you mean add a Directory element. How would I do this when all I
have is a path?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard
Sent: Friday, October 19, 2007 2:58 PM
To: WiX Users
Subject: Re: [WiX-users] Problems with copy file


In article
[EMAIL PROTECTED]
m,
Mike Menaker [EMAIL PROTECTED]  writes:

 File Id=3DFILE1 Name=3DFILE1 LongName=3DMovieSearch.gram
 Source=3D$(var.SOURCEPATH)\ \
 CopyFile Id=3DCopyFile DestinationName=3D FILE1
 DestinationLongName=3Dfile.txt DestinationProperty=3D[PATH]\dir\
/
 /File   =20
 
 If I use DestinationProperty=3DPATH it works.
 
 I have also tried DestinationProperty=3DPATH\dir\
 
 What am I doing wrong?

DestinationProperty must be the name of a row in your Directory table,
it isn't a formatted string that gives the location of the directory.

So to fix your problem, add a Directory element that defines
[PATH]\dir and then reference this in your CopyFile element.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for
download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Problems with copy file

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
Mike Menaker [EMAIL PROTECTED]  writes:

 How would I do this?
 
 Path is set by the user like this from the UI:
 
 Control Id=EditPath Type=Edit X=21 Y=64 Width=237 Height=17
 
   Property=PATH
 
 It seems like I would just keep running into the problem of combining
 the property with a string.

Add a Directory element to define a directory.  The associated
property will be populated with the path to the directory.  When the
user edits the property, it will change the location of the directory
as used by the install.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Problems with copy file

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
Jeremy Farrell [EMAIL PROTECTED]  writes:

 Then, assuming the documentation's correct, it needs to be set to a property 
which contains the required path as the doc says. In
 
 DestinationProperty=PATH
 
 which works, you've set it to the name of the property called PATH which cont
ains a pathname. You need to create a property which contains a string giving t
he required path, and give the name of that property to DestinationProperty.

Its not a property he needs to create, its a row in the Directory
table (primary keys in the directory table are also mirrored as
properties containing the resolved path, but just creating a property
is not sufficient).

Create a row in the Directory table by inserting a Directory
element.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Problems with copy file

2007-10-19 Thread Mike Menaker
How would I do this?

Path is set by the user like this from the UI:

Control Id=EditPath Type=Edit X=21 Y=64 Width=237 Height=17

Property=PATH

It seems like I would just keep running into the problem of combining
the property with a string.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeremy
Farrell
Sent: Friday, October 19, 2007 3:25 PM
To: WiX Users
Subject: Re: [WiX-users] Problems with copy file

Then, assuming the documentation's correct, it needs to be set to a
property which contains the required path as the doc says. In

DestinationProperty=PATH

which works, you've set it to the name of the property called PATH which
contains a pathname. You need to create a property which contains a
string giving the required path, and give the name of that property to
DestinationProperty.

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of 
 Mike Menaker
 Sent: Friday, October 19, 2007 11:01 PM
 To: Richard; WiX Users
 Subject: Re: [WiX-users] Problems with copy file
 
 According to the Wix Documentation
 
 DestinationProperty   String  Set this value to a property
 that will have a value that resolves to the full path of the 
 destination
 directory. The property does not have to exist in the 
 installer database
 at creation time; it could be created at installation time by a custom
 action, on the command line, etc. This attribute cannot be 
 specified in
 conjunction with DestinationDirectory.
 
 What do you mean add a Directory element. How would I do this 
 when all I
 have is a path?
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Richard
 Sent: Friday, October 19, 2007 2:58 PM
 To: WiX Users
 Subject: Re: [WiX-users] Problems with copy file
 
 
 In article
 [EMAIL PROTECTED]
 ologies.co
 m,
 Mike Menaker [EMAIL PROTECTED]  writes:
 
  File Id=3DFILE1 Name=3DFILE1 LongName=3DMovieSearch.gram
  Source=3D$(var.SOURCEPATH)\ \
  CopyFile Id=3DCopyFile DestinationName=3D FILE1
  DestinationLongName=3Dfile.txt DestinationProperty=3D[PATH]\dir\
 /
  /File   =20
  
  If I use DestinationProperty=3DPATH it works.
  
  I have also tried DestinationProperty=3DPATH\dir\
  
  What am I doing wrong?
 
 DestinationProperty must be the name of a row in your Directory table,
 it isn't a formatted string that gives the location of the directory.
 
 So to fix your problem, add a Directory element that defines
 [PATH]\dir and then reference this in your CopyFile element.
 -- 
 The Direct3D Graphics Pipeline -- DirectX 9 draft available for
 download
   http://www.xmission.com/~legalize/book/download/index.html
 
 Legalize Adulthood! http://blogs.xmission.com/legalize/
 
 --
 --
 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and 
 a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and 
 a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Changing the text in the UI

2007-10-19 Thread 0x001A4

Sorry this can be ignored. I found the file. In case anyone else has the same
question, it is WixUI_en-us.wxl

0x001A4 wrote:
 
 I can't seem to find the area where I can change the various texts in the
 UI. For instance, I would like to change the title on some of the screens.
 This what I see in the element:
 
 Control Id=Title Type=Text X=135 Y=100 Width=220 Height=60
 Transparent=yes NoPrefix=yes Text=$(loc.ExitDialogTitle) /
 
 Where do I find loc.ExitDialogTitle and edit the text? I know I can change
 Text= to whatever I want, but I'd rather find the source and change it
 there.
 

-- 
View this message in context: 
http://www.nabble.com/Changing-the-text-in-the-UI-tf4654839.html#a13300884
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

2007-10-19 Thread Kelly Leahy
Yep... definitely shouldn't be moving built-in files like msbuild.exe. 
Lots of bad things can happen as most of those sorts of tools assume they 
are in a particular location when you're using them.

Better to qualify your path to the file or use the windows path to get a 
reference to it via batch files or something.

Kelly




hina1703 [EMAIL PROTECTED]

Sent by: [EMAIL PROTECTED]
10/19/2007 09:58 AM

To
wix-users@lists.sourceforge.net
cc

Subject
Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please 
guide)







Yes. I copied MSBuild.exe from
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 to C:\WIX\Test_Dot_NET for
building purpose. 

Thanks,
Hina
 

John Vottero wrote:
 
 Is that all the diagnostic output?  The Initial Properties section
 seems to be missing.
 
 Did you move or copy the MSBuild.exe executable?  If so, don't.  It
 looks for other files (like *.task) in the same location as the
 executable.
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:wix-users-
 [EMAIL PROTECTED] On Behalf Of hina1703
 Sent: Friday, October 19, 2007 9:54 AM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
 (Somebody, please guide)
 
 
 Here is the diagnostic output:
 
 Initial Items:
 BootstrapperFile
 Microsoft.JSharp.2.0
 Microsoft.Net.Framework.2.0
 Microsoft.Sql.Server.Express.1.0
 Microsoft.Windows.Installer.3.1
 
 Target Bootstrapper in file C:\WIX\Test_Dot_NET\Bootstrapper.xml:
   MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loade
 d from their expected location C:\WIX\Test_Dot_NET. Default tasks
 will not
 be
 available.
   C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootst
 rapper task was not found. Check the following: 1.) The name of the
 task in
 the
  project file is the same as the name of the task class. 2.) The task
 class
 is 
 public and implements the Microsoft.Build.Framework.ITask interface.
 3.)
 The ta
 sk is correctly declared with UsingTask in the project file, or in
 the
 *.tasks
  files located in the C:\WIX\Test_Dot_NET directory.
 Done building target Bootstrapper in project Bootstrapper.xml --
 FAILED.
 
 Done building project Bootstrapper.xml -- FAILED.
 
 Project Performance Summary:
94 ms  C:\WIX\Test_Dot_NET\Bootstrapper.xml   1 calls
 
 Target Performance Summary:
47 ms  Bootstrapper   1 calls
 
 Build FAILED.
 MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loaded
 from their expected location C:\WIX\Test_Dot_NET. Default tasks will
 not
 be av
 ailable.
 C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootstra
 pper task was not found. Check the following: 1.) The name of the
 task
 in
 the p
 roject file is the same as the name of the task class. 2.) The task
 class is
 pu
 blic and implements the Microsoft.Build.Framework.ITask interface.
 3.)
 The
 task
  is correctly declared with UsingTask in the project file, or in the
 *.tasks f
 iles located in the C:\WIX\Test_Dot_NET directory.
 1 Warning(s)
 1 Error(s)
 
 
 I don't have any *.tasks file in the project directory. Do I need to
 create
 one?
 
 Thanks,
 Hina
 
 John Vottero wrote:
 
  Try adding /v:diag to your command to get diagnostic output and post
  that.
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:wix-users-
  [EMAIL PROTECTED] On Behalf Of hina1703
  Sent: Thursday, October 18, 2007 5:27 PM
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
  (Somebody, please guide)
 
 
  Thanks for your reply John. I tried to build bootstrapper by doing
  msbuild
  bootstrapper.xml,
  but I am getting error:
  error MSB4036: The GenerateBootstrapper task was not found.
 
  My bootstrapper.xml looks as below:
 
  ?xml version=1.0 encoding=UTF-8?
Project
  xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  ItemGroup
BootstrapperFile Include=Microsoft.Net.Framework.2.0
  ProductName.NET Framework 2.0/ProductName
/BootstrapperFile
BootstrapperFile Include= Microsoft.Windows.Installer.3.1
  ProductNameWindows Installer 3.1/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.JSharp.2.0 
  ProductNameVisual J# redistributable/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0
  ProductNameSQL Server 2005 Express Edition/ProductName
/BootstrapperFile
  /ItemGroup
  Target Name=Bootstrapper
GenerateBootstrapper
  ApplicationFile=Test_Dot_NET.msi
  ApplicationName=Test_Dot_NET
  BootstrapperItems=@(BootstrapperFile) OutputPath=bin
  ComponentsLocation=Relative Culture=pt-PT
  Path=C:\WIX\Test_Dot_NET\release /
  /Target
/Project
 
  Please advise.
 
  Hina
 
  John Vottero wrote:

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

2007-10-19 Thread hina1703

Yes. I copied MSBuild.exe from
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 to C:\WIX\Test_Dot_NET for
building purpose. 

Thanks,
Hina
 

John Vottero wrote:
 
 Is that all the diagnostic output?  The Initial Properties section
 seems to be missing.
 
 Did you move or copy the MSBuild.exe executable?  If so, don't.  It
 looks for other files (like *.task) in the same location as the
 executable.
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:wix-users-
 [EMAIL PROTECTED] On Behalf Of hina1703
 Sent: Friday, October 19, 2007 9:54 AM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
 (Somebody, please guide)
 
 
 Here is the diagnostic output:
 
 Initial Items:
 BootstrapperFile
 Microsoft.JSharp.2.0
 Microsoft.Net.Framework.2.0
 Microsoft.Sql.Server.Express.1.0
 Microsoft.Windows.Installer.3.1
 
 Target Bootstrapper in file C:\WIX\Test_Dot_NET\Bootstrapper.xml:
   MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loade
 d from their expected location C:\WIX\Test_Dot_NET. Default tasks
 will not
 be
 available.
   C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootst
 rapper task was not found. Check the following: 1.) The name of the
 task in
 the
  project file is the same as the name of the task class. 2.) The task
 class
 is 
 public and implements the Microsoft.Build.Framework.ITask interface.
 3.)
 The ta
 sk is correctly declared with UsingTask in the project file, or in
 the
 *.tasks
  files located in the C:\WIX\Test_Dot_NET directory.
 Done building target Bootstrapper in project Bootstrapper.xml --
 FAILED.
 
 Done building project Bootstrapper.xml -- FAILED.
 
 Project Performance Summary:
94 ms  C:\WIX\Test_Dot_NET\Bootstrapper.xml   1 calls
 
 Target Performance Summary:
47 ms  Bootstrapper   1 calls
 
 Build FAILED.
 MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loaded
 from their expected location C:\WIX\Test_Dot_NET. Default tasks will
 not
 be av
 ailable.
 C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootstra
 pper task was not found. Check the following: 1.) The name of the
 task
 in
 the p
 roject file is the same as the name of the task class. 2.) The task
 class is
 pu
 blic and implements the Microsoft.Build.Framework.ITask interface.
 3.)
 The
 task
  is correctly declared with UsingTask in the project file, or in the
 *.tasks f
 iles located in the C:\WIX\Test_Dot_NET directory.
 1 Warning(s)
 1 Error(s)
 
 
 I don't have any *.tasks file in the project directory. Do I need to
 create
 one?
 
 Thanks,
 Hina
 
 John Vottero wrote:
 
  Try adding /v:diag to your command to get diagnostic output and post
  that.
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:wix-users-
  [EMAIL PROTECTED] On Behalf Of hina1703
  Sent: Thursday, October 18, 2007 5:27 PM
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
  (Somebody, please guide)
 
 
  Thanks for your reply John. I tried to build bootstrapper by doing
  msbuild
  bootstrapper.xml,
  but I am getting error:
  error MSB4036: The GenerateBootstrapper task was not found.
 
  My bootstrapper.xml looks as below:
 
  ?xml version=1.0 encoding=UTF-8?
Project
  xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  ItemGroup
BootstrapperFile Include=Microsoft.Net.Framework.2.0
  ProductName.NET Framework 2.0/ProductName
/BootstrapperFile
BootstrapperFile Include= Microsoft.Windows.Installer.3.1
  ProductNameWindows Installer 3.1/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.JSharp.2.0 
  ProductNameVisual J# redistributable/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0
  ProductNameSQL Server 2005 Express Edition/ProductName
/BootstrapperFile
  /ItemGroup
  Target Name=Bootstrapper
GenerateBootstrapper
  ApplicationFile=Test_Dot_NET.msi
  ApplicationName=Test_Dot_NET
  BootstrapperItems=@(BootstrapperFile) OutputPath=bin
  ComponentsLocation=Relative Culture=pt-PT
  Path=C:\WIX\Test_Dot_NET\release /
  /Target
/Project
 
  Please advise.
 
  Hina
 
  John Vottero wrote:
  
   You don't include the bootstrapper xml in the WiX file.  You
 build
  your
   app.msi from the WiX file. Then you build your bootstrapper by
  doing:
  
   msbuild bootstrapper_project_file.xml
  
  
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:wix-users-
   [EMAIL PROTECTED] On Behalf Of hina1703
   Sent: Tuesday, October 16, 2007 12:48 PM
   To: wix-users@lists.sourceforge.net
   Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
   (Somebody, please guide)
  
  
   Please reply.
  
   Hina
 

Re: [WiX-users] Path to MSI?

2007-10-19 Thread Wilson, Phil
The OriginalDatabase is sometimes a reasonable alternative, but it has
its own pitfalls too. The key issue is whether you want it in all
circumstances (uninstall, repair, modify) or only at first install. In
particular, OriginalDatabase works before any implicit ResolveSource in
the first install. 

Phil Wilson 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rad Ricka
Sent: Friday, October 19, 2007 8:05 AM
To: WiX Users; Richard
Subject: Re: [WiX-users] Path to MSI?

Thanks Richard,

SourceDir works perfectly for me; but thanks for pointing out the
pitfalls.

Regards,

R.


- Original Message - 
From: Richard [EMAIL PROTECTED]
To: WiX Users wix-users@lists.sourceforge.net
Sent: Friday, October 19, 2007 3:08 PM
Subject: Re: [WiX-users] Path to MSI?



 In article [EMAIL PROTECTED],
Sebastian Brand [EMAIL PROTECTED]  writes:

 Using the [SourceDir] property? :-)

 SourceDir is only correct after you call ResolveSource.

 Calling ResolveSource can require that the original media be present.

 This is problematic for upgrades and patching, because the source
 media isn't likely to be around at those times.
 -- 
 The Direct3D Graphics Pipeline -- DirectX 9 draft available for
download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/



-
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a
browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Path to MSI?

2007-10-19 Thread Rad Ricka
Thanks Richard,

SourceDir works perfectly for me; but thanks for pointing out the pitfalls.

Regards,

R.


- Original Message - 
From: Richard [EMAIL PROTECTED]
To: WiX Users wix-users@lists.sourceforge.net
Sent: Friday, October 19, 2007 3:08 PM
Subject: Re: [WiX-users] Path to MSI?



 In article [EMAIL PROTECTED],
Sebastian Brand [EMAIL PROTECTED]  writes:

 Using the [SourceDir] property? :-)

 SourceDir is only correct after you call ResolveSource.

 Calling ResolveSource can require that the original media be present.

 This is problematic for upgrades and patching, because the source
 media isn't likely to be around at those times.
 -- 
 The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Detecting processor model

2007-10-19 Thread jrcolons

How can I get those variables passed to my wix script?


Tony Hoyle wrote:
 
 Alexei Boukirev wrote:
 Windows NT 4 and above have several environemnt variables that you can
 check in MSI:
 PROCESSOR_IDENTIFIER, PROCESSOR_LEVEL, and PROCESSOR_REVISION.
 So  Pentium  II on one of my desktops has PROCESSOR_REVISION=0702,
 Pentium III on a server
 gives 0703, Pentium M on laptop - 0d06.
 
 Interesting.. how reliable is this?  I mamanged to change mine to 
 revesion  without it complaining at all.  Will it reset after some 
 minutes or when some system process notices?
 
 Tony
 
 
 ---
 SF.Net email is sponsored by:
 Tame your development challenges with Apache's Geronimo App Server.
 Download
 it for free - -and be entered to win a 42 plasma tv or your very own
 Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

-- 
View this message in context: 
http://www.nabble.com/Detecting-processor-model-tf334714.html#a13297294
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

2007-10-19 Thread John Vottero
Is that all the diagnostic output?  The Initial Properties section
seems to be missing.

Did you move or copy the MSBuild.exe executable?  If so, don't.  It
looks for other files (like *.task) in the same location as the
executable.

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:wix-users-
 [EMAIL PROTECTED] On Behalf Of hina1703
 Sent: Friday, October 19, 2007 9:54 AM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
 (Somebody, please guide)
 
 
 Here is the diagnostic output:
 
 Initial Items:
 BootstrapperFile
 Microsoft.JSharp.2.0
 Microsoft.Net.Framework.2.0
 Microsoft.Sql.Server.Express.1.0
 Microsoft.Windows.Installer.3.1
 
 Target Bootstrapper in file C:\WIX\Test_Dot_NET\Bootstrapper.xml:
   MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loade
 d from their expected location C:\WIX\Test_Dot_NET. Default tasks
 will not
 be
 available.
   C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootst
 rapper task was not found. Check the following: 1.) The name of the
 task in
 the
  project file is the same as the name of the task class. 2.) The task
 class
 is 
 public and implements the Microsoft.Build.Framework.ITask interface.
 3.)
 The ta
 sk is correctly declared with UsingTask in the project file, or in
 the
 *.tasks
  files located in the C:\WIX\Test_Dot_NET directory.
 Done building target Bootstrapper in project Bootstrapper.xml --
 FAILED.
 
 Done building project Bootstrapper.xml -- FAILED.
 
 Project Performance Summary:
94 ms  C:\WIX\Test_Dot_NET\Bootstrapper.xml   1 calls
 
 Target Performance Summary:
47 ms  Bootstrapper   1 calls
 
 Build FAILED.
 MSBUILD : warning MSB4010: The *.tasks files could not be
 successfully
 loaded
 from their expected location C:\WIX\Test_Dot_NET. Default tasks will
 not
 be av
 ailable.
 C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
 GenerateBootstra
 pper task was not found. Check the following: 1.) The name of the
task
 in
 the p
 roject file is the same as the name of the task class. 2.) The task
 class is
 pu
 blic and implements the Microsoft.Build.Framework.ITask interface.
3.)
 The
 task
  is correctly declared with UsingTask in the project file, or in the
 *.tasks f
 iles located in the C:\WIX\Test_Dot_NET directory.
 1 Warning(s)
 1 Error(s)
 
 
 I don't have any *.tasks file in the project directory. Do I need to
 create
 one?
 
 Thanks,
 Hina
 
 John Vottero wrote:
 
  Try adding /v:diag to your command to get diagnostic output and post
  that.
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:wix-users-
  [EMAIL PROTECTED] On Behalf Of hina1703
  Sent: Thursday, October 18, 2007 5:27 PM
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
  (Somebody, please guide)
 
 
  Thanks for your reply John. I tried to build bootstrapper by doing
  msbuild
  bootstrapper.xml,
  but I am getting error:
  error MSB4036: The GenerateBootstrapper task was not found.
 
  My bootstrapper.xml looks as below:
 
  ?xml version=1.0 encoding=UTF-8?
Project
  xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  ItemGroup
BootstrapperFile Include=Microsoft.Net.Framework.2.0
  ProductName.NET Framework 2.0/ProductName
/BootstrapperFile
BootstrapperFile Include= Microsoft.Windows.Installer.3.1
  ProductNameWindows Installer 3.1/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.JSharp.2.0 
  ProductNameVisual J# redistributable/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0
  ProductNameSQL Server 2005 Express Edition/ProductName
/BootstrapperFile
  /ItemGroup
  Target Name=Bootstrapper
GenerateBootstrapper
  ApplicationFile=Test_Dot_NET.msi
  ApplicationName=Test_Dot_NET
  BootstrapperItems=@(BootstrapperFile) OutputPath=bin
  ComponentsLocation=Relative Culture=pt-PT
  Path=C:\WIX\Test_Dot_NET\release /
  /Target
/Project
 
  Please advise.
 
  Hina
 
  John Vottero wrote:
  
   You don't include the bootstrapper xml in the WiX file.  You
build
  your
   app.msi from the WiX file. Then you build your bootstrapper by
  doing:
  
   msbuild bootstrapper_project_file.xml
  
  
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:wix-users-
   [EMAIL PROTECTED] On Behalf Of hina1703
   Sent: Tuesday, October 16, 2007 12:48 PM
   To: wix-users@lists.sourceforge.net
   Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
   (Somebody, please guide)
  
  
   Please reply.
  
   Hina
  
   hina1703 wrote:
   
Thanks for the reply. So will the bootstrapper file be .xml
 file?
   How
   can
I include xml file into wxs file?
Is there any good 

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

2007-10-19 Thread hina1703

Here is the diagnostic output:

Initial Items:
BootstrapperFile
Microsoft.JSharp.2.0
Microsoft.Net.Framework.2.0
Microsoft.Sql.Server.Express.1.0
Microsoft.Windows.Installer.3.1

Target Bootstrapper in file C:\WIX\Test_Dot_NET\Bootstrapper.xml:
  MSBUILD : warning MSB4010: The *.tasks files could not be successfully
loade
d from their expected location C:\WIX\Test_Dot_NET. Default tasks will not
be
available.
  C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
GenerateBootst
rapper task was not found. Check the following: 1.) The name of the task in
the
 project file is the same as the name of the task class. 2.) The task class
is 
public and implements the Microsoft.Build.Framework.ITask interface. 3.)
The ta
sk is correctly declared with UsingTask in the project file, or in the
*.tasks
 files located in the C:\WIX\Test_Dot_NET directory.
Done building target Bootstrapper in project Bootstrapper.xml -- FAILED.

Done building project Bootstrapper.xml -- FAILED.

Project Performance Summary:
   94 ms  C:\WIX\Test_Dot_NET\Bootstrapper.xml   1 calls

Target Performance Summary:
   47 ms  Bootstrapper   1 calls

Build FAILED.
MSBUILD : warning MSB4010: The *.tasks files could not be successfully
loaded
from their expected location C:\WIX\Test_Dot_NET. Default tasks will not
be av
ailable.
C:\WIX\Test_Dot_NET\Bootstrapper.xml(18,7): error MSB4036: The
GenerateBootstra
pper task was not found. Check the following: 1.) The name of the task in
the p
roject file is the same as the name of the task class. 2.) The task class is
pu
blic and implements the Microsoft.Build.Framework.ITask interface. 3.) The
task
 is correctly declared with UsingTask in the project file, or in the
*.tasks f
iles located in the C:\WIX\Test_Dot_NET directory.
1 Warning(s)
1 Error(s)


I don't have any *.tasks file in the project directory. Do I need to create
one?

Thanks,
Hina

John Vottero wrote:
 
 Try adding /v:diag to your command to get diagnostic output and post
 that.
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:wix-users-
 [EMAIL PROTECTED] On Behalf Of hina1703
 Sent: Thursday, October 18, 2007 5:27 PM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
 (Somebody, please guide)
 
 
 Thanks for your reply John. I tried to build bootstrapper by doing
 msbuild
 bootstrapper.xml,
 but I am getting error:
 error MSB4036: The GenerateBootstrapper task was not found.
 
 My bootstrapper.xml looks as below:
 
 ?xml version=1.0 encoding=UTF-8?
   Project
 xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
 ItemGroup
   BootstrapperFile Include=Microsoft.Net.Framework.2.0
 ProductName.NET Framework 2.0/ProductName
   /BootstrapperFile
   BootstrapperFile Include= Microsoft.Windows.Installer.3.1
 ProductNameWindows Installer 3.1/ProductName
   /BootstrapperFile
   BootstrapperFile Include=Microsoft.JSharp.2.0 
 ProductNameVisual J# redistributable/ProductName
   /BootstrapperFile
   BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0
 ProductNameSQL Server 2005 Express Edition/ProductName
   /BootstrapperFile
 /ItemGroup
 Target Name=Bootstrapper
   GenerateBootstrapper
 ApplicationFile=Test_Dot_NET.msi
 ApplicationName=Test_Dot_NET
 BootstrapperItems=@(BootstrapperFile) OutputPath=bin
 ComponentsLocation=Relative Culture=pt-PT
 Path=C:\WIX\Test_Dot_NET\release /
 /Target
   /Project
 
 Please advise.
 
 Hina
 
 John Vottero wrote:
 
  You don't include the bootstrapper xml in the WiX file.  You build
 your
  app.msi from the WiX file. Then you build your bootstrapper by
 doing:
 
  msbuild bootstrapper_project_file.xml
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:wix-users-
  [EMAIL PROTECTED] On Behalf Of hina1703
  Sent: Tuesday, October 16, 2007 12:48 PM
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Adding Bootstrapper code to wxs file.
  (Somebody, please guide)
 
 
  Please reply.
 
  Hina
 
  hina1703 wrote:
  
   Thanks for the reply. So will the bootstrapper file be .xml file?
  How
  can
   I include xml file into wxs file?
   Is there any good tutorial avaliable on bootstrapper? I find it
 very
   confusing topic with very little help available.
  
   Hina
  
   Sebastian Brand-2 wrote:
  
   Hina,
  
   You have to split up that file into 2 files, one for the
  bootstrapper
   and one for wix.
  
  
   Best regards,
   Sebastian Brand
  
   Instyler Software - http://www.instyler.com
  
  
   On Oct 16, 2007, at 4:06 PM, hina1703 wrote:
  
  
   Hello,
  
   I have a basic question. I am new to XML. I am trying to add a
   bootstrapper
   code to my wxs file.
  
   ?xml version=1.0 encoding=UTF-8?
 Project
 xmlns=http://schemas.microsoft.com/developer/msbuild/
   2003
  
   ItemGroup
 

Re: [WiX-users] Path to MSI?

2007-10-19 Thread Sebastian Brand
Using the [SourceDir] property? :-)

Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com


On Oct 19, 2007, at 10:10 AM, Rad Ricka wrote:

 Hello,

 what's the most effective way to programmatically get the path to  
 where my MSI is being run from?

 Cheers,

 R.
 -- 
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a  
 browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/ 
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] HI WIX 3.0 FileShare question

2007-10-19 Thread Sebastian Brand
I'm not sure if this works, but give it a try:

You can create a new Directory element:

Directory Name=[BLA]
  Component
   FileShare...
.../

and call the msi (using msiexec) with the parameter BLA=D:\Share1

The location of the new Directory may be anywhere as the BLA property  
is passed with a full path.


Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com


On Oct 19, 2007, at 10:04 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi Sebastian,

 Thank you very much for the response.

 I am using following code snippet for creating file-share:

 Directory Id=TARGETDIR Name=SourceDir
 Directory Id=ProgramFilesFolder
   Directory Id=INSTALLLATIONDIR Name=$(var.ProductName)

 Component Id=ProductComponent Guid=7f1d40c6-7366-4b3a- 
 b0e0-59aff11ce19e
   CreateFolder/
   .
 /Component

 !-- Creating share folder for storing share info --
 !-- Grant Read permission to IIS_NETWORKSERVICE and --
 !-- Grant write permission to Win32ServiceAccount --

 Directory Name=PUBLICSHARE Id=D_PUBLICSHARE 
   Component Id=C_PUBLICSHARE_1 Guid={GUID} DiskId=1
 CreateFolder/
 util:FileShare Id=S_PUBLICSHARE  
 Description=PublicShare Name=PublicShare
   util:FileSharePermission User=Win32ServiceAccount  
 GenericRead=yes Read=yes/
   util:FileSharePermission User=IIS_NETWORKSERVICE  
 GenericRead=yes Read=yes /
 /util:FileShare
   /Component
 /Directory
   /Directory
 /Directory
   /Directory

 This creates the share folder inside [INSTALLLATIONDIR], while  
 taking this share-folder section outside but inside the logical  
 Directory (the outmost directory), then it creates the file-share  
 in the root directory of the drive where the product is been  
 installed.

 But I want to create the file-share in the different drives like D: 
 \Share1 or E:\Share2 , (they are passed as parameter (Property) to  
 MSI. If the physical directory for the share in the target drive  
 does not exist, I want to create it, FYI: they all exists in the  
 same machine.)

 I am trying to find out the way to do it using FileShare element of  
 WIX 3.0, Can I perform this using the FileShare element? Or I need  
 to use some scripting command (i.e. using xcacls.vbs) in a custom  
 action.

 I would appreciate any clue.

 Thank you,
 -Krishna

  Krishna Sapkota | Software Design Engineer | SolutionsIQ |  
 Technical Services  Engineering | [EMAIL PROTECTED] |  
 425.703.7327
  Tell me how TSE can improve here

 -Original Message-
 From: Sebastian Brand [mailto:[EMAIL PROTECTED]
 Sent: Friday, October 19, 2007 12:33 AM
 To: Krishna Sapkota (Solutions IQ)
 Cc: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] HI WIX 3.0 FileShare question

 What does your wix file look like?

 FileShare uses the component's directory. If you want to use
 different drives for the fileshares your Directory structure must
 be correct. How do you get those E:\.. and D:\.. folders on the
 target system?


 Best regards,
 Sebastian Brand

 Instyler Software - http://www.instyler.com


 On Oct 19, 2007, at 6:02 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi,



 I am trying to create a FileShare using WIX 3.0, how can I give the
 folder path dynamically to create different file share. Look like
 it always creates a folder in the same root. I am trying to do
 something like below



 Want to create \\computer1\Share1 for E:\root1\Share1



 And \\computer1\Share2 for D:\root\Share2



 I appreciate any help,



 Thank you,

 -Krishna





 image001.jpg Krishna Sapkota | Software Design Engineer |
 SolutionsIQ | Technical Services  Engineering | v-
 [EMAIL PROTECTED] | 425.703.7327

  Tell me how TSE can improve here



 image001.jpg
 - 
 -
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a
 browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] HI WIX 3.0 FileShare question

2007-10-19 Thread Krishna Sapkota (Solutions IQ)
Hi Sebastian,

Thank you very much for the response.

I am using following code snippet for creating file-share:

Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
  Directory Id=INSTALLLATIONDIR Name=$(var.ProductName)

Component Id=ProductComponent 
Guid=7f1d40c6-7366-4b3a-b0e0-59aff11ce19e
  CreateFolder/
  .
/Component

!-- Creating share folder for storing share info --
!-- Grant Read permission to IIS_NETWORKSERVICE and --
!-- Grant write permission to Win32ServiceAccount --

Directory Name=PUBLICSHARE Id=D_PUBLICSHARE 
  Component Id=C_PUBLICSHARE_1 Guid={GUID} DiskId=1
CreateFolder/
util:FileShare Id=S_PUBLICSHARE Description=PublicShare 
Name=PublicShare
  util:FileSharePermission User=Win32ServiceAccount 
GenericRead=yes Read=yes/
  util:FileSharePermission User=IIS_NETWORKSERVICE 
GenericRead=yes Read=yes /
/util:FileShare
  /Component
/Directory
  /Directory
/Directory
  /Directory

This creates the share folder inside [INSTALLLATIONDIR], while taking this 
share-folder section outside but inside the logical Directory (the outmost 
directory), then it creates the file-share in the root directory of the drive 
where the product is been installed.

But I want to create the file-share in the different drives like D:\Share1 or 
E:\Share2 , (they are passed as parameter (Property) to MSI. If the physical 
directory for the share in the target drive does not exist, I want to create 
it, FYI: they all exists in the same machine.)

I am trying to find out the way to do it using FileShare element of WIX 3.0, 
Can I perform this using the FileShare element? Or I need to use some scripting 
command (i.e. using xcacls.vbs) in a custom action.

I would appreciate any clue.

Thank you,
-Krishna

 Krishna Sapkota | Software Design Engineer | SolutionsIQ | Technical Services 
 Engineering | [EMAIL PROTECTED] | 425.703.7327
 Tell me how TSE can improve here

-Original Message-
From: Sebastian Brand [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 12:33 AM
To: Krishna Sapkota (Solutions IQ)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] HI WIX 3.0 FileShare question

What does your wix file look like?

FileShare uses the component's directory. If you want to use
different drives for the fileshares your Directory structure must
be correct. How do you get those E:\.. and D:\.. folders on the
target system?


Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com


On Oct 19, 2007, at 6:02 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi,



 I am trying to create a FileShare using WIX 3.0, how can I give the
 folder path dynamically to create different file share. Look like
 it always creates a folder in the same root. I am trying to do
 something like below



 Want to create \\computer1\Share1 for E:\root1\Share1



 And \\computer1\Share2 for D:\root\Share2



 I appreciate any help,



 Thank you,

 -Krishna





 image001.jpg Krishna Sapkota | Software Design Engineer |
 SolutionsIQ | Technical Services  Engineering | v-
 [EMAIL PROTECTED] | 425.703.7327

  Tell me how TSE can improve here



 image001.jpg
 --
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a
 browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Custom Actions.

2007-10-19 Thread Jason Rivers
Hi Dana,

The custom Action i'm calling, actually gets a list of files with an
extension of .DIN  .DSE from the directory where our product has been
installed to. These define the Keyboard for our application, and a session
file, the user can change these during the install, this is why it is in a
custom action and not through the .MSI.
 but because it get's the the list of files from where the installer has
just installed the files to, it does need to have the INSTALLDIR parsed to
it.

I'm reverse engineering an InstallShield installer because our company
wishes to move away from that and have our overnight build machine
automatically build the installers, so the WiX system is great for that, if
I can get this working anyway.

the main issue is I'm reverse engineering something that was thrown together
very quickly with limited time.

anyway, if the command I'm using is correct to parse the information then I
will try and look elsewhere for the issue, it's just this does work on the
old (installshield) installer using an MSI.

Jason.

On 10/19/07, Dana Gutride [EMAIL PROTECTED] wrote:

 What does the msi log say is happening here?  That is usually the best way
 to troubleshoot custom action errors.  The other trick I'll use is pop up a
 message box from my custom action code and then attach to it with the
 debugger.  As a rule, any custom actions that modify the target system
 should be deferred and you won't have access to msi properties (use
 CustomActionData from a dll).

 One question for you, though...  wouldn't it be better to utilize the MSI
 registry table for creating registry keys?  It is not only transactional
 (your keys are removed if the install fails), but they are removed on
 uninstall and you can include properties and all kinds of other good stuff
 in them.

 Dana

 On 10/19/07, Jason Rivers [EMAIL PROTECTED] wrote:

  Hi all.
 
  I'm having some trouble with parsing information to a custom action.
 
  I have the command:
 
  CustomAction Id=InstallUser Impersonate=yes Return=ignore
  Execute=oncePerProcess BinaryKey= instexe.exe ExeCommand=0
  /InstallUser [INSTALLDIR] [ALLUSERS] /
 
 
  and the lines
 
 
  InstallExecuteSequence
   Custom Action=InstallUser After=InstallFilesNOT
  Installed/Custom
  /InstallExecuteSequence
 
 
  I don't know about the [ALLUSERS] but I know it is not parsing the
  [INSTALLDIR] parameter to the EXE, this EXE sets up all the windows
  registry settings for the application we write.
 
  if someone could help with where I'm going wrong here and give me some
  advice on how to parse the INSTALL Directory information, and the Users home
  / All Users Home folders to an EXE or DLL it would be very appreciated.
 
  Thanks in advanced.
 
  Jason.
 
 
  -
  This SF.net email is sponsored by: Splunk Inc.
  Still grepping through log files to find problems?  Stop.
  Now Search log events and configuration files using AJAX and a browser.
  Download your FREE copy of Splunk now  http://get.splunk.com/
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Custom Actions.

2007-10-19 Thread Dana Gutride
What does the msi log say is happening here?  That is usually the best way
to troubleshoot custom action errors.  The other trick I'll use is pop up a
message box from my custom action code and then attach to it with the
debugger.  As a rule, any custom actions that modify the target system
should be deferred and you won't have access to msi properties (use
CustomActionData from a dll).

One question for you, though...  wouldn't it be better to utilize the MSI
registry table for creating registry keys?  It is not only transactional
(your keys are removed if the install fails), but they are removed on
uninstall and you can include properties and all kinds of other good stuff
in them.

Dana

On 10/19/07, Jason Rivers [EMAIL PROTECTED] wrote:

 Hi all.

 I'm having some trouble with parsing information to a custom action.

 I have the command:

 CustomAction Id=InstallUser Impersonate=yes Return=ignore
 Execute=oncePerProcess BinaryKey= instexe.exe ExeCommand=0
 /InstallUser [INSTALLDIR] [ALLUSERS] /


 and the lines


 InstallExecuteSequence
  Custom Action=InstallUser After=InstallFilesNOT
 Installed/Custom
 /InstallExecuteSequence


 I don't know about the [ALLUSERS] but I know it is not parsing the
 [INSTALLDIR] parameter to the EXE, this EXE sets up all the windows
 registry settings for the application we write.

 if someone could help with where I'm going wrong here and give me some
 advice on how to parse the INSTALL Directory information, and the Users home
 / All Users Home folders to an EXE or DLL it would be very appreciated.

 Thanks in advanced.

 Jason.

 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Detecting processor model

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
jrcolons [EMAIL PROTECTED]  writes:

 How can I get those variables passed to my wix script?

You can access environment variables from a Formatted string using
[%envarname] syntax.  You can use a type 51 CA to set a property to
the value of an environment variable this way.
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Path to MSI?

2007-10-19 Thread Rad Ricka
Hello,

what's the most effective way to programmatically get the path to where my MSI 
is being run from?

Cheers,

R.-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] HI WIX 3.0 FileShare question

2007-10-19 Thread Krishna Sapkota (Solutions IQ)
This is what I was trying but it didn't work. It creates the physical folder 
named [BLA] in the InstalledDIR and creates the file-share on it. It does not 
create the D:\Share1 folder but creates a folder named [BLA].

Thanks,
-Krishna



 Krishna Sapkota | Software Design Engineer | SolutionsIQ | Technical Services 
 Engineering | [EMAIL PROTECTED] | 425.703.7327
 Tell me how TSE can improve here


-Original Message-
From: Sebastian Brand [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:13 AM
To: Krishna Sapkota (Solutions IQ)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] HI WIX 3.0 FileShare question

I'm not sure if this works, but give it a try:

You can create a new Directory element:

Directory Name=[BLA]
  Component
   FileShare...
.../

and call the msi (using msiexec) with the parameter BLA=D:\Share1

The location of the new Directory may be anywhere as the BLA property
is passed with a full path.


Best regards,
Sebastian Brand

Instyler Software - http://www.instyler.com


On Oct 19, 2007, at 10:04 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi Sebastian,

 Thank you very much for the response.

 I am using following code snippet for creating file-share:

 Directory Id=TARGETDIR Name=SourceDir
 Directory Id=ProgramFilesFolder
   Directory Id=INSTALLLATIONDIR Name=$(var.ProductName)

 Component Id=ProductComponent Guid=7f1d40c6-7366-4b3a-
 b0e0-59aff11ce19e
   CreateFolder/
   .
 /Component

 !-- Creating share folder for storing share info --
 !-- Grant Read permission to IIS_NETWORKSERVICE and --
 !-- Grant write permission to Win32ServiceAccount --

 Directory Name=PUBLICSHARE Id=D_PUBLICSHARE 
   Component Id=C_PUBLICSHARE_1 Guid={GUID} DiskId=1
 CreateFolder/
 util:FileShare Id=S_PUBLICSHARE
 Description=PublicShare Name=PublicShare
   util:FileSharePermission User=Win32ServiceAccount
 GenericRead=yes Read=yes/
   util:FileSharePermission User=IIS_NETWORKSERVICE
 GenericRead=yes Read=yes /
 /util:FileShare
   /Component
 /Directory
   /Directory
 /Directory
   /Directory

 This creates the share folder inside [INSTALLLATIONDIR], while
 taking this share-folder section outside but inside the logical
 Directory (the outmost directory), then it creates the file-share
 in the root directory of the drive where the product is been
 installed.

 But I want to create the file-share in the different drives like D:
 \Share1 or E:\Share2 , (they are passed as parameter (Property) to
 MSI. If the physical directory for the share in the target drive
 does not exist, I want to create it, FYI: they all exists in the
 same machine.)

 I am trying to find out the way to do it using FileShare element of
 WIX 3.0, Can I perform this using the FileShare element? Or I need
 to use some scripting command (i.e. using xcacls.vbs) in a custom
 action.

 I would appreciate any clue.

 Thank you,
 -Krishna

  Krishna Sapkota | Software Design Engineer | SolutionsIQ |
 Technical Services  Engineering | [EMAIL PROTECTED] |
 425.703.7327
  Tell me how TSE can improve here

 -Original Message-
 From: Sebastian Brand [mailto:[EMAIL PROTECTED]
 Sent: Friday, October 19, 2007 12:33 AM
 To: Krishna Sapkota (Solutions IQ)
 Cc: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] HI WIX 3.0 FileShare question

 What does your wix file look like?

 FileShare uses the component's directory. If you want to use
 different drives for the fileshares your Directory structure must
 be correct. How do you get those E:\.. and D:\.. folders on the
 target system?


 Best regards,
 Sebastian Brand

 Instyler Software - http://www.instyler.com


 On Oct 19, 2007, at 6:02 AM, Krishna Sapkota (Solutions IQ) wrote:

 Hi,



 I am trying to create a FileShare using WIX 3.0, how can I give the
 folder path dynamically to create different file share. Look like
 it always creates a folder in the same root. I am trying to do
 something like below



 Want to create \\computer1\Share1 for E:\root1\Share1



 And \\computer1\Share2 for D:\root\Share2



 I appreciate any help,



 Thank you,

 -Krishna





 image001.jpg Krishna Sapkota | Software Design Engineer |
 SolutionsIQ | Technical Services  Engineering | v-
 [EMAIL PROTECTED] | 425.703.7327

  Tell me how TSE can improve here



 image001.jpg
 -
 -
 ---
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a
 browser.
 Download your FREE copy of Splunk now  http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




[WiX-users] FilePath manipulation in WIX

2007-10-19 Thread Nitin Chaudhari
Hi,

 

I can do a registrysearch and obtain a path like : D:\Program
Files\Microsoft Office\OFFICE11\ADDINS\OTKLOADR.DLL

 

Once I have this path I want to split it in directory (D:\Program
Files\Microsoft Office\OFFICE11\ADDINS) and file (OTKLOADR.DLL) and then use
it in directorysearch and filesearch to finally see if the given dll has the
required version.

 

Any idea how to do this.

 

Thanks,

Nitin.


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Path to MSI?

2007-10-19 Thread Richard

In article [EMAIL PROTECTED],
Rad Ricka [EMAIL PROTECTED]  writes:

 what's the most effective way to programmatically get the path to where =
 my MSI is being run from?

What's the goal?

What problem are you trying to solve by getting the path of the MSI?
-- 
The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
  http://www.xmission.com/~legalize/book/download/index.html

Legalize Adulthood! http://blogs.xmission.com/legalize/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users