Re: [WiX-users] Problem in Getting the path of executable file and scripts in WIX Installer

[supriya]

Hello All,

Thanks for understanding my issue. I have found the solution to my problem.

It was all because of harvesting the solution. I was missing the step so was
not able to run the MSI on machine other then the development.

I have then perform the harvesting  of the Installer and it worked.

If there is any other guy like me then can follow the below link which
explains the proper steps to generate successfully MSI.

http://blog.bartdemeyer.be/2013/10/create-an-installer-for-website-with-wix-part-1/

Thanks

Supriya



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-in-Getting-the-path-of-executable-file-and-scripts-in-WIX-Installer-tp7594628p7596199.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn/bundle EXE - setting property?

[psimms]

Hi Phil,

Thank you for getting back to me,

Yes I have tried doing a registry search then calling that variable within
the InstallCommand for exepackage however it doesn't seem to be able to read
it in that way, even though in the logs I do see the variable being declared
but when the installcommand is executed it is blank where the variable was
suppose to be.

If I hard code a variable it will accept that and works (variable to the
registry search does not work).

Seems a bit of overkill to do a custom action just to set a variable however
I will investigate it.  I am completely new to burn and never done a burn
custom action.  Is it the same process as a standard custom action?

Reg search:-
 

Installcommand:-
  InstallCommand ="/S /D=[INSTALLDIR]" 

Variable hard coded:-
   



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596200.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix39 signing external cabs

[Phill Hogland]

No, I never found a solution to this problem.  I reverted back to using
embedded cab files, which avoided the problem, for now.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix39-signing-external-cabs-tp7595976p7596202.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn/bundle EXE - setting property?

[Phill Hogland]

There is no such thing as a 'Burn custom action' (and it would be overkill if
it existed).  I suggest that you try the built-in functionality of
util:RegistrySearch and using the variable in the Install condition.

If it does not work for you, then post the relevant sections of code and a
verbose log, so that others volunteers can advise you on how to get it to
work.  The pattern of doing a registry search and using the variable in an
InstallCondition is very common and used by many, including the wix source. 
So figure out why it is not working for you.  You can configure in the
registry, verbose logging for MSIs, which also enables verbose logging for
Burn.  Then look in your temp folder for the log.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596201.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Multilingual Bundles

[Tobias S]

Hi all,

Previously I thought Bundles can be designed by creating a multilingual BAL
and bundle that with (a) monolingual english MSI(s). But now I mention
small things that make it inevitable to have MSIs with transforms e.g. for
things like Description + Command localization for File Extension
Registration.

What are the best approaches for MSIs within multilingual bundles?

Regards,
Tobias
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn/bundle EXE - setting property?

[psimms]

I created a dummy basic installer with the same logic that has the issue,
code below and the log file attached.

See the installcommand below were the /D=[SDK_DIR]" should install the
SDK.exe to that location as determined in the registry search.  In line 6 of
the log it declares the SDK_DIR variable however in line 36 of the attached
log it is blank where the variable is supposed to be used.

Am I missing something here?

InstallCommand ="/SUPERS /D=[SDK_DIR]"


Integration_20140804153643.log

  



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596206.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn/bundle EXE - setting property?

[Sean Hall]

In your registry search, change Variable="[SDK_DIR]" to Variable="SDK_DIR".


On Mon, Aug 4, 2014 at 9:52 AM, psimms  wrote:

> I created a dummy basic installer with the same logic that has the issue,
> code below and the log file attached.
>
> See the installcommand below were the /D=[SDK_DIR]" should install the
> SDK.exe to that location as determined in the registry search.  In line 6
> of
> the log it declares the SDK_DIR variable however in line 36 of the attached
> log it is blank where the variable is supposed to be used.
>
> Am I missing something here?
>
> InstallCommand ="/SUPERS /D=[SDK_DIR]"
>
>
> Integration_20140804153643.log
> <
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7596206/Integration_20140804153643.log
> >
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596206.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Can Heat be used more than once in a single MSI project

[Taylor, Duane E.]

Hi All,



I have two MSI projects to a common root directory.  The path to the root 
directory can be selected by the user.  Each project uses Heat to generate the 
files to be deployed.  I also have a burn bootstrapper that chains together the 
two msi packages.



I am looking into implementing a feature tree to allow the user to select 
either or both of the MSI packages.  After reading online it appears that 
capability is not part of Burn and would have to be a custom module.



Is it possible that I could create a single MSI project and encapsulate into 
separate features each of my existing MSI packages?  I am wondering if it is 
possible to use Heat twice in one project.



Any suggestions?



Thanks,

Duane

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[dpflan]

My MSI will install a dll and an exe.

The dll will self-register.
The exe is run by a custom action with a command-line parameter to perform
registration and update the registry.
The exe can take a command-line parameter to unregister itself and remove
references in the registry.

How do I ensure that uninstallation can still succeed - including unregister
via the EXE and unregistering of the DLL - if the user has deleted the
files?

