Re: [WiX-users] Advertised shortcuts and the new world of bundles

2014-11-02 Thread Rob Mensching
With the design you've chosen, you've made advertised shortcuts less functional.

_
 Short replies here. Complete answers over there: http://www.firegiant.com/


-Original Message-
From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] 
Sent: Sunday, November 2, 2014 4:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Advertised shortcuts and the new world of bundles

If I have a single .msi that installs files and an advertised start menu 
shortcut, and some files become damaged or missing, launching the start menu 
shortcut will repair the relevant feature(s) and launch the application anyway.

But let's say I have a Burn bundle with two .msi's, one with required libraries 
and another with the actual application. If I launch the advertised shortcut, 
Windows Installer is unaware of the library MSI.
If files are missing or corrupted, Windows Installer would only repair features 
in the application MSI, it can't repair the bundle, or know that the library 
MSI has to be repaired too.

The same happens if I install advertised features. Features can be installed on 
demand when launched via advertised shortcuts, but that won't install files 
that are part of separate MSIs in the bundle.

So my question is, if I have a bundle, what is the point of advertised 
shortcuts? In what situation are they useful and functional?

--
Nicolás
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Advertised shortcuts and the new world of bundles

2014-11-02 Thread Nicolás Alvarez
If I have a single .msi that installs files and an advertised start
menu shortcut, and some files become damaged or missing, launching the
start menu shortcut will repair the relevant feature(s) and launch the
application anyway.

But let's say I have a Burn bundle with two .msi's, one with required
libraries and another with the actual application. If I launch the
advertised shortcut, Windows Installer is unaware of the library MSI.
If files are missing or corrupted, Windows Installer would only repair
features in the application MSI, it can't repair the bundle, or know
that the library MSI has to be repaired too.

The same happens if I install advertised features. Features can be
installed on demand when launched via advertised shortcuts, but that
won't install files that are part of separate MSIs in the bundle.

So my question is, if I have a bundle, what is the point of advertised
shortcuts? In what situation are they useful and functional?

-- 
Nicolás

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Compression Level

2014-11-02 Thread Phill Hogland
Well I guess my last observation is not correct when I both delete the cabs
folder and the bin and obj folders.  The property in an imported target is
used by msbuild launched on the command line to build a project (without
defining the properties using the /p switch).



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compression-Level-tp7597566p7597657.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Compression Level

2014-11-02 Thread Phill Hogland
I do not think that the files were different, since I did a "debug" build,
and then a "release" build as soon as the debug build was finished (without
any change to the source tree).  Even though the Release build was set to
use high compression, it reused the cab file (when the path is set to a
common location for all configurations) which had been built with no
compression.  If I delete the Cab Cache folder then the cab was rebuilt
using the requested compression.  At least that seems to be what the issue
is.  I have yet to go back through all of my projects and eliminate the
common cache path.

cabs
True

Also I noticed, but did not dig deeper yet, that when I have the above lines
in an 'imported' target file, external to the project file, and when I
delete the cabs folder, then run msbuild on the command line specifying the
project, the cabs folder is not created (probably because I did not
specifically pass in the above using the MSBuild /p switch).  But in VS2013
when the same project is built the cabs folder is created.  I thought I
would do a few more experiments to make sure I understand how to get the
same results whether building via msbuild or vs2013.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Compression-Level-tp7597566p7597656.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to add Active Directory user into SQL server with windows authentication through WIX installer

2014-11-02 Thread Bala
Hi,

 

 

I am new to WIX installer, I am creating installer application to install
the web application

 

In my requirement like Install the application in server having active
directory user account and sql server with windows authentication. I am able
to install the web application, but while trying to connect the SQL database
from the web application it throws error DB permission issue.

 

Please help me to solve the issue.

I think this is due to the active directory user does not exist in SQL
server, I want to know how to add Active directory user in to SQL server
through WIX installer with Windows authentication.

 

 

Thanks

Bala.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] 64bit bootstrapper using wix

2014-11-02 Thread Rob Mensching
Not until someone had a real use case for it. 

_
 Short replies here. Complete answers over there: http://www.firegiant.com/


-Original Message-
From: liorby1 [mailto:k...@walla.co.il] 
Sent: Sunday, November 2, 2014 4:29 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64bit bootstrapper using wix

Are there any plans to have a  64 bit burn?
I need to build an installer that should work on windows core.
thanks in advance,
Lior

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] 64bit bootstrapper using wix

2014-11-02 Thread liorby1
Are there any plans to have a  64 bit burn?
I need to build an installer that should work on windows core.
thanks in advance,
Lior



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/64bit-bootstrapper-using-wix-tp7582851p7597653.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users