[WiX-users] SourceDir

2010-08-20 Thread Satyaprakash J
Hi
I run the following command to generate the attached .wxs file.

heat dir 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug -gg 
-sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup

In the directory.wxs file the Source attribute of File element 
is set to SourceDir\FileName. See attached wxs file.

I would like to know how this SourceDir can be replaced with 
the actual path 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug
 when running heat.

Thanks
Satyaprakash J



--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] SourceDir

2010-08-20 Thread Satyaprakash J
Hi

 I run the following command to generate the attached .wxs file.



 heat dir 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug
 -gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup



 In the directory.wxs file the Source attribute of File element is set to 
SourceDir\FileName. See attached wxs file.



 I would like to know how this SourceDir can be replaced with the actual 
path 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3cfile:\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3e
 when running heat.



Thanks

Satyaprakash J

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] SourceDir

2010-08-20 Thread Kyle McClellan
Set the PreprocessorVariable. It's an optional string parameter that will 
substitute SourceDir for another variable name (ex: var.Dir).

-Original Message-
From: Satyaprakash J [mailto:sat...@smartek21.com] 
Sent: Friday, August 20, 2010 2:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SourceDir

Hi

 I run the following command to generate the attached .wxs file.



 heat dir 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug
 -gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup



 In the directory.wxs file the Source attribute of File element is set to 
SourceDir\FileName. See attached wxs file.



 I would like to know how this SourceDir can be replaced with the actual 
path 
\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debugfile:///\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3cfile:\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug%3e
 when running heat.



Thanks

Satyaprakash J


--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Sourcedir

2007-12-14 Thread Paul McCloskey
Thanks for the reply. Since we're using WIX for MSI authoring and
examining a bootstrapper architectchure, we've been experimenting with
Office 2007. It's the biggest WIX authored bootstrapper driven install
we could think of. Specifically I'm interested in exactly how they can
through Group Policy assign a single MSI to a machine which then appears
to copy or install the installation media to the client machine, and
finishes by launching the setup.exe on the local machine. Getting a
handle on how Microsoft is doing this will greatly help us offer Group
Policy deployment scenarios to our customers.

Probably way too much detail, but to get back to the original question
of the SourceDir property, I've only been able to reliably detect Group
Policy deployment and launch the custom action to trigger the
bootstrapper which never actually launches anything because I haven't
found a reliable way to find where the network MSI is running from. 

Any ideas are welcome.



-Original Message-
From: Richard [mailto:[EMAIL PROTECTED] On Behalf Of
Richard
Sent: Friday, December 14, 2007 12:16 PM
To: Paul McCloskey
Subject: Re: [WiX-users] Sourcedir 


In article
[EMAIL PROTECTED],
Paul McCloskey [EMAIL PROTECTED]  writes:

 We're exploring using a bootstrapper type install architecture for our
 suite of products.

If there's no rush, I would wait for the next release of Windows
Installer which will integrate bootstrappers for just the GPO
deployment scenario you're talking about.

Otherwise, the sequence of things will always be wrong because the
bootstrapper should run before your product MSI runs.
-- 
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/

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Sourcedir

2007-12-13 Thread Paul McCloskey
Hello,

 

I'm trying to find a reliable way to get the path to the running MSI.
Once I have the path, I'd like to spawn an executable that is relative
to the MSI in a custom action. I'd like to try and do this as early as
possible in the execute sequence. I've tried using SOURCEDIR to mixed
results, and I've tried using C++ functions like GetModuleFileName, and
I've tried using the CURRENTDIRECTORY property. What is complicating my
approach is that this has to happen during Group Policy assignment so
most of these functions return C:\Windows\system32, which is where the
main msiexec is running from. 

 

Any ideas?

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Sourcedir

2007-12-13 Thread Richard

In article [EMAIL PROTECTED],
Paul McCloskey [EMAIL PROTECTED]  writes:

 I'm trying to find a reliable way to get the path to the running MSI.
 Once I have the path, I'd like to spawn an executable that is relative
 to the MSI in a custom action.

Why?  What is this executable supposed to do?
-- 
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/

-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users