I would like to make an uninstall package as part of the MSI that has a
backup version of the files an merely run uninstall via this package and
remove the files on disk.

What are some good approaches for dealing with this issue?

Best,
Dan



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[Hoover, Jacob]

Don't use self registration, use the registry keys in the MSI Registry table. 
Then it works, and you don't need to worry about a custom action.

-Original Message-
From: dpflan [mailto:dpflann...@gmail.com] 
Sent: Monday, August 04, 2014 12:13 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

My MSI will install a dll and an exe.

The dll will self-register.
The exe is run by a custom action with a command-line parameter to perform 
registration and update the registry.
The exe can take a command-line parameter to unregister itself and remove 
references in the registry.

How do I ensure that uninstallation can still succeed - including unregister 
via the EXE and unregistering of the DLL - if the user has deleted the files?

I would like to make an uninstall package as part of the MSI that has a backup 
version of the files an merely run uninstall via this package and remove the 
files on disk.

What are some good approaches for dealing with this issue?

Best,
Dan



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[dpflan]

This could be a good alternative. Though, I remember I could not use heat to
harvest a 64bit dll.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596211.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[dpflan]

Is there an equivalent tool for harvesting registry info for the 64bit dll?

1. One solution is to not let any files self-register.

Is there another solution?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596212.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[Hoover, Jacob]

If the only thing that is using your DLL is your EXE, use reg-free COM via an 
application manifest and forget about the registry altogether.


-Original Message-
From: dpflan [mailto:dpflann...@gmail.com] 
Sent: Monday, August 04, 2014 12:30 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

Is there an equivalent tool for harvesting registry info for the 64bit dll?

1. One solution is to not let any files self-register.

Is there another solution?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596212.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

[dpflan]

The EXE and DLL are independent.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596214.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to create path using Burn

[Marco Tognacci]

I have a Burn setup exe package and I'd like to make patches to update only a 
few files using the same Burn interface, how can I make this?
Which is the right way for automate this process inside TFS build system?I have 
a build definition that create all the msi packages that are included in the 
Burn bundle and the make the exe burn  setup.In a such way I'd like to create 
patches for this package.
I have read that I can use Torch for making the transform and the using Pyro to 
make the patch, but I don't know hot to mix it with burn.And is there a way for 
using Torch and Pyro using project definition without using calling to command 
line Torch.exe and Pyro.exe?   
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to create path using Burn

[John Cooper]

This is how I make patches.

http://borgsdemons.com/blog/2014/07/11/yet-more-improve-wix-way-patch-project-with-burn-bootstrapper/
 

I currently don't have a product with multiple MSI's, although I am planning to 
"debundle" a multiple feature MSI into multiple MSI's and deploy them with Burn.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com



-Original Message-
From: Marco Tognacci [mailto:mark...@live.it] 
Sent: Monday, August 4, 2014 3:25 PM
To: WiX - users
Subject: [WiX-users] How to create path using Burn

I have a Burn setup exe package and I'd like to make patches to update only a 
few files using the same Burn interface, how can I make this?
Which is the right way for automate this process inside TFS build system?I have 
a build definition that create all the msi packages that are included in the 
Burn bundle and the make the exe burn  setup.In a such way I'd like to create 
patches for this package.
I have read that I can use Torch for making the transform and the using Pyro to 
make the patch, but I don't know hot to mix it with burn.And is there a way for 
using Torch and Pyro using project definition without using calling to command 
line Torch.exe and Pyro.exe?   
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Heat be used more than once in a single MSI project

[Phill Hogland]

>>I am wondering if it is possible to use Heat twice in one project. 

A MSBuild target is only called once.  

In one project I need to harvest files from different source locations.  I
define MSBuild Targets with appropriate properties and in each I call the
HeatDirectory Task (not target).  The targets are chained in a
DependsOnTargets statement so Heat is called probably 20 or more times in
that project.  It works fine.

In another project I called the CopyFile Task multiple times to build a new
source folder tree and then called HeatDirectory once to harvest the whole
tree.

Either approach is possible.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-Heat-be-used-more-than-once-in-a-single-MSI-project-tp7596208p7596217.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Prevent old InstallShield version from installing over WiX

[Mike Schuett]

Hello,

I'm migrating an install from MSI based InstallShield to WiX using the
standard bootstrapper. Installation of the new product version (WiX based)
over older versions (IS MSI based) works fine.

The problem I'm having is the old IS installs do not recognize the newer WiX
installations and I end up with two installations.

Any suggestions would be appreciated.

Thanks,
Mike




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Prevent-old-InstallShield-version-from-installing-over-WiX-tp7596218.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Multilingual Bundles

[Bob Arnson]

On 04-Aug-14 10:43, Tobias S wrote:
> What are the best approaches for MSIs within multilingual bundles?
Keep neutral resources in one package, localized resources in another 
package, one per language (i.e., lang pack).

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


--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users