Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??

[James]

Hi, 

Have you found a solution for this? Are there any pointers for this ? 

I have exactly same issue. 

-James 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598436.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??

[James]

On Fri, 5/12/14, James [via Windows Installer XML (WiX) toolset] 
 wrote:

 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
 To: "James" 
 Date: Friday, 5 December, 2014, 9:10 AM
 
 
 
Hi, 
 
 
 Have you found a solution for this? Are there any pointers
 for this ? 
 
 
 I have exactly same issue. 
 
 
 -James 
 




 

 


If you reply to this email,
 your message will be added to the discussion below:

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598436.html



To unsubscribe from Deploying multiple cultures using
 Burn/MSI(s). Wix 3.9 issue??, click
 here.
 
NAML





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598437.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??

[James]

Hi,

Thank you for your quick response. I didn't get this quite clearly. Can you 
please help?

Attached is my bundle.wxs file. There are few thing I am not very sure how to 
do. Some background before the queries.

The bundle.wxs pacages 3 MSI's. Prerequisite(1), ResourceFolder(2) and 
Final_SF1(3). They are to be called in sequence I mentioned. The only MSI which 
has GUI and is localized is Final_SF1. This localized MSI's are available in 
the respective folders 
(SourceFile="..\Final_SF1\bin\$(var.Platform)\$(var.Configuration)\cs-CZ\Final_SF1.msi")
 from my build script in respective language folders. I have created fragments 
as mentioned in earlier reply for few languages.

Now the issues.
1. How does I fit these localized MSI's into the sequence of execution?
2. How the bundle knows (or rather I tell bundle) which langaueg Final_SF1 MSI 
is to be called/executed?
3. And the current code fails to build saying "error CNDL0005: The Chain 
element contains an unexpected child element 'PackageGroup'"

Am I missing something obvious ? What changes I need to do in my bundle.wxs.

Regards,
James
  From: Phill Hogland [via Windows Installer XML (WiX) toolset] 

 To: James  
 Sent: Friday, 5 December 2014, 11:21
 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
   
 Based on input in this thread I concluded that using embedded transforms would 
not work in a Burn driven scenario reliably.  At the time I had difficulty 
understanding how to allow the packages to be created with multiple cultures in 
separate output folders and then pull those back into the bundle.  I posted 
this question and got good advice.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-td7596991.html

When a package builds, it uses an external cab file, and builds the output of 
that package project to separate culture named output folders (default behavior 
of wix).

Then in the bundle's I rename the package like this

  
    
      
      
    
  
  
    
      
    
  
  
    
      
    
  

The packages are not compressed so the renamed msi and related external cab 
file end up in a sub folder relative to the bundle named App.  The tree is much 
larger than when transforms are used, but since we stage to a server and the 
customer only gets the small bootstrapper exe (and the packages that their 
configuration needs), this seems to work for use.  Others in this list 
mentioned using the transforms external to the msi, but I can't speak to that 
process.
 
 
   If you reply to this email, your message will be added to the discussion 
below: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598452.html
 

  To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 
issue??, click here.
 NAML 



Bundle.wxs (10K) 
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/attachment/7598503/0/Bundle.wxs>




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598503.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??

[James]

This worked well. Thank you.James

  From: Phill Hogland [via Windows Installer XML (WiX) toolset] 

 To: James  
 Sent: Tuesday, 9 December 2014, 14:30
 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
   
 Define a variable in your bundle, detect the culture in your BA, and set this 
variable (or use one of the Burn built-in language variables).  You could take 
different approaches here, but the result is that you use the variable in your 
InstallCondition to determine which of the msi packages will be installed (or 
use the information in the OnPlanPackageBegin handler to select whether a 
particular package will be installed or not.)

In the example you would replace 'App' with 'Final_SF1', I assume.
When you add the following to your chain, all of the PackageGroupRef related to 
specific cultures, in the example, are included in your chain in the sequence 
that you authored them.

Chain
...Prerequisites
...other stuff
PackageGroupRef Id='Final_SF1'

Then you need to author the other parameters of the MsiPackage elements so that 
burn can find the msi packages and you have InstallConditions that specify 
whether the package is installed.

I use the following but you might have different requirements.

I set the var in my ba to an lcid.
InstallCondition='MyNumericVar=1031'  (true when installing de-DE, otherwise 
not installed)
 
 
   If you reply to this email, your message will be added to the discussion 
below: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598508.html
 

  To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 
issue??, click here.
 NAML 





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598625.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Copying INI file to target folder which is not part of installer

[James]

Hi,
I need to copy MyConfig.INI file to target folder via my Wix Installer. The 
user will have two files with him/her.The installer (bundle exe which includes 
my MSI) and this MyConfig.INI file. The name of this file will be fixed. But 
this file will not be available at build time and it will come to user from 
different source.

At the moment I am using custom action to copy this file manually to target 
folder. Is there any simple way (other than custom action) using which the 
installer can detect presence of this file and copy this to target installation 
folder?
Please note, the installer exe and this file will be at same location and this 
file is NOT available in build system so the installer only has name of this 
file.
Thanks in advance.

-James
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Removing bundle after installing MSI's

[James McConville]

Hello all,

Need to find out if this is possible or if I've completely missed the point of 
Bundles.

Is it possible to remove all traces of the bundle after installation, not just 
hide it.

Essentially I want to use the bundle purely as a delivery method for the app 
and its dependent apps (which I want to leave alone if I remove the msi).

Is it possible to do this or should I be looking at another solution?

Thanks for your help!
James.





--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing .NET FRAMEWORK 4.5.1

[James Welle]

Hi Michal,

I believe this is not possible yet.

There is an open issue to make this work in v3.8.

http://wixtoolset.org/issues/4180/

James

-Original Message-
From: michalc777 [mailto:michalc...@hotmail.com] 
Sent: Sunday, November 24, 2013 7:26 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing .NET FRAMEWORK 4.5.1

Hi, 

I'm trying to write a bootstrapper that will install .net 4.5.1 as a 
prerequisite to my app installation. 
I'm using wix toolset v3.7
I have read some tutorials and try to perform this using: 

But it doesn't compile. 
The error I get is: 
Unresolved reference to symbol 'ChainPackageGroup:NetFx451Web' 

You can see that this is the correct package group id as described here: 
http://wixtoolset.org/documentation/manual/v3/customactions/wixnetfxextension.html

If any of you know how to solve this it would be great :) 

Thanks. 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing-NET-FRAMEWORK-4-5-1-tp7590893.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Shape the Mobile Experience: Free Subscription Software experts and developers: 
Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Encrypt and store the SQL sa password in the windows registry

[James Johnston]

Isn't storing the administrator password for a server in the registry a
terrible idea?  This is setting off all kinds of alarm bells in my mind...
Even if you "encrypt" it, I would think it would still be easy enough to
recover the plaintext just by finding the key in the MSI file and then
decrypting.  I don't see how it offers any real security beyond shielding
from casual prying eyes.  I would think an installer that does this without
telling could easily trap the unwary system administrator who wants to run a
tight ship...

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, February 16, 2011 15:35
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Encrypt and store the SQL sa password in the
windows registry

Not today but it would be a great custom action to have.

On Tue, Feb 15, 2011 at 2:40 PM, Thai-Hoa Nguyen
wrote:

>
>
> Hello
>
> I'm currently storing the SQL sa password so the database can be 
> uninstalled later.
>
>  Value='[SQLPASSWORD]' Type='string' />
>
>
>   Id='SqlPwdReg' Key='SOFTWARE\xyz\abc' Name='SQLPwd'
> Root='HKLM' Type='raw'/>
> 
>
> Is there a quick and easy way to encrypt and decypt the password in Wix?
>
> Thank you.
>
> --
>  The ultimate all-in-one performance toolkit: Intel(R) 
> Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
virtually, Rob Mensching - http://RobMensching.com LLC

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Encrypt and store the SQL sa password in the windows registry

[James Johnston]

I think that would depend on whether the SQL Server is located on the same 
physical computer as the software in question that wants to store an account 
password.  If it's the same computer then you are correct - in fact that 
thought had already crossed my mind.  The one remaining issue I can think of is 
that the user's password is still compromised in a way that it wouldn't be 
otherwise.  Windows and I'm sure SQL Server uses one-way hash functions so 
that, even if the "password file" is stolen, significant effort must be 
expended to determine what the passwords are if the quality of the passwords is 
good.  If the administrator is using the same password for everything then 
there could be a problem: it might allow an attacker to further infiltrate the 
network.  If the password was only used for that one account then it's a 
non-issue.

I think that the "save password" concept really gets scary if the SQL Server is 
located on a different computer.  For example, suppose the app uses the "sa" 
password to create the database on a remote server.  But for security reasons 
the app should not use the "sa" account for day-to-day use, and so the "sa" 
password is never used again except for uninstall and is saved in the registry 
somehow as has been discussed.  In that case, if the client computer is 
compromised, this "saved password" registry key.  I.e. the attacker pulls the 
hard drive from the client computer, reads the key associated with the SYSTEM 
context somehow, and then decrypts the password.  Now he's gained access to the 
server that he did not previously have. 

-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: Wednesday, February 16, 2011 18:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Encrypt and store the SQL sa password in the windows 
registry

That all depends on what key you use to encrypt the data. If the key is 
associated with the SYSTEM context then only the SYSTEM context will be able to 
decrypt the data. If an attacker already has access to the SYSTEM context then 
it's already Game Over.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail

> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: Wednesday, February 16, 2011 8:19 AM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Encrypt and store the SQL sa password in the 
> windows registry
> 
> Isn't storing the administrator password for a server in the registry 
> a terrible idea?  This is setting off all kinds of alarm bells in my mind...
> Even if you "encrypt" it, I would think it would still be easy enough 
> to recover the plaintext just by finding the key in the MSI file and 
> then decrypting.  I don't see how it offers any real security beyond 
> shielding from casual prying eyes.  I would think an installer that 
> does this without telling could easily trap the unwary system administrator 
> who wants to run a tight ship...
> 
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, February 16, 2011 15:35
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Encrypt and store the SQL sa password in the 
> windows registry
> 
> Not today but it would be a great custom action to have.
> 
> On Tue, Feb 15, 2011 at 2:40 PM, Thai-Hoa Nguyen
> wrote:
> 
> >
> >
> > Hello
> >
> > I'm currently storing the SQL sa password so the database can be 
> > uninstalled later.
> >
> >  > Value='[SQLPASSWORD]' Type='string' />
> >
> >
> >   > Id='SqlPwdReg' Key='SOFTWARE\xyz\abc' Name='SQLPwd'
> > Root='HKLM' Type='raw'/>
> > 
> >
> > Is there a quick and easy way to encrypt and decypt the password in Wix?
> >
> > Thank you.
> >
> > 
> > --
> >  The ultimate all-in-one performance toolkit: Intel(R) 
> > Parallel Studio XE:
> > Pinpoint memory and threading errors before they happen.
> > Find and fix more than 250 security defects in the development cycle.
> > Locate bottlenecks in serial and parallel code that limit performance.
> > http://p.sf.net/sfu/intel-dev2devfeb
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://

Re: [WiX-users] Dynamically set WixVariable WixUILicenseRtf

[James Johnston]

Oh wow...  Right now we just change it in our build script when calling
light:

light  -dWixUILicenseRtf=SupportFiles/License_${language}.rtf


Which is also unnecessarily kludgy; that information really should be in the
localization file but at the time I didn't figure out how (that blog entry
was written after I wrote the setup project...).

Your solution is better except that it involves modifying WiX source code.
Any chance this might be added to a future version of WiX?  This common task
seems needlessly complicated.  Maybe the change would break compatibility,
but on the other hand the status quo of modifying WiX source code doesn't
seem any better to me!

Unless there is a better way that neither of us know about??

James

-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com] 
Sent: Friday, February 18, 2011 15:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Dynamically set WixVariable WixUILicenseRtf

Ok, knew there exists an english speaking tutorial:
http://weblogs.sqlteam.com/mladenp/archive/2010/04/15/WiX-3-Tutorial-Custom-
EULA-License-and-MSI-localization.aspx

2011/2/18 Tobias S :
> You have to overwrite the default WiX dialog e.g. in WixUI_InstallDir 
> with a modified LicenseAgreementDlg.wxs:
>
> 1.) get the WiX Source code
>
>
> 2.) from there add copies from
> src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs + 
> LicenseAgreementDlg.wxs to your solution renamed as 
> MyLicenseAgreementDlg.wxs + MyWixUI_InstallDir.wxs
>
>
> 3.) MyLicenseAgreementDlg.wxs
> change lines
>  Title="!(loc.LicenseAgreementDlg_Title)">
> -->
>  Title="!(loc.LicenseAgreementDlg_Title)">
>
>
>
>  Width="330" Height="140" Sunken="yes" TabSkip="no">
>    
> 
>
> -->
>
>  Width="330" Height="140" Sunken="yes" TabSkip="no">
>    
>
>
> 4.) WixUI_InstallDir.wxs
> change line
>  
> -->
>  
>
> Replace all four occurences of LicenseAgreementDlg with
MyLicenseAgreementDlg
>
>
> 5.) Change in the main wxs the reference to the modified
MyWixUI_InstallDir
> 
> -->
> 
>
>
> 6.) Add for every language a localization file with at least the
> following content:
> 
>  xmlns="http://schemas.microsoft.com/wix/2006/localization";>
>  1033
>  Languages\EnglishLicenseAgreement.rtf
> 
>
>
> Here LicenseRtf is the location of the localized License Agreement
>
>
> Regards
> Tobias
>
>
> 2011/2/18 Michael Tissington :
>> How can I dynamically set the value of WixUILicenseRtf?
>>
>> I have tried 
>>
>> What I'm trying to do is for each localization to use a different
license.rtf.
>>
>>
>>

--
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] write to IniFile

[James Johnston]

http://msdn.microsoft.com/en-us/library/aa369282(VS.85).aspx

"DirProperty
Name of a property having a value that resolves to the full path of the
folder containing the .ini file. The property can be the name of a directory
in the Directory table, a property set by the AppSearch table, or any other
property that represents a full path. If this field is left blank, the .ini
file is created in the folder having the full path specified by the
WindowsFolder property."

Unless I'm missing something obvious, shouldn't it be as simple as
specifying a value for DirProperty?  We do this from WiX in our product with
no problems so far...  don't really see why a custom action would be
needed...

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Monday, February 21, 2011 15:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] write to IniFile

Yep, annoying, eh? The MSI SDK documents that behavior. Want to contribute a
custom action that does better?

On Mon, Feb 21, 2011 at 1:04 AM, Michael Tissington <
michael_tissing...@ciqual.com> wrote:

> I'm trying to write to an iniFile.
>
> How do I tell it which folder the file is in?
> Currently it seems to insist that it is in the \Windows folder.
>
>
>
> --
>  The ultimate all-in-one performance toolkit: Intel(R) 
> Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


--
virtually, Rob Mensching - http://RobMensching.com LLC

--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with RemoveExistingProducts action

[James Johnston]

In that case you have to be following component rules.  See
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/  Also with your
placement, if the old version fails to uninstall then the user will have
both old & new versions installed - something to keep in mind.

Try putting it after InstallInitialize.  The old version will be uninstalled
first before anything new is installed.  If the install of the new product
fails then the rollback will restore the old version.

If you use DIFxApp for driver installs then it needs to be put between
InstallValidate and InstallInitialize due to a bug in DIFxApp.  In that case
a failed install of the new product but after the successful uninstall of
the old product will leave the computer with no product installed at all.  I
think that must be a good place to put it if there are buggy custom actions
and component rules aren't being well-followed.

James

-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com] 
Sent: Tuesday, February 22, 2011 06:04
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Problem with RemoveExistingProducts action

I have upgrade scenario for my system from 2.0 version to 2.1 version. I
have file for example aaa.xml in 2.1 version and no such file in 2.0
version. It lies in independent component i feature Afeature (it was in 2.0
also). During install there are no problems: file installs to the right
location. But during upgrade from 2.0 version it copies and then deleted.
It seems that RemoveExistingProducts deletes it during uninstall of older
2.0 product. It planned after InstallFinalize action (the most right place
as I understand).
Due to the log Installer unpublish features and the delete files...
MSI (s) (DC:B8) [11:54:05:148]: Executing op:
FileRemove(,FileName=aaa.xml,,ComponentId={369A88EA-F2DD-4124-9560-13E5694E2
EEB})
RemoveFiles: File: aaa.xml, folder: C:\Mag\

I dont understand - what happened? Why it deletes files? May be I didnt
configured installer correctly? But how?

--
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights. 
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk 
Collect, index and harness all the fast moving IT data generated by your 
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights. 
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with RemoveExistingProducts action

[James Johnston]

I would actually consider that desirable behavior in my product, since
version 2.1 was designed and tested with bbb.dll version 1.0 - not version
1.5.  What's happening is the removal of product 2.0 causes the reference
count on component bbb.dll to go to zero, and so MSI deletes the file.  Then
the new version installs a fresh copy of bbb.dll version 1.0.

If you want to retain the behavior you describe, then you would need to test
product version 2.1 with both bbb.dll versions 1.5 and 1.0.  Version 1.5
would occur when the user upgrades and version 1.0 would occur on a clean
install of product 2.1.  If at all possible, I like to just to put the DLLs
alongside your application in the application directory, and not put them in
a shared place like the Windows System32 directory - this is easier since
you only have to test one configuration instead of two.  This tends to be a
recommended way of doing things to avoid "DLL Hell".

That said, sometimes 3rd-party components have prescribed ways of
installation and there's nothing you can do about it.  And maybe there are
some reasons for keeping the bbb.dll file around.  For example, you might
have bbb.dll as a 3rd-party component in the SYSTEM32 directory.  In that
case I would set the "Permanent" and "SharedDllRefCount" attributes both to
"yes".  Permanent will add an extra reference to the component during
installation, so that it doesn't get deleted on uninstall (or therefore an
upgrade).  SharedDllRefCount deals with maintaining a similar, older-style
reference counting scheme for non-Windows Installer installers so that some
other non-MSI installer doesn't wipe your DLL from underneath you.

James 

-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com] 
Sent: Friday, February 25, 2011 04:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem with RemoveExistingProducts action

It seems that I dont break component rules... I just add new component into
existing feature and trying to upgrade.
Besides I put it after InstallInitialize, but now take another problem. If
some of dlls will have lower version - it deleted during upgrade.
If product version 2.0 have bbb.dll version 1.5, and product version 2.1
have dll version 1.0 - it just erase it during upgrade!
As I understand it must leave bbb.dll version 1.5...


On Tue, Feb 22, 2011 at 9:13 PM, James Johnston
wrote:

> In that case you have to be following component rules.  See 
> http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/  Also with 
> your placement, if the old version fails to uninstall then the user 
> will have both old & new versions installed - something to keep in mind.
>
> Try putting it after InstallInitialize.  The old version will be 
> uninstalled first before anything new is installed.  If the install of 
> the new product fails then the rollback will restore the old version.
>
> If you use DIFxApp for driver installs then it needs to be put between 
> InstallValidate and InstallInitialize due to a bug in DIFxApp.  In 
> that case a failed install of the new product but after the successful 
> uninstall of the old product will leave the computer with no product 
> installed at all.
>  I
> think that must be a good place to put it if there are buggy custom 
> actions and component rules aren't being well-followed.
>
> James
>
> -Original Message-
> From: Igor Lemsky [mailto:igor.lem...@gmail.com]
> Sent: Tuesday, February 22, 2011 06:04
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Problem with RemoveExistingProducts action
>
> I have upgrade scenario for my system from 2.0 version to 2.1 version. 
> I have file for example aaa.xml in 2.1 version and no such file in 2.0 
> version. It lies in independent component i feature Afeature (it was 
> in 2.0 also). During install there are no problems: file installs to 
> the right location. But during upgrade from 2.0 version it copies and then
deleted.
> It seems that RemoveExistingProducts deletes it during uninstall of 
> older
> 2.0 product. It planned after InstallFinalize action (the most right 
> place as I understand).
> Due to the log Installer unpublish features and the delete files...
> MSI (s) (DC:B8) [11:54:05:148]: Executing op:
>
> FileRemove(,FileName=aaa.xml,,ComponentId={369A88EA-F2DD-4124-9560-13E
> 5694E2
> EEB})
> RemoveFiles: File: aaa.xml, folder: C:\Mag\
>
> I dont understand - what happened? Why it deletes files? May be I 
> didnt configured installer correctly? But how?
>
> --
> --
> --
> Index, Search & Analyze Logs and other IT data in Real-Time with 
> Splunk Collect, index and harness all the fast moving IT

Re: [WiX-users] Windows 7 MSI privileges

[James Johnston]

A list of reasons why not to use selfreg:

http://msdn.microsoft.com/en-us/library/aa371608(VS.85).aspx

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, March 17, 2011 10:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Windows 7 MSI privileges

If you want to do "what is right" you could start by not using
self-registration.

Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-
From: The Eligible Bachelors [mailto:theeligiblebachel...@yahoo.com]
Sent: 16 March 2011 13:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Windows 7 MSI privileges

Great. I added Execute="deferred" and Impersonate="no" to my custom actions
and it seemed to fix the problem.

I certainly dont want to go against UAC. I want to do what is right,
whatever that may be, so thanks for the help.

> You need Execute="deferred" custom actions with Impersonate="no". This 
> will allow your custom actions, and subsequent child processes that 
> they create, to inherit the local system privileges of the Windows 
> Installer service.


  


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit for your
organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit for your
organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] 32-Bit < > 64-Bit

[James Robertson]

Hi,

I have an existing installer for a 32-bit application that has been working 
fine for the last year or so.  I am now looking at adding a second installer 
(users will download the 32-bit or 64-bit installer, I'm not planning on having 
a single installer decide which version to install) based on the same script 
that can install a 64-bit version of my application.  I have something that 
almost works, but am stuck on a few things.

The current 32-bit installer drops executable files in Program Files (x86) and 
some common data files in ProgramData.  These folders are cleaned up as part of 
the uninstall procedure as long as they're empty (new files can be added by the 
user to the ProgramData folder, and these will remain across upgrades).  The 
new 64-bit installer is supposed to drop executable files in Program Files and 
the same data files in Program Data.

The existing installer always uninstalls any previous version before installing 
the new one (so users can downgrade if I screw up) and I am trying to make the 
64-bit version function in the same way.  Ideally the installer will treat any 
existing install 32-bit or 64-bit in the same say regardless of their actual 
install paths, I.e., providing the version number is different, the previously 
installed version will be uninstalled before the new version is installed.

>From what I can see, installing and uninstalling a 64-bit version on a clean 
>machine works.  I am going to go one step further and assume that upgrading 
>64-bit to 64-bit also works.

The problems I have are as follows:

1) When I install the 64-bit version when a 32-bit installation is already 
present, the 32-bit version isn't uninstalled.  So while the 64-bit version is 
installed in Program Files there is no shortcut to it, nor is there any way to 
uninstall it (the 32-bit version is still listed in Programs and Features).

2) When I install the 32-bit version when a 64-bit installation is already 
present, the 64-bit version is not correctly removed, but the start menu 
shortcut and uninstall link in Programs and Features now reference the 32-bit 
version.


So, how is this scenario supposed to be implemented?  Are there any decent 
tutorials or references on how to implement this upgrade scenario correctly?

The current installer script as it stands can be viewed here:  
http://www.osodata.com/stuff/Product.wxs


James

--
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Why are we using a mailing list vs forum?

[James Robertson]

I guess you could just open a gmail (or whatever) account and subscribe that to 
this list instead of your office email account.


john.bu...@telvent.com wrote:
> Heh, well I guess.  I get annoyed with all the new mail alerts at work. 
> They make us use Lotus Notes, which doesn't easily allow me to filter what 
> emails show as un-read or cause alerts.  And with limited mailbox space 
> (ya, we're awesome) it's a bit of a pain to stay subscribed all the time.
> 
> There isn't a web interface; It's just an archive.  So no posting or 
> un-read markers.  I think both ways would be compatible (web forum 
> interface and mailing list interface).  That'd be kind of neat.
> 
> - John
> 
> 
>  
> Jeremy Farrell
> 05/18/2011 12:47 PM
> Por favor, responda a "General discussion for Windows Installer XML 
> toolset." 
> 
> Send To: 
> 
> General discussion for Windows Installer XML toolset. 
> 
> cc: 
> 
> Subject: 
> Re: [WiX-users] Why are we using a mailing list vs forum?
> 
> 
>> From: john.bu...@telvent.com [mailto:john.bu...@telvent.com] 
>> Subject: [WiX-users] Why are we using a mailing list vs forum?
>>
>> Just curious.
> 
> Because mailing lists are easier and far more convenient to use.
> 
>> I find forums easier to use. :o)  ...
> 
> All down to personal preference. I believe there are web-based interfaces 
> to this list available.
> --
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its 
> next-generation tools to help Windows* and Linux* C/C++ and Fortran 
> developers boost performance applications - including clusters. 
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its 
> next-generation tools to help Windows* and Linux* C/C++ and Fortran 
> developers boost performance applications - including clusters. 
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 

--
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFxApp does not properly rollback to the old driverwhen doing a major upgrade

[James Johnston]

t products does not work.  It's another example
of not seeing the big picture and refusing to do anything about it when
customers try to point this out.  It's very frustrating to deal with.
(Heck... if one of those two products was open source, I would have
seriously considered fixing it and submitting a patch...)

James 

-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com] 
Sent: Wednesday, April 27, 2011 08:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] DIFxApp does not properly rollback to the old
driverwhen doing a major upgrade

I emailed difxt...@microsoft.com and received this response.
"AFAIK, Difx doesn't do anything to explicitly support
RemoveExistingProducts.  The scenario described on that page would require
it to rollback a partial install of a new driver and the previous uninstall
of the old driver.  The limited functionality in the rollback mechanism of
DIFx does not support that."

So it looks like there isn't going to be a fix for this.

Rob

On 11/03/2011 14:00, Rob Hamflett wrote:
> I appear to be looking at the same problem.  I was able to reproduce 
> it by hitting 'cancel' near the end of an uninstall and letting it 
> rollback.  After that uninstallation failed.  Performing a repair 
> fixed things.  Did you email the difx team at the email address Quinton
suggested, and if so, did you ever hear anything back.
>
> Thanks,
> Rob
>
> On 10/12/2010 20:37, James Johnston wrote:
>> Seeing as how this seems to be a fundamental problem with DIFxApp not 
>> handling all the upgrade possibilities well, I was curious to see how 
>> other products do things and so I ripped apart some MSIs in Orca.  I 
>> was looking to see if DIFxApp was set up the same way (CustomAction 
>> table).  I also inspected the placement of the RemoveExistingProducts 
>> action since after my previous e-mail I believe that this plays a 
>> critical role in whether this corrupted system state may occur.  
>> Since I haven't seen any other indication or documentation on the 
>> Internet (a Google search for RemoveExistingProducts and DIFxApp 
>> reveals little), I thought it would be useful to report my findings 
>> so others can see what some commercial software is doing.  My
>> findings:
>>
>> All products using DIFxApp place MsiProcessDrivers and 
>> MsiCleanupOnSuccess actions in the normal places.  CustomAction types 
>> are always the same.  I identified the program used to compile the 
>> MSI by looking at the self-named custom actions each install tool 
>> tends to create (e.g. InstallShield has its own DLL with tons of custom
actions).
>>
>> Refer to
>> http://jpassing.com/2007/06/16/where-to-place-removeexistingproducts-
>> in-a-ma jor-msi-upgrade/ to better understand the placement of 
>> RemoveExistingProducts action.  Examining this table leads me to 
>> believe that placement between InstallInitialize and InstallFinalize 
>> is the best place, since a canceled setup will always leave the old 
>> version on the computer, no matter what.  But this doesn't seem to 
>> work with DIFxApp due to its bug, as previously noted.
>>
>> My product (with the rollback problem):  Compiled with WiX and uses
DIFxApp.
>> RemoveExistingProducts is placed after InstallInitialize.  According 
>> to the previous link, a failure at any time (uninstall or reinstall) 
>> results in only the old version remaining: leaving system state 
>> exactly as it was found.  Unfortunately, as previously noted, a bug 
>> in DIFxApp prevents this from happening.
>>
>> Apple Mobile Device Support (included with iTunes; presumably their 
>> iPod drivers, etc.).  Compiled with WiX and uses DIFxApp.  
>> RemoveExistingProducts is placed after InstallFinalize.  Probably the 
>> DIFxApp bug is not a problem here, because the new version is 
>> installed before the old version is uninstalled.  An error in the new 
>> version setup (from DIFx or other source) would still leave the old
version and its drivers untouched.  An error in
>> the old version uninstall would leave the new version&   its drivers
>> untouched.  According to the table at the above link, the pitfall is 
>> that if the uninstall fails, then BOTH versions of the product remain 
>> installed on the computer.  This seems like a very inconsistent, 
>> illogical state to be in; I can imagine that there could be some 
>> issues with a lot of products (including mine) if this were to 
>> happen.  (Perhaps an MSI expert can convince me otherwise?  
>> Otherwise, I wonder if Apple's software can get itself in a bad way 
>> if I click Cancel at just the right moment.)
>>

[WiX-users] CAQuietExec & Custom Action DLL excute's out of order

[James Constable]

I am using WiX version 3.5.2519.0
If you have a Custom Action DLL and a CAQuietExec Custom Action that 
needs other Windows Installer properties; set them to execute one after 
the other, they do not.The CAQuietExec Custom Action that needs other 
Windows Installer properties executes late in the install process, does 
not execute in the order specified. Followed: 
http://wix.sourceforge.net/manual-wix3/qtexec.htm 



.
.
.





This is the type Custom Action (above) that does not execute in the order I 
specified
using the 'After=' attribute.
I have even made a simple WXS file, same thing happens, in part:
 
 

  

  

  
  

  
  

..
..
..
  
    

    
    
    
    
  

The Custom Action DLL is a shell that just logs a message.

Tried changing deferred to immediate and vica versa for the 'Execute=' 
attribute, no difference.

How can
 I make these Custom Actions actually execute in order?

Thanks,

James
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Registry permissions are not inherited

[James Johnston]

Hi,

I'm trying to create some default registry keys for a component in
HKEY_LOCAL_MACHINE that all users should have full access to.  Here's what
I've got so far:














The keys I would like created:

   * HKLM\SOFTWARE\MyCompany: should have default ACL that users cannot
write to (inherit from parent)
   * HKLM\SOFTWARE\MyCompany\MyFile: all users should have read/write access
to this key
   * HKLM\SOFTWARE\MyCompany\MyFile\MySubKey: all users should have
read/write access to this key (inherit from parent)

Unfortunately, the last key seems to be created with an ACL that only allows
administrators to write to the key (same ACL as for the main "SOFTWARE"
key).  Intuitively I would think that the RegistryKey underneath the key
granting everyone access would also grant everyone access.  But that seems
not to be the case. 

Most puzzling is that examining "MySubKey" in the registry editor shows that
the "Include inheritable permissions from this object's parent" is checked.
And creating new keys under "MyFile" key in registry editor works just fine
when running as a user - so the permissions are inherited.  Looking at the
ACL entry for "Everyone" on "MyFile" key says that the entry applies to
"this key and subkeys" so again, I'm not sure why it isn't working.

What do I need to do to achieve my goal of having the "Everyone" entry
propagate to the subkeys created by MSI - as outlined in my list of desired
ACLs?  I realize I could probably add duplicate "Permission" elements to the
registry values being created.  But that doesn't sound very ideal; it seems
like there must be a better way!

Best regards,

James Johnston


--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registry permissions are not inherited

[James Johnston]

I replaced "Permission" with "util:PermissionEx" in the sample below.
Unfortunately, ordinary users are still not allowed to write to MySubKey.
An examination of the permissions in Registry Editor shows that entries were
added to the existing ACL for "MyFile".  (i.e. the existing entries were not
stepped on like the old "Permission" element did - a good thing).  But they
were set to only apply to the current key, and not to subkeys - no
inheritance.

An examination of the custom action code in "secureobj.cpp" shows
"ea.grfInheritance = NO_INHERITANCE" if the object is not a
folder/directory.  Now this is with WiX 3.0 sources but I searched the
tracker and apparently somebody else reported the same issue last year with
WiX 3.5 and it hasn't been looked at yet:

http://sourceforge.net/tracker/index.php?func=detail&aid=3029343&group_id=10
5970&atid=642717
Another similar ticket:
https://sourceforge.net/tracker/index.php?func=detail&aid=2612975&group_id=1
05970&atid=642717
And one more:
https://sourceforge.net/tracker/index.php?func=detail&aid=1241592&group_id=1
05970&atid=642717
And finally:
https://sourceforge.net/tracker/index.php?func=detail&aid=2991460&group_id=1
05970&atid=642714
(all seem to be duplicates)

In fact looking at the WiX 3.6 code shows this code is still unmodified and
in place.  So this explains why I still have issues with util:PermissionEx.

It seems to me that the best solution would be to specify inheritance via
attribute, just as the tracker suggests.  I can't think of a workaround when
using util:PermissionEx because subkeys created later by my application will
not inherit the "Everyone" entry and so other users won't be able to read
it...  So this raises two questions:

1.  Any good workaround to get things inheriting properly?
2.  Any feedback on the previous feature requests?  I notice that an active
subscriber actually posted a patch.  But this was 3 years ago; it seems it
didn't go anywhere?  See:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PermissionEx-e
nhancements-wix-Bugs-2127236-2016138-td1303935.html
Also see a follow-up:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chnaged-to-Cod
y-Cutrer-s-SecureObjects-enhancements-tt1563118.html

I was originally thinking of offering to implement this feature as I would
like to see this happen, but after seeing that somebody else already did and
nothing really seemed to happen with it - I am not sure if that would be
worth my time.  (Also I have no idea what is involved with contributing to
WiX - I haven't been able to find a web page describing how this process
works for WiX - many open source projects have an entire page dedicated to
this topic).  I am left scratching my head...  Is this something that will
eventually become part of a future WiX version, or were there reasons for
not merging code for the new feature?  Or does the code need more work?  It
would be nice to not have to constantly merge an old patch with every new
version of WiX. :)

Best regards,

James Johnston

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Saturday, August 06, 2011 14:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry permissions are not inherited

That is the behavior of the Windows Installer. Take a look at the
WixUtilExtension PermissionEx.

On Fri, Aug 5, 2011 at 12:44 PM, James Johnston
wrote:

> Hi,
>
> I'm trying to create some default registry keys for a component in 
> HKEY_LOCAL_MACHINE that all users should have full access to.  Here's 
> what I've got so far:
>
> 
>
>
>
>
>
>
>
>
>
>
> 
>
> The keys I would like created:
>
>   * HKLM\SOFTWARE\MyCompany: should have default ACL that users cannot 
> write to (inherit from parent)
>   * HKLM\SOFTWARE\MyCompany\MyFile: all users should have read/write 
> access to this key
>   * HKLM\SOFTWARE\MyCompany\MyFile\MySubKey: all users should have 
> read/write access to this key (inherit from parent)
>
> Unfortunately, the last key seems to be created with an ACL that only 
> allows administrators to write to the key (same ACL as for the main 
> "SOFTWARE"
> key).  Intuitively I would think that the RegistryKey underneath the 
> key granting everyone access would also grant everyone access.  But 
> that seems not to be the case.
>
> Most puzzling is that examining "MySubKey" in the registry editor 
> shows that the "Include inheritable permissions from this object's 
> parent" is checked.
> And creating new keys under "MyFile" key in registry editor works just 
> fine 

Re: [WiX-users] WiX Wrappers: For or against?

[James Johnston]

I second the vote for WixEdit.  I used it when first setting up my
installer.  Helped me learn WiX to some extent.

Now that the files are littered with preprocessor commands and I only make
small, minor changes, I find it easier to edit the WXS files directly in a
text editor.

One thing I feel is important is commenting.  There are several places where
I do things and the reasons for it are not immediately clear.  Comments help
with that, but you can't edit comments in WixEdit.  If I do use WixEdit, I
generally go back and add comments to the file as needed.

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: Monday, August 22, 2011 08:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX Wrappers: For or against?

I use WixEdit and like it. It's a GUI editor plus a simple wizard and a
couple of other features. You can switch into the .wxs file easily using one
of the menu items that runs a text editor of your choice and it will detect
and reload changes when you switch back. The files it generates can be
easily compiled with the command line tools. I find it best for small, quick
projects, such as test installers. It was also helpful when I was learning
Wix. Our main products' installers are large and complex and I use Wix
Votive solutions for those.

-Original Message-
From: Alec Taylor [mailto:alec.tayl...@gmail.com]
Sent: 20 August 2011 11:18
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX Wrappers: For or against?

Good evening,

I've seen quite a few WiX Wrapper around, including a few Open-Source ones.

Examples:
* http://sourceforge.net/projects/wixedit/ (not 100% sure this is a wrapper)
* http://sourceforge.net/projects/keeyai-flame/

What are your thoughts on WiX Wrappers, would you recommend a certain one
(not necessarily from above), or would you recommend figuring it out without
wrappers?

(e.g. just use CLI compilers and Notepad2)

Thanks for all suggestions,

Alec Taylor


-
-
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user
administration capabilities and model configuration. Take the hassle out of
deploying and managing Subversion and the tools developers use with it.
http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and
we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.



--
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Identifying Features that have been installed

[James Johnston]

You could always use the COM library if you're not comfortable with the C
API calls.  Add a COM reference to "Microsoft Windows Installer Object
Library" to your project...

Installer.get_Features and Installer.get_FeatureState look like they might
be useful.

-Original Message-
From: Anil Patel [mailto:apatel...@googlemail.com] 
Sent: Thursday, August 25, 2011 11:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Identifying Features that have been installed

Hi Peter,

Really appreciate your feedback on this.

The MsiGetEnumsFeatues() is defined as

UINT MsiEnumFeatures(
  __in   LPCTSTR szProduct,
  __in   DWORD iFeatureIndex,
  __out  LPTSTR lpFeatureBuf,
  __out  LPTSTR lpParentBuf
);

So to get the product code, I found this code

[DllImport("msi", CharSet = CharSet.Auto)]
static extern int MsiGetProductCode(string component, StringBuilder
buffer);

public static string GetProductCode(string component)
{
StringBuilder productCodeStringBuilder = new StringBuilder(512);
switch (MsiGetProductCode(component, productCodeStringBuilder))
{
case ERROR_SUCCESS:
return productCodeStringBuilder.ToString();
// *Please* don't actually just throw an exception like
this.
// Throw the relevent exception based on the error code
returned.
case ERROR_BAD_CONFIGURATION:
throw new Exception("The configuration data is
corrupt.");
case ERROR_INSTALL_FAILURE:
throw new Exception("The product code could not be
determined.");
case ERROR_INVALID_PARAMETER:
throw new Exception("An invalid parameter was passed to
the function.");
case ERROR_UNKNOWN_COMPONENT:
throw new Exception("The specified component is
unknown.");
default:
throw new Exception();
}
}

The problem is thay symbolic constants in the switch statement (eg
ERROR_INVALID_PARAMETER which are uints) aren't recognised so error on
compile.

Do you know how I can resolve these. I'm assuming there might be an Enum for
them but I can't locate them.

Again any help would be appreciated.

Regards,
Anil.


On Thu, Aug 25, 2011 at 11:13 AM, Peter Shirtcliffe
wrote:

> MsiEnumFeatures()
> http://msdn.microsoft.com/en-us/library/aa370098%28v=vs.85%29.aspx
>
>
> -Original Message-
> From: Anil Patel [mailto:apatel...@googlemail.com]
> Sent: 25 August 2011 11:08
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Identifying Features that have been installed
>
> Hello,
>
> I have a configuration program that is run manually by a user 
> (following a new install or a change to an existing installation) 
> which allows the user to configure the installed features.
>
> There is a requirement to disable the configuration of features not 
> installed by the user.
>
> The question is, is there a way for the configuration program to 
> identify which featues have been installed?
>
> I could record this data into the registry during the install and 
> remove it when a feature is uninstalled but I just wondered if there 
> was any other way of doing this.
>
> Thank you for your time.
>
>
> Regards,
> Anil.
>
> --
> ---
> -
> EMC VNX: the world's simplest storage, starting under $10K The only 
> unified storage solution that offers unified management Up to 160% 
> more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and 
> requires that you delete it without acting upon or copying any of its 
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
>  Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire 
> SL6 7DY, UK.
>
>
>
> --
>  EMC VNX: the world's simplest storage, starting under $10K 
> The only unified storage solution that offers unified management Up to 
> 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
EMC VNX: the world's simplest storage, starting under $10K The only unified
sto

[WiX-users] Problem using iis:MimeMap

[James Randolph]

Hello,

I was trying to add a fews
MimeMapelements
under a website.  Upon trying to figure out why my new MIME types
were not added I ran across a stackoverflow
questionthat
says that MimeMap does not work under a WebSite
parent even
though it's shown in the WiX schema.  I was wondering if this is still an
issue?

Thanks,

Randolph
--
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Investigating use of WiX

[James Powers]

Hi Everyone,

I'm a newbie here, so thank you all in advance for your patience and 
understanding.  I'm investigating whether or not I want to use WiX to build my 
setup/deployment project for my application.  I have read through the tutorial 
and explored the WiX sourceforge site already, but now I'd like to hear from 
practitioners some advice.  Here is what I'm trying to do:

In a single MSI file (or, in a single easy step for my end users)...

1) Install pre-requisites for my application (if they don't exist)
  - .NET 3.5 framework
  - Microsoft SQL Server Express 2008

2) Install my main application primary output
  - .EXE file
  - .DLL file
  - A couple other folders with misc. files

3) Programmatically setup my database
  - Figure out what the SQL instance name is
  - Create new SQL Databases
  - Create new SQL Stored Procedures
  - Create new SQL user w/appropriate access

4) Write new registry values
  - Write SQL instance name from Step 3
  - Write SQL user name and encrypted password from Step 3


My biggest question is whether or not I should embark on this adventure with 
WiX.  I have two main options:

1) I could simply state my application pre-requisites are .NET framework 3.5 
and SQL Server Express 2008.  If I just stated those were my pre-requisites, I 
wouldn't have to worry about installing them.  I could check to see if they 
exist and display an error if they don't.

With this option, I could also simply ask for the SQL Server instance name, the 
user account, and the password when my application loads for the first time.  I 
would leave it into the hands of the user to make sure SQL Server was 
installed.  I don't particularly like this option because it makes it harder on 
my end user.

2) I could try to figure all this out with WiX.  Or some other technology for 
that matter.  My biggest concern here is how to take control of the setup 
program and specify my database name, user account, and password.  I need to 
know what the credentials are so I can run my database table and stored 
procedure creation scripts.

So if I go this option, I don't know if I need to know the SQL Server SA 
password so I can then create my SQL User, tables, and stored procedures.  And 
if I do, how do I figure that out?


Any help or advice would be greatly appreciated.  Thank you!



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Should i go for creation of 64 bit msi?

[James Poole]

Unless you have a million dollar deal pending on support of a Core Server
without 32-bit WOW, I would say it's not worth your effort...

If you have the power, I would designate this as an unsupported
configuration.

-James

On Fri, Jun 11, 2010 at 1:41 PM, Sagar wrote:

>
> I agree with you Pally,
> but in some special scenarios like if the 64-bit OS itself doesn't support
> 32-installation then in that case we have no other option but to create a
> 64-bit installer irrespective of the files the msi deploys.
>
> I read
>
> http://blogs.msdn.com/b/heaths/archive/2009/11/06/wow64-is-optional-in-windows-server-2008-r2-server-core.aspx
> this blog  where it says
> 32-bit support is optional in Windows Server 2008 R2 Server Core.
>
>
> http://blogs.msdn.com/b/heaths/archive/2009/11/06/wow64-is-optional-in-windows-server-2008-r2-server-core.aspx
>
>
> I am i right?
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Should-i-go-for-creation-of-64-bit-msi-tp5168856p5168999.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> --
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Best Practices - Using "*" for GUID automation

[James Poole]

Could someone chime in with a time when you wouldn't want to use "*" on
component Guids?  Would this cause issues with generating patches?

-James

On Tue, Jun 29, 2010 at 1:19 PM, Andy Clugston  wrote:

> Okay, it seemed like this approach would work, just wanted to verify.
> Thanks!
>
> On Tue, Jun 29, 2010 at 10:10 AM, Cherney John-CJC030 <
> john.cher...@motorola.com> wrote:
>
> > I haven't had any problems with component ids set to "*". We keep the
> > Upgrade id constant but vary everything else, including the version and
> > the MSI name (which contains the version). Because of the changing
> > version and the constant upgrade id (and the PREVIOUSFOUND property
> > getting set in the UpgradeVersion element), we are automatically
> > uninstalling older versions as part of our install. Works very well.
> >
> > jwc
> >
> > -Original Message-
> > From: Andy Clugston [mailto:clug...@gmail.com]
> > Sent: Tuesday, June 29, 2010 7:35 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: [WiX-users] Best Practices - Using "*" for GUID automation
> >
> > I am trying to determine the best approach to take with creating GUIDs
> > for the various WiX elements.  We use a full upgrade approach so I
> > believe for the Product Id="*" is okay.  It probably goes without saying
> > that setting Package Id="*" makes sense in all cases.  It is my
> > understanding that the Upgrade Id should be static (never changes) for
> > the life of a product installer, assuming the name of the MSI does not
> > change.
> >
> > The one that I need some assistance with is at the Component level.  We
> > want to automate as much as we can, and having to update Component GUIDs
> > for hundreds of deliverables is a pain.  Is it safe to set Component
> > Guid="*", or will this cause problems in the future?  I worry that this
> > will affect how upgrades work, but I think I might be misunderstanding
> > (or
> > over-thinking) something.  I would assume it is bad practice to leave
> > the Component Guid the same for a deliverable if that deliverable is
> > updated between versions, however if a particular deliverable does *not*
> > change, is it safe to leave its Component Guid alone?
> >
> > Thanks.
> > 
> > --
> > This SF.net email is sponsored by Sprint What will you do first with
> > EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> --
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Bold Titles on Custom Dialogs

[James Green]

Hi All,
 
I'm just creating my first WiX installer so far all is well.  I've created
one custom dialog for my installer but I cannot seem to set the Title to
bold text to fall in line with the other dialogs.
 
I'm using  as the basis for the UI and in my
custom dialog I have the following set:
 

 
However, as opposed to the other dialogs this text isn't bold and I cannot
figure out how to set this.  Any pointers would be great.
 
Kind regards,
 
James Green
.NET Developer
 

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bold Titles on Custom Dialogs

[James Green]

Thanks again! 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Pally Sandher
Sent: 30 June 2010 16:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bold Titles on Custom Dialogs

It'll be rendering with the font specified in the DefaultUIFont Property
unless you tell it otherwise

Try


The standard fonts are listed in WiXUI_Installdir.wxs but you can define
your own using the TextStyle Element if you want to use something different,
just use them in the same way as above.

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-----
From: James Green [mailto:james.gr...@lalpac.com]
Sent: 30 June 2010 15:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bold Titles on Custom Dialogs

Hi All,
 
I'm just creating my first WiX installer so far all is well.  I've created
one custom dialog for my installer but I cannot seem to set the Title to
bold text to fall in line with the other dialogs.
 
I'm using  as the basis for the UI and in my
custom dialog I have the following set:
 

 
However, as opposed to the other dialogs this text isn't bold and I cannot
figure out how to set this.  Any pointers would be great.
 
Kind regards,
 
James Green
.NET Developer
 

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support:
+44 (0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please
notify the author by replying to this e-mail. If you are not the intended
recipient you may not use, disclose, distribute, copy, print or rely on this
e-mail.

Opinions advice, conclusions and other information in this message that do
not relate to the official business of LalPac Ltd shall be understood as
neither given nor endorsed by it or on its behalf, and consequently LalPac
Ltd shall bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and
are believed to be free of viruses but it is your responsibility to carry
out all necessary virus checks and LalPac Ltd accepts no liability in
connection therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a
satisfactory level of customer service is maintained, to maintain Company
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER

--
This SF.net email is sponsored by Sprint What will you do first with EVO,
the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
This SF.net email is sponsored by Sprint What will you do first with EVO,
the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachme

Re: [WiX-users] Bold Titles on Custom Dialogs

[James Green]

Many thanks! 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Yan Sklyarenko
Sent: 30 June 2010 16:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bold Titles on Custom Dialogs

Prefix the text with "{\WixUI_Font_Title}". So, in your text it will be:

   

But, if you want this to be localized (I guess you do), move the value of
the Text attribute to a *.wxl file, and leave a reference to it from the
Control element, something like this:

*.wxl
   ...
   {\WixUI_Font_Title}Create Virtual
Directory
   ...

*.wxs
 ...
   
 ...

Hope this helps,

-- Yan

-Original Message-----
From: James Green [mailto:james.gr...@lalpac.com]
Sent: Wednesday, 30 June, 2010 17:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bold Titles on Custom Dialogs

Hi All,
 
I'm just creating my first WiX installer so far all is well.  I've created
one custom dialog for my installer but I cannot seem to set the Title to
bold text to fall in line with the other dialogs.
 
I'm using  as the basis for the UI and in my
custom dialog I have the following set:
 

 
However, as opposed to the other dialogs this text isn't bold and I cannot
figure out how to set this.  Any pointers would be great.
 
Kind regards,
 
James Green
.NET Developer
 

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support:
+44 (0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please
notify the author by replying to this e-mail. If you are not the intended
recipient you may not use, disclose, distribute, copy, print or rely on this
e-mail.

Opinions advice, conclusions and other information in this message that do
not relate to the official business of LalPac Ltd shall be understood as
neither given nor endorsed by it or on its behalf, and consequently LalPac
Ltd shall bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and
are believed to be free of viruses but it is your responsibility to carry
out all necessary virus checks and LalPac Ltd accepts no liability in
connection therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a
satisfactory level of customer service is maintained, to maintain Company
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER

--
This SF.net email is sponsored by Sprint What will you do first with EVO,
the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
This SF.net email is sponsored by Sprint What will you do first with EVO,
the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all

[WiX-users] Removing IIS Virtual Dirs

[James Green]

Hi All,

I'm sure those that read my last post could have predicted this next
questsion! I've been looking into the removal of the virtual directory
during the uninstall process and found the following post:

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01664.html

Is this still regarded as the best/only way to remove virtual directories
using WiX?

Kind regards,
 
James Green
.NET Developer

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Removing IIS Virtual Dirs

[James Green]

OK, Replying to my onw threads already isn't good!

I've just been doing a bit more testing on my installer and it appears to be
removing the virtural directories automatically now, I have seen the
uninstall process leave orphaned virtual directories.  Does this sound
familiar to anyone here?

Regards,

James. 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of James Green
Sent: 30 June 2010 17:10
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Removing IIS Virtual Dirs

Hi All,

I'm sure those that read my last post could have predicted this next
questsion! I've been looking into the removal of the virtual directory
during the uninstall process and found the following post:

http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg01664.html

Is this still regarded as the best/only way to remove virtual directories
using WiX?

Kind regards,
 
James Green
.NET Developer

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please
notify the author by replying to this e-mail. If you are not the intended
recipient you may not use, disclose, distribute, copy, print or rely on this
e-mail.

Opinions advice, conclusions and other information in this message that do
not relate to the official business of LalPac Ltd shall be understood as
neither given nor endorsed by it or on its behalf, and consequently LalPac
Ltd shall bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and
are believed to be free of viruses but it is your responsibility to carry
out all necessary virus checks and LalPac Ltd accepts no liability in
connection therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a
satisfactory level of customer service is maintained, to maintain Company
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER



--
This SF.net email is sponsored by Sprint What will you do first with EVO,
the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Removing IIS Virtual Dirs

[James Green]

Thanks for this Rob, will check the logs if I see this again. 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Rob Mensching
Sent: 01 July 2010 06:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Removing IIS Virtual Dirs

Nope. If you see virtual directories being left behind, take a look in the
verbose log file and make sure the Component containing the vdir was
removed.

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] VS2010 automated build

[James Green]

I was just about to ask the same question! 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Stelios Kyprou
Sent: 01 July 2010 12:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VS2010 automated build

Good stuff!
@John:
A Paraffin question:
What if i want to exclude files lets say with extension: .vshost.exe, but
not .exe files?
I think i am not able to do that am i?

Stelios

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Removing IIS Virtual Dirs

[James Green]

Hi Again,

We have been doing a little more poking around with some test installers we
have created that make use of the WixIIsExtension library and we're seeing
some odd behaviour.  The latest installer that I have been working on seems
to work as expected on IIS 5.1 (XP) and IIS 7 on Server 2008 but fails to
remove the virtual directory on IIS 7 running under Windows 7.

The strange thing is on the Windows 7 machine the uninstall log was
reporting a successful rollback of the component within the installer but
the virtual directory was still present.

Has anyone else seen this behaviour or have any ideas what the issue may be?

Regards,

James

--
Nope. If you see virtual directories being left behind, take a look in the
verbose log file and make sure the Component containing the vdir was
removed.

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional Button Enabling

[James Green]

Hi Guys,
 
I really am the noob!  I've tried loads of different variations on this and
as far as I can tell from the examples this looks like it should be working
but it's not.  What am I doing wrong here?
 
I have four Edit controls and as long as there is something in all of then
the next button should be enabled.





Any pointers would be great.
 
Kind regards,
 
James Green
.NET Developer

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional Button Enabling

[James Green]

Hi Palbinder,

That was the syntax I originally tried.  There must be another issue I'm
overlooking at the moment.

Thanks,

James. 

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Pally Sandher
Sent: 02 July 2010 11:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Conditional Button Enabling

Use <> instead of !=

See http://msdn.microsoft.com/en-us/library/aa368012.aspx 

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting Progress of Rollback

[James Poole]

I've used the example here with success:
http://msdn.microsoft.com/en-us/library/aa368786%28v=VS.85%29.aspx

You'll see that it has a section where it handles the progress and roll
back.  Look at:

/* determine direction */

-James Poole

On Thu, Jul 1, 2010 at 6:02 PM, Andy Glass  wrote:

> I realize that this isn't a WiX-specific question, but I figure someone
> here may have run into the same issue:
>
> I've written a bootstrapper to install our msis, and am using
> MsiSetExternalUI to get  the status updates/progress for the bootstrapper's
> UI.  The problem is that when the installation fails or is canceled, it
> seems to stop sending messages to the external UI callback and so I have no
> way to tell how far along the rollback is, or even if it has completed.
>  Does anyone know of a good way to do this (either actually getting the
> rollback progress or simply telling when it is done)?
>
> -Andy
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting Progress of Rollback

[James Poole]

What was the return code from MsiInstallProduct?

Also, are you sure you are at a point where it would actually give you roll
back status?  If it's a small product it may just be happening too fast for
you to notice.

On Fri, Jul 2, 2010 at 12:02 PM, Andy Glass  wrote:

> That is actually the code I'm basing off of.  The problem is that after the
> user cancels the installation and the handler returns IDCANCEL,
> MsiInstallProduct immediately returns and the handler receives no more
> messages.
>
> -Andy
>
> -Original Message-
> From: James Poole [mailto:w...@slowcommotion.com]
> Sent: Friday, July 02, 2010 5:59 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Getting Progress of Rollback
>
> I've used the example here with success:
> http://msdn.microsoft.com/en-us/library/aa368786%28v=VS.85%29.aspx
>
> You'll see that it has a section where it handles the progress and roll
> back.  Look at:
>
> /* determine direction */
>
> -James Poole
>
> On Thu, Jul 1, 2010 at 6:02 PM, Andy Glass  wrote:
>
> > I realize that this isn't a WiX-specific question, but I figure someone
> > here may have run into the same issue:
> >
> > I've written a bootstrapper to install our msis, and am using
> > MsiSetExternalUI to get  the status updates/progress for the
> bootstrapper's
> > UI.  The problem is that when the installation fails or is canceled, it
> > seems to stop sending messages to the external UI callback and so I have
> no
> > way to tell how far along the rollback is, or even if it has completed.
> >  Does anyone know of a good way to do this (either actually getting the
> > rollback progress or simply telling when it is done)?
> >
> > -Andy
> >
> >
> --
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Showing Message after running Managed CA

[James Green]

Hi All,
 
So far all is working OK with my installer.  I have a single managed (C#)
Custom Action that gets run to test a database connection.  I have it
writing out to a property like this:
 
session["DB_CONNECTION_OK"] = "1";

I can see this getting updated in the log correctly.  However, on the dialog
the message I have 'bound' to this property is never shown when the property
is updated however, it is in to correct state when the dialog is initialised
(ie: hidden):


  DB_CONNECTION_OK = 1
  DB_CONNECTION_OK = 0


What extra steps are required to get this message to show on the form one
the DB_CONNECTION_OK property is set to 1?
 
Kind regards,
 
James Green
.NET Developer

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Showing Message after running Managed CA

[James Green]

Billiant, thanks Peter, all solved.

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Peter
Shirtcliffe
Sent: 05 July 2010 14:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Showing Message after running Managed CA

See my reply in this thread. 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/UI-Edit-Bo
x-not-updating-td5077648.html

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFxApp

[James Johnston]

Maybe the driver is not WHQL signed?

I'm not sure why you wouldn't have the same issue with DPInst, however.  I
was under the impression that the various DIFX methods (DPInst, DIFxApp,
DIFxAPI) would all call the same underlying code to perform the driver
install.  Seems like anything else would be a crazy design.

> -Original Message-
> From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
> Sent: Friday, November 16, 2012 15:29
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] DIFxApp
> 
> I'm trying to replace a driver "installer" (essentially a self-extracting
EXE with
> INF file etc. which runs DPInst) with a WiX-based MSI.
> 
> I'm using WixDifxAppExtention and it's working except that I get a
security
> warning: "Windows can't verify the publisher of this driver software"
(with
> options to continue or abort driver installation). The existing EXE/DPInst
> installer doesn't produce this warning.
> 
> Any idea what I might be doing wrong?
> 
> Thanks
> 
> 
> 
>

--
> Monitor your physical, virtual and cloud infrastructure from a single web
> console. Get in-depth insight into apps, servers, databases, vmware, SAP,
> cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Installing a driver in Win 7

[James Johnston]

What's wrong?  You're DPInst.  Use DIFxApp, not DPInst.  DIFxApp was
designed for MSI; you're trying to fit a square peg into a round hole using
DPInst.

For example, have you considered whether your MSI works correctly in a
rollback situation?  Uninstall?  Repair?  Situations where the user
interface has limited permissions?  Other edge cases I'm not thinking of?
Etc. etc.  The DIFxApp programmers already figured this stuff out for you
and tested it.  Failing to address this stuff could make your package a
future sysadmin's nightmare.

The 32/64-bit issue, while inconvenient, exists with DPInst anyway if I
remember right.  It's possible to generate both 32-bit and 64-bit MSIs from
the same WiX source code with DIFxApp.  This is the correct way to do driver
installation with MSI.

> -Original Message-
> From: Branko Horvat [mailto:horvat.bra...@pieps.com]
> Sent: Tuesday, January 08, 2013 11:20
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Installing a driver in Win 7
> 
> I'm trying to make an installer using DPInst.exe as a CustomAction.
Although
> there are some solutions provided, it fails.
> I can install the driver using rightclick on .inf and Install. I can even
use
> manually DPInst.exe on installed folder.
> 
> When I use Notepad.exe instead of DPInst.exe it works. Although
> DPInst.exe is inlcuded in the installed folder as DPInst64.exe. I can even
> achieve that Notepad opens our .inf file (provide parameter).
> 
> The result of installing our .msi is the entry in ARP. In Device Manager
the
> device is not properly installed.
> Seeing .log shows an error in using quiet mode, or nothing. My notion was,
> the path is somehow wrong.
> So, I tried to add "/path parameter" but still failed.
> 
> I know I can try finally using  but I still try using
DPInst.exe to
> avoid taking care of
> 32- or 64-bits. Do you have any idea what could be wrong?
> 
> These is my fragment of trials on "custom actions":
> 
> 
>  DllEntry="CAQuietExec64"
> Execute="immediate" Return="check"/>
> 
> The log says:
> CAQuietExec64:  Error 0x80070002: Command failed to execute.
> CAQuietExec64:  Error 0x80070002: CAQuietExec64 Failed
> 
> Or
> 
> DPInst64.exe
>  ExeCommand='' Return='asyncNoWait' />
> 
> There is no error but neither proper installation.
> 
> Notepad.exe
>  ExeCommand='[SourceDir]piepscdc.inf' Return='asyncNoWait' />
> 
> Here I had to provide path [SourceDir] or target
> [INSTALLDIR]\subfolder\some.inf ...
> 
> 
> NOT
> VersionNT64
>  After='InstallFinalize'>VersionNT64
> 
>

--
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and
> more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFxApp and upgrades

[James Johnston]

This did the trick for us:




I haven't had any complaints in a long time now since doing this.  At this
point, I would always schedule things this way if using DIFxApp.  As I
described in the message you quoted, we previously had
RemoveExistingProducts scheduled after InstallInitialize, which led to the
problems I described.

The downside to scheduling RemoveExistingProducts before InstallInitialize
is that if the install fails, the old version isn't restored and the user is
left with no product at all on their system.  But it's better than a
corrupted DIFxApp configuration being left on the system.

It would really be nice if the DIFxApp team would fix these issues...  Or at
least document the limitations so that at least people who read the docs
don't get trapped by this.

> -Original Message-
> From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
> Sent: Wednesday, January 09, 2013 14:14
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
> 
> We've recently been seeing issue 1 where an upgrade doesn't work due to a
> missing registry entry.  We're currently telling customers how to do a
full
> repair on a case by case basis as this occurs.  Did anyone ever find a fix
for
> this?
> 
> Thanks,
> Rob
> 
> On 29/11/2010 21:23, James Johnston wrote:
> > Hi,
> >
> > A couple questions, both regarding DIFxApp.  (We use it to install
> > three drivers for three plug-and-play USB devices for a hardware
> > product that we
> > ship.)
> >
> > 1.  Some time ago Rob Mensching mentioned the following on this list:
> >
> > "Yeah, there are some design issues in the DIFxApp code around
> > Upgrades I'm still trying to figure out what to do with DIFx since we
> > don't have the code to fix it here. I'll try to find someone to
> > forward this thread to see if we can't get some movement (not that it
has
> worked yet)."
> > http://www.mail-archive.com/wix-
> us...@lists.sourceforge.net/msg35219.h
> > tml
> >
> > I am very interested in knowing whether anybody here knows what some
> > of these design issues might be?  Can DIFxApp be used when an
> > application must be serviced in the future?  I looked through MSDN and
> > did not find any mention one way or the other regarding DIFxApp and
> > upgrades.  If upgrades are not supported (which would seem like a
> > serious deficiency!), what is the recommended way of servicing an app
> > that uses DIFxApp?  Just what, exactly, are the caveats involved with
> upgrades and DIFx?
> >
> > The reason I ask is that upgrades are not going as well as we would
like.
> > Currently we service our application very simply.  Every new version
> > is a major upgrade: new product code, new version number.  We have
> > always scheduled RemoveExistingProducts immediately after
> > InstallInitialize.  We have tested this in-house on just about every
> > computer at our (small) company without any issue: the upgrades
generally
> go very smoothly.
> > Additionally, most of our customers have also done upgrades without
> issue.
> >
> > However, there have been a few customers (i.e. about 10: enough for us
> > to not consider it to be an isolated incident) where they were unable
> > to upgrade.  The setup program will roll back and fail when upgrading.
> > Also, they are then unable to uninstall the software: again, the setup
> > program rolls back when attempting to remove the product.  The MSI
> > logs always point to DIFx as the problem, with DIFx indicating that
> > key DIFx information in the registry is missing.  Searching Google
> > seems to indicate that we may not be the only people experiencing this
> > issue.  The problem has been observed on both Windows XP SP3 and
> > Windows 7 (few customers use Vista).  Every setup package uses the
> > version of DIFx included with WiX 3.0 (I believe it's version 2.1.1).
> >
> > In order to get the customer working again, we have successfully used
> > the following workaround in every case: (1) delete the key file as
> > specified by the driver component, (2) do a repair of the existing
> > product; the absence of the key file triggers MSI/DIFx to successfully
> > install the driver again,
> > (3) we can now uninstall the old product/MSI, (4) the new product/MSI
> > can be installed.  Unfortunately, we have not been able to reproduce
> > the problem locally.  That also means that we (obviously) haven't
> > identified what it is about the customer computer that causes problems.
> > 


--

Re: [WiX-users] DIFxApp and upgrades

[James Johnston]

This MSKB article discusses how to do it:

http://support.microsoft.com/kb/259697

> -Original Message-
> From: Shane Corbin [mailto:shane_cor...@selinc.com]
> Sent: Friday, January 11, 2013 22:49
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
> 
> I'm still curious how you are calling CM_Reenumerate_DevNode on the root
> devnode in your custom action.
> 
> Would you mind sharing this snippet?
> 


--
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] I watched your youtube vid. I have 3 files, created installer ok, but installing it gave win-error.

[james pruett]

Hi,

Thanks for writing Wix.
I will donate to the tip jar or flattr.

I tried my installer and didn't quite make it...
Not sure how to diagnose it.

Here is everything (.SED, _installer.exe)
http://www.wikispeedia.org/speedo/
Thanks for looking! I appreciate it.

-cellurl
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] newbie

[james pruett]

Can anyone point me to how I debug this puppy?
It failed when I did the install.
Is there a fail-log or such?
If I am asking wrong, please let me know.
Thanks for looking
-celllurl


[Version]
Class=IEXPRESS
SEDVersion=3
[Options]
PackagePurpose=InstallApp
ShowInstallProgramWindow=0
HideExtractAnimation=0
UseLongFileName=0
InsideCompressed=0
CAB_FixedSize=0
CAB_ResvCodeSigning=0
RebootMode=N
InstallPrompt=%InstallPrompt%
DisplayLicense=%DisplayLicense%
FinishMessage=%FinishMessage%
TargetName=%TargetName%
FriendlyName=%FriendlyName%
AppLaunched=%AppLaunched%
PostInstallCmd=%PostInstallCmd%
AdminQuietInstCmd=%AdminQuietInstCmd%
UserQuietInstCmd=%UserQuietInstCmd%
SourceFiles=SourceFiles
[Strings]
InstallPrompt=
DisplayLicense=
FinishMessage=
TargetName=C:\aaa_jim_test\Speedanator_installer.EXE
FriendlyName=Speedanator
AppLaunched=Demo.WindowsForms.exe
PostInstallCmd=
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="GMap.NET.WindowsForms.dll"
FILE1="Demo.WindowsForms.exe"
FILE2="GMap.NET.Core.dll"
[SourceFiles]
SourceFiles0=C:\aaa_jim_test\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified

[james pruett]

Hi,
Can anyone spot what I am doing wrong?
Thanks for looking.
-cellurl


VisualStudio10 comes up with this error:--

Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0,
Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its
dependencies. The system cannot find the file specified.



here is the .SED file-

[Version]
Class=IEXPRESS
SEDVersion=3
[Options]
PackagePurpose=InstallApp
ShowInstallProgramWindow=0
HideExtractAnimation=0
UseLongFileName=0
InsideCompressed=0
CAB_FixedSize=0
CAB_ResvCodeSigning=0
RebootMode=N
InstallPrompt=%InstallPrompt%
DisplayLicense=%DisplayLicense%
FinishMessage=%FinishMessage%
TargetName=%TargetName%
FriendlyName=%FriendlyName%
AppLaunched=%AppLaunched%
PostInstallCmd=%PostInstallCmd%
AdminQuietInstCmd=%AdminQuietInstCmd%
UserQuietInstCmd=%UserQuietInstCmd%
SourceFiles=SourceFiles
[Strings]
InstallPrompt=
DisplayLicense=
FinishMessage=
TargetName=C:\aaa_jim_test\Speedanator_installer.EXE
FriendlyName=Speedanator
AppLaunched=Demo.WindowsForms.exe
PostInstallCmd=
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="GMap.NET.WindowsForms.dll"
FILE1="Demo.WindowsForms.exe"
FILE2="GMap.NET.Core.dll"
[SourceFiles]
SourceFiles0=C:\aaa_jim_test\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=


---here are all the source files--

http://www.wikispeedia.org/speedo/
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified

[james pruett]

aren't you the
"Windows Installer" <http://wixtoolset.org/>
folks?





On Tue, Feb 26, 2013 at 3:15 PM, james pruett  wrote:

> Hi,
> Can anyone spot what I am doing wrong?
> Thanks for looking.
> -cellurl
>
>
> VisualStudio10 comes up with this error:--
>
> Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0,
> Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its
> dependencies. The system cannot find the file specified.
>
>
>
> here is the .SED file-
>
> [Version]
> Class=IEXPRESS
> SEDVersion=3
> [Options]
> PackagePurpose=InstallApp
> ShowInstallProgramWindow=0
> HideExtractAnimation=0
> UseLongFileName=0
> InsideCompressed=0
> CAB_FixedSize=0
> CAB_ResvCodeSigning=0
> RebootMode=N
> InstallPrompt=%InstallPrompt%
> DisplayLicense=%DisplayLicense%
> FinishMessage=%FinishMessage%
> TargetName=%TargetName%
> FriendlyName=%FriendlyName%
> AppLaunched=%AppLaunched%
> PostInstallCmd=%PostInstallCmd%
> AdminQuietInstCmd=%AdminQuietInstCmd%
> UserQuietInstCmd=%UserQuietInstCmd%
> SourceFiles=SourceFiles
> [Strings]
> InstallPrompt=
> DisplayLicense=
> FinishMessage=
> TargetName=C:\aaa_jim_test\Speedanator_installer.EXE
> FriendlyName=Speedanator
> AppLaunched=Demo.WindowsForms.exe
> PostInstallCmd=
> AdminQuietInstCmd=
> UserQuietInstCmd=
> FILE0="GMap.NET.WindowsForms.dll"
> FILE1="Demo.WindowsForms.exe"
> FILE2="GMap.NET.Core.dll"
> [SourceFiles]
> SourceFiles0=C:\aaa_jim_test\
> [SourceFiles0]
> %FILE0%=
> %FILE1%=
> %FILE2%=
>
>
> ---here are all the source files--
>
> http://www.wikispeedia.org/speedo/
>
>
>
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified

[james pruett]

hmmm,
Can you help me make an installer?








On Tue, Feb 26, 2013 at 3:55 PM, Steven Ogilvie wrote:

> Classification: Public
>
>
> This is the Windows Installer XML installer user list, I think you want
> the IExpress Self Extraction Directive File? We don't use iexpress.exe
>
> -Original Message-
> From: james pruett [mailto:gpscru...@gmail.com]
> Sent: February-26-13 4:47 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Could not load file or assembly 'GMap.NET.Core,
> Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one
> of its dependencies. The system cannot find the file specified
>
> aren't you the
> "Windows Installer" <http://wixtoolset.org/> folks?
>
>
>
>
>
> On Tue, Feb 26, 2013 at 3:15 PM, james pruett  wrote:
>
> > Hi,
> > Can anyone spot what I am doing wrong?
> > Thanks for looking.
> > -cellurl
> >
> >
> > VisualStudio10 comes up with this error:--
> >
> > Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0,
> > Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its
> > dependencies. The system cannot find the file specified.
> >
> >
> >
> > here is the .SED file-
> >
> > [Version]
> > Class=IEXPRESS
> > SEDVersion=3
> > [Options]
> > PackagePurpose=InstallApp
> > ShowInstallProgramWindow=0
> > HideExtractAnimation=0
> > UseLongFileName=0
> > InsideCompressed=0
> > CAB_FixedSize=0
> > CAB_ResvCodeSigning=0
> > RebootMode=N
> > InstallPrompt=%InstallPrompt%
> > DisplayLicense=%DisplayLicense%
> > FinishMessage=%FinishMessage%
> > TargetName=%TargetName%
> > FriendlyName=%FriendlyName%
> > AppLaunched=%AppLaunched%
> > PostInstallCmd=%PostInstallCmd%
> > AdminQuietInstCmd=%AdminQuietInstCmd%
> > UserQuietInstCmd=%UserQuietInstCmd%
> > SourceFiles=SourceFiles
> > [Strings]
> > InstallPrompt=
> > DisplayLicense=
> > FinishMessage=
> > TargetName=C:\aaa_jim_test\Speedanator_installer.EXE
> > FriendlyName=Speedanator
> > AppLaunched=Demo.WindowsForms.exe
> > PostInstallCmd=
> > AdminQuietInstCmd=
> > UserQuietInstCmd=
> > FILE0="GMap.NET.WindowsForms.dll"
> > FILE1="Demo.WindowsForms.exe"
> > FILE2="GMap.NET.Core.dll"
> > [SourceFiles]
> > SourceFiles0=C:\aaa_jim_test\
> > [SourceFiles0]
> > %FILE0%=
> > %FILE1%=
> > %FILE2%=
> >
> >
> > ---here are all the source files--
> >
> > http://www.wikispeedia.org/speedo/
> >
> >
> >
> >
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics Download AppDynamics Lite for
> free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> This message has been marked as Public by Steven Ogilvie on February-26-13
> 4:55:06 PM.
>
> The above classification labels were added to the message by TITUS Message
> Classification.
> Visit www.titus.com for more information.
>
>
> --
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified

[james pruett]

Thanks for pointing out what I was using to create it.
I will link your tools into Visual Studio and try again.
Thanks again.
-cellurl





On Tue, Feb 26, 2013 at 3:15 PM, james pruett  wrote:

> Hi,
> Can anyone spot what I am doing wrong?
> Thanks for looking.
> -cellurl
>
>
> VisualStudio10 comes up with this error:--
>
> Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0,
> Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its
> dependencies. The system cannot find the file specified.
>
>
>
> here is the .SED file-
>
> [Version]
> Class=IEXPRESS
> SEDVersion=3
> [Options]
> PackagePurpose=InstallApp
> ShowInstallProgramWindow=0
> HideExtractAnimation=0
> UseLongFileName=0
> InsideCompressed=0
> CAB_FixedSize=0
> CAB_ResvCodeSigning=0
> RebootMode=N
> InstallPrompt=%InstallPrompt%
> DisplayLicense=%DisplayLicense%
> FinishMessage=%FinishMessage%
> TargetName=%TargetName%
> FriendlyName=%FriendlyName%
> AppLaunched=%AppLaunched%
> PostInstallCmd=%PostInstallCmd%
> AdminQuietInstCmd=%AdminQuietInstCmd%
> UserQuietInstCmd=%UserQuietInstCmd%
> SourceFiles=SourceFiles
> [Strings]
> InstallPrompt=
> DisplayLicense=
> FinishMessage=
> TargetName=C:\aaa_jim_test\Speedanator_installer.EXE
> FriendlyName=Speedanator
> AppLaunched=Demo.WindowsForms.exe
> PostInstallCmd=
> AdminQuietInstCmd=
> UserQuietInstCmd=
> FILE0="GMap.NET.WindowsForms.dll"
> FILE1="Demo.WindowsForms.exe"
> FILE2="GMap.NET.Core.dll"
> [SourceFiles]
> SourceFiles0=C:\aaa_jim_test\
> [SourceFiles0]
> %FILE0%=
> %FILE1%=
> %FILE2%=
>
>
> ---here are all the source files--
>
> http://www.wikispeedia.org/speedo/
>
>
>
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] System Properties?

[James Allen]

I am building a bootstrapper for which I need to check minimum system 
requirements and I was wondering if there is a way to check for the following :

Ø  Available Hard Disk Space

Ø  RAM

Ø  Processor

Ø  Display Screen resolution


I would like to do this from my Bundle element if that is possible. Also is 
there a list I can reference of the predefined WiX properties that can be used 
in Launch Conditions?

James Allen


--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] System Properties?

[James Allen]

This will compile however the resultant .exe will not run, what am I doing 
wrong?

http://msdn.microsoft.com/en-us/library/windows/desktop/aa371639(v=vs.85).aspx>
 >=2) AND (PhysicalMemory > 2048) AND (OutOfDiskSpace = 'FALSE'))" >

James Allen


--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] System Properties?

[James Allen]

Thanks for all the help guys, that got me unstuck!

James Allen


--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] RemoveExisting Products failing with /qn upgrade

[James Poole]

Does any know why the RemoveExistingProducts action would fail when an
upgrade is run silently?

If I run in full UI mode, everything works as expected.  If I run the
upgrade with /qn, the RemoveExistingProducts does not work and I end up with
both products installed on the system.

RemoveExistingProducts is scheduled right after InstallInitialize.

Verbose log says:


MSI (s) (B8:28) [03:53:57:096]: Doing action: RemoveExistingProducts
Action ended 3:53:57: InstallInitialize. Return value 1.
Action start 3:53:57: RemoveExistingProducts.
MSI (s) (B8:48) [03:53:57:128]: Resetting cached policy values
MSI (s) (B8:48) [03:53:57:128]: Machine policy value 'Debug' is 0
MSI (s) (B8:48) [03:53:57:128]: *** RunEngine:
   *** Product: 1
   *** Action:
   *** CommandLine: **
MSI (s) (B8:28) [03:53:57:128]: Ignoring failure to remove product
during upgrade - product already uninstalled.
MSI (s) (B8:28) [03:53:57:128]: Doing action: ca_LogUserInfo
Action ended 3:53:57: RemoveExistingProducts. Return value 1.
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] RemoveExisting Products failing with /qn upgrade

[James Poole]

Thanks for the input guys... Tom, I owe you a beer.

In case anyone finds this in the archives:

There was a custom action that was slamming the property referenced in the
ActionProperty column of the Upgrade Table.  During the UI sequence, it was
scheduled before FindRelatedProducts so it had not effect, but for the
Execute Sequece it was after.

The property was getting set to "1", so it now makes sense that the log said
"Product: 1" during RemoveExistingProducts.

Thanks again,
James

On Sat, Jul 17, 2010 at 8:56 AM, Blair  wrote:

> Also, try running a pure uninstall in quiet mode with logging.
>
> -Original Message-
> From: Thomas Svare [mailto:thomas_sv...@symantec.com]
> Sent: Saturday, July 17, 2010 5:17 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] RemoveExisting Products failing with /qn upgrade
>
> One thing to look at would be how FindRelatedProducts is scheduled in
> the InstallUISequence and InstallExecuteSequence.  Also look at what the
> ActionProperty in the Upgrade table is set to in both cases.
>
> Thanks,
> Tom
>
> -Original Message-
> From: James Poole [mailto:w...@slowcommotion.com]
> Sent: Friday, July 16, 2010 5:34 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] RemoveExisting Products failing with /qn upgrade
>
> Does any know why the RemoveExistingProducts action would fail when an
> upgrade is run silently?
>
> If I run in full UI mode, everything works as expected.  If I run the
> upgrade with /qn, the RemoveExistingProducts does not work and I end up
> with
> both products installed on the system.
>
> RemoveExistingProducts is scheduled right after InstallInitialize.
>
> Verbose log says:
>
>
> MSI (s) (B8:28) [03:53:57:096]: Doing action: RemoveExistingProducts
> Action ended 3:53:57: InstallInitialize. Return value 1.
> Action start 3:53:57: RemoveExistingProducts.
> MSI (s) (B8:48) [03:53:57:128]: Resetting cached policy values
> MSI (s) (B8:48) [03:53:57:128]: Machine policy value 'Debug' is 0
> MSI (s) (B8:48) [03:53:57:128]: *** RunEngine:
>   *** Product: 1
>   *** Action:
>   *** CommandLine: **
> MSI (s) (B8:28) [03:53:57:128]: Ignoring failure to remove product
> during upgrade - product already uninstalled.
> MSI (s) (B8:28) [03:53:57:128]: Doing action: ca_LogUserInfo
> Action ended 3:53:57: RemoveExistingProducts. Return value 1.
> 
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> 
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Messagebox from custom action with a lot of text

[James Poole]

Did you try just showing a standard windows forms message box from within
your C# custom action?

MessageBox.Show()

On Mon, Jul 19, 2010 at 12:31 PM,  wrote:

>
> Hi Christopher
>
> I currently have the action scheduled after "CreateFolders".  I use the CA
> almost like a startup-condition.  There may also be other places where i
> intend to show a messagebox, but this is not defined yet.
>
> I hoped it would be something rather simple, either a flag or set the focus
> of the WindowsForms message box.  I fear the solution may be a little more
> complicated.
>
> Greetings
>
>
> 
> Von: Christopher Painter [chr...@deploymentengineering.com]
> Gesendet: Montag, 19. Juli 2010 18:18
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] Messagebox from custom action with a lot of text
>
> Where is this custom action scheduled?   I usually have a reusable dialog
> that
> contains an error property and then have my CA set the property and return.
> ControlEvents then detect the error property has data and do a SpawnDialog
> on
> the  generic error dialog and gate transition to the next dialog.
>
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> - Original Message 
> From: "daniel.knoep...@noser.com" 
> To: wix-users@lists.sourceforge.net
> Sent: Mon, July 19, 2010 10:55:12 AM
> Subject: [WiX-users] Messagebox from custom action with a lot of text
>
> Hi
>
> In our wix installer a C# custom action, needs to pop up a window to show a
> message that might be quite long.
> I currently do it the following way:
>
>
> public void ShowWarningMessageBox(string pMessage)
>
> {
>
>
>
> Record record = new Record();
>
> record.FormatString = pMessage;
>
> Session.Message(InstallMessage.Error |
> (InstallMessage)System.Windows.Forms.MessageBoxIcon.Warning |
>
> (InstallMessage)System.Windows.Forms.MessageBoxButtons.OK, record);
>
>
>
>
>
> Unfortunately, longer messages are not fully shown, only parts of it. Is
> there a
> way to ensure that the entire text is displayed?
>
>
>
> If somehow possible, i would like to stick with the Wix session.Message
> method,
> rather than using windows forms because of the focus. If somebody knows,
> how to
> ensure that the focus is set correctly in a windows forms message box, i
> would
> also happily go with that (preventing displaying a msgbox in silent mode is
> no
> problem as the uilevel property can be checked)
>
>
>
> Greetigns and thanks in advance
>
>
>
> Dan
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Supersede Patch

[James Poole]

This is more of a general MSI question...

Can a Patch that is NOT Uninstallable be superseded?

I seem to recall this being possible, but I am getting an error
"Uninstallation of the patch package is not supported" when I try to install
the second patch that supersedes the first.

Thanks,
James Poole
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] QuietExec in CA

[James Kessler]

Hi,

I'm getting the following build error when I try and use QuietExec in a C++
custom action:
"error LNK2001: unresolved external symbol _QuietExec"

I'm using WiX 3.0, dutil.lib and wcautil.lib are included my linker input.
What am I missing?

Thanks,
James
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] QuietExec in CA

[James Kessler]

I mean the QuietExec() function which is part of wcautil.lib. If I create a
new C++ custom action with

hr = QuietExec(pwzCommand, dwTimeout);

The compiler returns "unresolved external symbol _QuietExec". QuietExec is
defined in wcautil.h and  I'm successfully using other functions in the
wcautil library. I'm not sure if I'm missing a dependency or if something is
missing in the library.

Thanks for your help,
James


On Mon, Jul 26, 2010 at 7:56 PM, Elfe Xu  wrote:

>
> Do you mean QtExec ?
>
> http://wix.sourceforge.net/manual-wix3/qtexec.htm
> http://wix.sourceforge.net/manual-wix3/qtexec.htm
>
> In order to use QtExec, you must include a reference to the
> WixUtilExtension
> when building your MSI. To do this, add the command line argument -ext
> WixUtilExtension.dll when calling Light.exe.
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/QuietExec-in-CA-tp5339782p5340458.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] QuietExec in CA

[James Kessler]

Using WiX build 3.0.5419.0 and whatever wcautil.lib is included with that
package.


On Tue, Jul 27, 2010 at 11:45 AM, Blair  wrote:

> Which build of WiX are you using? Which wcautil lib are you linking with?
>
> -Original Message-
> From: James Kessler [mailto:kessl...@gmail.com]
> Sent: Tuesday, July 27, 2010 7:47 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] QuietExec in CA
>
> I mean the QuietExec() function which is part of wcautil.lib. If I create a
> new C++ custom action with
>
> hr = QuietExec(pwzCommand, dwTimeout);
>
> The compiler returns "unresolved external symbol _QuietExec". QuietExec is
> defined in wcautil.h and  I'm successfully using other functions in the
> wcautil library. I'm not sure if I'm missing a dependency or if something
> is
> missing in the library.
>
> Thanks for your help,
> James
>
>
> On Mon, Jul 26, 2010 at 7:56 PM, Elfe Xu  wrote:
>
> >
> > Do you mean QtExec ?
> >
> > http://wix.sourceforge.net/manual-wix3/qtexec.htm
> > http://wix.sourceforge.net/manual-wix3/qtexec.htm
> >
> > In order to use QtExec, you must include a reference to the
> > WixUtilExtension
> > when building your MSI. To do this, add the command line argument -ext
> > WixUtilExtension.dll when calling Light.exe.
> >
> > --
> > View this message in context:
> >
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/QuietExec-in-C
> A-tp5339782p5340458.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> >
>
> 
> --
> > The Palm PDK Hot Apps Program offers developers who use the
> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > of $1 Million in cash or HP Products. Visit us here for more details:
> > http://ad.doubleclick.net/clk;226879339;13503038;l?
> > http://clk.atdmt.com/CRS/go/247765532/direct/01/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> 
> --
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> --
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] QuietExec in CA

[James Kessler]

Thank you Blair, that resolved it. I filed bug to document the issue (ID:
3035649).


On Tue, Jul 27, 2010 at 5:43 PM, Blair  wrote:

> Looks to me like a bug. In your wcautil.h file, change the following:
>
> HRESULT QuietExec(
>__in_z LPWSTR wzCommand,
>__in DWORD dwTimeout
>);
>
> To:
> HRESULT WIXAPI QuietExec(
>__in_z LPWSTR wzCommand,
>__in DWORD dwTimeout
>);
>
> If that works, please file a bug against 3.0 (this issue is already fixed
> in
> 3.5) stating that the wcautil header file is missing the "WIXAPI" on the
> QuietExec() declaration. I'm not sure if that is a bad enough bug to spin a
> new build, but it should be documented so that others will know the
> workaround.
>
> -Original Message-
> From: James Kessler [mailto:kessl...@gmail.com]
> Sent: Tuesday, July 27, 2010 3:28 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] QuietExec in CA
>
> Using WiX build 3.0.5419.0 and whatever wcautil.lib is included with that
> package.
>
>
> On Tue, Jul 27, 2010 at 11:45 AM, Blair  wrote:
>
> > Which build of WiX are you using? Which wcautil lib are you linking with?
> >
> > -Original Message-
> > From: James Kessler [mailto:kessl...@gmail.com]
> > Sent: Tuesday, July 27, 2010 7:47 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] QuietExec in CA
> >
> > I mean the QuietExec() function which is part of wcautil.lib. If I create
> a
> > new C++ custom action with
> >
> > hr = QuietExec(pwzCommand, dwTimeout);
> >
> > The compiler returns "unresolved external symbol _QuietExec". QuietExec
> is
> > defined in wcautil.h and  I'm successfully using other functions in the
> > wcautil library. I'm not sure if I'm missing a dependency or if something
> > is
> > missing in the library.
> >
> > Thanks for your help,
> > James
> >
> >
> > On Mon, Jul 26, 2010 at 7:56 PM, Elfe Xu  wrote:
> >
> > >
> > > Do you mean QtExec ?
> > >
> > > http://wix.sourceforge.net/manual-wix3/qtexec.htm
> > > http://wix.sourceforge.net/manual-wix3/qtexec.htm
> > >
> > > In order to use QtExec, you must include a reference to the
> > > WixUtilExtension
> > > when building your MSI. To do this, add the command line argument -ext
> > > WixUtilExtension.dll when calling Light.exe.
> > >
> > > --
> > > View this message in context:
> > >
> >
> >
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/QuietExec-in-C
> > A-tp5339782p5340458.html
> > > Sent from the wix-users mailing list archive at Nabble.com.
> > >
> > >
> > >
> >
> >
>
> 
> > --
> > > The Palm PDK Hot Apps Program offers developers who use the
> > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > > of $1 Million in cash or HP Products. Visit us here for more details:
> > > http://ad.doubleclick.net/clk;226879339;13503038;l?
> > > http://clk.atdmt.com/CRS/go/247765532/direct/01/
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> >
>
> 
> > --
> > The Palm PDK Hot Apps Program offers developers who use the
> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > of $1 Million in cash or HP Products. Visit us here for more details:
> > http://ad.doubleclick.net/clk;226879339;13503038;l?
> > http://clk.atdmt.com/CRS/go/247765532/direct/01/
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> >
>
> 
> --
> > The Palm PDK Hot Apps Program offers developers who use the
> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > of $1 Million in cash or HP Products. Visit us here for more details:
> > http://ad.doubleclick.net/clk;226879339;13503038;l?
> > http://clk.atdmt.com/CRS/go/247765532/direct/01/
> &g

[WiX-users] ShortCuts Win 7

[James Green]

Hi All,

 

I've just followed this example
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm to the
letter in my own script but still no short cut.  Do I need to be doing
something else for this to work on Windows 7?

 

Thanks,

 

James


LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER
--
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] WIX Licensing

[James Poole]

I just sat through a meeting at my employer for the last 3 months (a
significantly large software company) who told me the CPL license WIX is
released under was too restrictive to allow me to use it as a development
tool.  Of course I just spent the last 2 months porting a horrific
InstallShield installer to WIX...

Is there any chance this license will ever get updated to a more recent open
source license (CPL is sooo 2001).

Or is there any way for me to purchase WIX under a different license?
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WIX Licensing

[James Poole]

Apparently my company is OK with the Eclipse Public License but not the
Common Public License, and the only change between the two is the removal of
this sentence in section 7:

*"If Recipient institutes patent litigation against a Contributor with
respect to a patent applicable to software (including a cross-claim or
counterclaim in a lawsuit), then any patent licenses granted by that
Contributor to such Recipient under this Agreement shall terminate as of the
date such litigation is filed."

*Other companies apparently did have issues with this part of the CPL which
is why the Eclipse foundation created an updated version.

My question is this:

Is Microsoft still the ultimate decision maker when it comes to what license
this is released under?  What would the process be for having this get
released under a newer open source license?

-James

On Wed, Aug 25, 2010 at 5:19 PM, Christopher Painter <
chr...@deploymentengineering.com> wrote:

> That's interesting.  I also work for a very large software company and we
> have
> a highly formal process for evaluating tools with a group of people that
> study
> these things in extreme detail and while I did have to jump through some
> compliance hoops  ( for example we did Fortify security scans and I had to
> track
> down any false positives with the  help of Rob to justify the alerts )
> nobody
> made any such statement about the EULA.  I'm suspecting the person who made
> this
> decision is misinformed but unless we know there exact complaints it's hard
> to
> address them.
>
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> - Original Message 
> From: James Poole 
> To: General discussion for Windows Installer XML toolset.
> 
> Sent: Wed, August 25, 2010 2:20:37 PM
> Subject: [WiX-users] WIX Licensing
>
> I just sat through a meeting at my employer for the last 3 months (a
> significantly large software company) who told me the CPL license WIX is
> released under was too restrictive to allow me to use it as a development
> tool.  Of course I just spent the last 2 months porting a horrific
> InstallShield installer to WIX...
>
> Is there any chance this license will ever get updated to a more recent
> open
> source license (CPL is sooo 2001).
>
> Or is there any way for me to purchase WIX under a different license?
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question about using XmlFile (WixUtilExtension.dll in general, actually)

[James Kessler]

Are you referencing the dll in your Visual Studio project?


On Thu, Aug 26, 2010 at 3:29 PM, Dave DaveLists  wrote:

> Thanks for the response Chad. I do indeed have the xmlns:util setup at
> the top of my WIX source file. Do you use WIX 3.0 or 3.5? We moved to
> Visual Studio 2010 with WIX 3.5, but interestingly enough a machine
> that still has Visual 2008 and WIX 3.0 works fine with the same code
> (XmlFile and all).
>
> -Dave
>
> On Thu, Aug 26, 2010 at 11:42 AM, Chad Petersen
>  wrote:
> > Try adding the xmlns:util="
> http://schemas.microsoft.com/wix/UtilExtension"; schema to the top of the
> file that has the XmlFile element in it.
> >
> > Mine looks like this
> >
> > http://www.w3.org/2001/XMLSchema-instance"; xmlns="
> http://schemas.microsoft.com/wix/2006/wi"; xmlns:util="
> http://schemas.microsoft.com/wix/UtilExtension";>
> >
> > -Original Message-
> > From: Dave DaveLists [mailto:dbfli...@gmail.com]
> > Sent: Wednesday, August 25, 2010 8:50 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Question about using XmlFile
> (WixUtilExtension.dll in general, actually)
> >
> > Ah, yes, sorry. It is a wix compiler error:
> >
> > The Component element contains an unhandled extension element
> > 'util:XmlFile'.  Please ensure that the extension for elements in the
> > 'http:⁄⁄schemas.microsoft.com⁄wix⁄UtilExtension' namespace has been
> > provided.
> >
> > I googled this line and found a few references to it but the
> > suggestion was always to add a reference to WixUtilExtension.dll,
> > which we already have. We tried deleting it and putting it back in
> > manually but this did not help (and I verified that the DLL is in the
> > directory where candle and light are, just to be sure).
> >
> > Thanks,
> >
> > -Dave
> >
> > On Tue, Aug 24, 2010 at 6:16 PM, Bob Arnson  wrote:
> >>  On 24-Aug-10 21:00, Dave DaveLists wrote:
> >>> we expected to be able to reference XmlFile using util:XmlFile but
> >>> this is failing at compile time.
> >>
> >> It might help if you described how it was failing...
> >>
> >> --
> >> sig://boB
> >> http://joyofsetup.com/
> >>
> >>
> >>
> --
> >> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> >> Be part of this innovative community and reach millions of netbook users
> >> worldwide. Take advantage of special opportunities to increase revenue
> and
> >> speed time-to-market. Join now, and jumpstart your future.
> >> http://p.sf.net/sfu/intel-atom-d2d
> >> ___
> >> WiX-users mailing list
> >> WiX-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>
> >
> >
> --
> > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> > Be part of this innovative community and reach millions of netbook users
> > worldwide. Take advantage of special opportunities to increase revenue
> and
> > speed time-to-market. Join now, and jumpstart your future.
> > http://p.sf.net/sfu/intel-atom-d2d
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> --
> > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> > Be part of this innovative community and reach millions of netbook users
> > worldwide. Take advantage of special opportunities to increase revenue
> and
> > speed time-to-market. Join now, and jumpstart your future.
> > http://p.sf.net/sfu/intel-atom-d2d
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-use

[WiX-users] Using a Custom Action dll in another solution

[James Green]

Hi All,

 

I created a Custom Action dll (.NET) for a test solution.  In this solution
I have the CA project, a simple test app project and a WiX setup project.
This works fine.  I'm now trying to take the CA dll produced by this test
solution into our live project.  I've copied both dlls (the Deploy.dll and
Deploy.CA.dll) in the live projects Libs folder and tried to add a reference
to it in the WiX project in this solution.  It just errors with the
following message:

 

"A reference to [path to Dll] could not be added. Please make sure that the
file is accessible, and that it is a valid WiX reference."

 

There isn't any reason it won't be accessible so I can only assume that
there is something wrong with the dll and it's not being recognised as a WiX
reference.  What should I be doing to fix this?  And why would it work fine
when used from within the same solution but fail when added to a different
solution?  Very confusing ...

 

Thanks in advance,

 

James


LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using WixUI_InstallDir

[James Green]

Hi All,

 

I need to disable the Repair & Change options in an installer I'm working
on.  However, when I enter these setting in my Product.wxs file WiX throws a
wobbly as these are already defined in the WixUI_InstallDir code.

 

Whats the best way to tackle this situation?  Can I get at the code inside
WixUI_InstallerDir?

 

TIA,

 

James


LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understood as neither 
given nor endorsed by it or on its behalf, and consequently LalPac Ltd shall 
bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and 
are believed to be free of viruses but it is your responsibility to carry out 
all necessary virus checks and LalPac Ltd accepts no liability in connection 
therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a 
satisfactory level of customer service is maintained, to maintain Company 
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using WixUI_InstallDir

[James Green]

Fantastic!  All fixed ... now to try and deal with the right click - Repair
option ... hmm ...

Thanks Blair,

James

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Blair
Sent: 24 November 2010 02:16
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using
WixUI_InstallDir

ARPNOMODIFY is already set for WixUI_InstallDir since that dialog set
doesn't include any feature selection dialog (so there isn't any point in
allowing "Change"). However, I don't see ARPNOREPAIR being set there. You
should be able to set that one property and trust the other one is set.

The code for WixUI_InstallDir is found in the src\ext\UIExtension\wixlib
folder in the WixUI_InstallDir.wxs file.

-----Original Message-
From: James Green [mailto:james.gr...@lalpac.com] 
Sent: Tuesday, November 23, 2010 9:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using
WixUI_InstallDir

Hi All,

 

I need to disable the Repair & Change options in an installer I'm working
on.  However, when I enter these setting in my Product.wxs file WiX throws a
wobbly as these are already defined in the WixUI_InstallDir code.

 

Whats the best way to tackle this situation?  Can I get at the code inside
WixUI_InstallerDir?

 

TIA,

 

James


LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this
e-mail.

Opinions advice, conclusions and other information in this message that do
not relate to the official business of LalPac Ltd shall be understood as
neither given nor endorsed by it or on its behalf, and consequently LalPac
Ltd shall bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software and
are believed to be free of viruses but it is your responsibility to carry
out all necessary virus checks and LalPac Ltd accepts no liability in
connection therewith.

The Company actively monitors all incoming and outgoing e-mails to ensure a
satisfactory level of customer service is maintained, to maintain Company
security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support: +44 
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If an addressing or transmission error has misdirected this e-mail, please 
notify the author by replying to this e-mail. If you are not the intended 
recipient you may not use, disclose, distribute, copy, print or rely on this 
e-mail.

Opinions advice, conclusions and other information in this message that do not 
relate to the official business of LalPac Ltd shall be understoo

Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFYWhilst using WixUI_InstallDir

[James Green]

Thanks for that Palbinder!

James

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Pally Sandher
Sent: 24 November 2010 11:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFYWhilst using
WixUI_InstallDir

Add a LaunchCondition which checks the REINSTALLMODE property is not set
but make sure you test patching/upgrading if you're going to be shipping
MSP's and/or major upgrades in the future as they set it too IIRC.

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-Original Message-----
From: James Green [mailto:james.gr...@lalpac.com] 
Sent: 24 November 2010 09:22
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFYWhilst using
WixUI_InstallDir

Fantastic!  All fixed ... now to try and deal with the right click -
Repair option ... hmm ...

Thanks Blair,

James

-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Blair
Sent: 24 November 2010 02:16
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using
WixUI_InstallDir

ARPNOMODIFY is already set for WixUI_InstallDir since that dialog set
doesn't include any feature selection dialog (so there isn't any point
in allowing "Change"). However, I don't see ARPNOREPAIR being set there.
You should be able to set that one property and trust the other one is
set.

The code for WixUI_InstallDir is found in the src\ext\UIExtension\wixlib
folder in the WixUI_InstallDir.wxs file.

-Original Message-
From: James Green [mailto:james.gr...@lalpac.com]
Sent: Tuesday, November 23, 2010 9:24 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting ARPNOREPAIR/ARPNOMODIFY Whilst using
WixUI_InstallDir

Hi All,

 

I need to disable the Repair & Change options in an installer I'm
working on.  However, when I enter these setting in my Product.wxs file
WiX throws a wobbly as these are already defined in the WixUI_InstallDir
code.

 

Whats the best way to tackle this situation?  Can I get at the code
inside WixUI_InstallerDir?

 

TIA,

 

James


LalPac Limited registered in England No: 4211747

Partner in Licensing to over 120 UK local government authorities.

Temple Court, 8 The Causeway, Chippenham, Wiltshire, SN15 3BT, UK.
Tel: +44 (0)1249 660088Fax: +44 (0)1249 660099 - Technical Support:
+44
(0)1249 462542
Web: www.lalpac.com - Email: i...@lalpac.com

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. 
If an addressing or transmission error has misdirected this e-mail,
please notify the author by replying to this e-mail. If you are not the
intended recipient you may not use, disclose, distribute, copy, print or
rely on this e-mail.

Opinions advice, conclusions and other information in this message that
do not relate to the official business of LalPac Ltd shall be understood
as neither given nor endorsed by it or on its behalf, and consequently
LalPac Ltd shall bear no responsibility whatsoever in respect thereof.

This e-mail and any attachments have been checked by anti-virus software
and are believed to be free of viruses but it is your responsibility to
carry out all necessary virus checks and LalPac Ltd accepts no liability
in connection therewith.

The Company actively monitors all incoming and outgoing e-mails to
ensure a satisfactory level of customer service is maintained, to
maintain Company security, and to prevent abuse of the Company systems.

Please do not print this e-mail unless absolutely necessary - SAVE PAPER


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for
grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your gam

[WiX-users] DIFxApp and upgrades

[James Johnston]

Hi,

A couple questions, both regarding DIFxApp.  (We use it to install three
drivers for three plug-and-play USB devices for a hardware product that we
ship.)

1.  Some time ago Rob Mensching mentioned the following on this list:

"Yeah, there are some design issues in the DIFxApp code around Upgrades I'm
still trying to figure out what to do with DIFx since we don't have the code
to fix it here. I'll try to find someone to forward this thread to see if we
can't get some movement (not that it has worked yet)."
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg35219.html

I am very interested in knowing whether anybody here knows what some of
these design issues might be?  Can DIFxApp be used when an application must
be serviced in the future?  I looked through MSDN and did not find any
mention one way or the other regarding DIFxApp and upgrades.  If upgrades
are not supported (which would seem like a serious deficiency!), what is the
recommended way of servicing an app that uses DIFxApp?  Just what, exactly,
are the caveats involved with upgrades and DIFx?

The reason I ask is that upgrades are not going as well as we would like.
Currently we service our application very simply.  Every new version is a
major upgrade: new product code, new version number.  We have always
scheduled RemoveExistingProducts immediately after InstallInitialize.  We
have tested this in-house on just about every computer at our (small)
company without any issue: the upgrades generally go very smoothly.
Additionally, most of our customers have also done upgrades without issue.

However, there have been a few customers (i.e. about 10: enough for us to
not consider it to be an isolated incident) where they were unable to
upgrade.  The setup program will roll back and fail when upgrading.  Also,
they are then unable to uninstall the software: again, the setup program
rolls back when attempting to remove the product.  The MSI logs always point
to DIFx as the problem, with DIFx indicating that key DIFx information in
the registry is missing.  Searching Google seems to indicate that we may not
be the only people experiencing this issue.  The problem has been observed
on both Windows XP SP3 and Windows 7 (few customers use Vista).  Every setup
package uses the version of DIFx included with WiX 3.0 (I believe it's
version 2.1.1).

In order to get the customer working again, we have successfully used the
following workaround in every case: (1) delete the key file as specified by
the driver component, (2) do a repair of the existing product; the absence
of the key file triggers MSI/DIFx to successfully install the driver again,
(3) we can now uninstall the old product/MSI, (4) the new product/MSI can be
installed.  Unfortunately, we have not been able to reproduce the problem
locally.  That also means that we (obviously) haven't identified what it is
about the customer computer that causes problems. 

2.  The second question is also related to upgrades.  This one is easily
reproducible.  The problem is that the connected USB device is completely
removed from Device Manager after the upgrade, and does not reappear until
the "Scan for hardware changes" button in Device Manager is clicked.  What
seems to happen is the following:

a.  As part of the major upgrade, the old driver is uninstalled.  At this
time, the device is completely removed from Device Manager (like if I
right-clicked it and said to uninstall it).
b.  The new driver is installed, but does not install/upgrade any driver for
the connected device because it is no longer enumerated in Device Manager.
(i.e. DIFx does not think any such device is connected & needs setup).
c.  Of course, the user proceeds to use our application, and wonders why the
hardware device is no longer found.
d.  Clicking the "Scan for hardware changes" button in Device Manager (or
rebooting) will enumerate the USB device and load the appropriate drivers
from DIFx.  At this point, our application will work again.

It seems like this must be an extremely common occurrence with other
plug-and-play widgets that use DIFxApp and need upgrading.  I can easily
enough add a custom action at the end of setup that calls the
CM_Reenumerate_DevNode API (see http://support.microsoft.com/kb/259697).
But given the fact that this seems like it should be a common situation: is
this the recommended way to handle this?  What is the best practice to use
in this scenario?  Does a custom action already exist for this?  Am I doing
something wrong with DIFx (i.e. do I need to change my usage of DIFx instead
of write a custom action)?

If anyone has so much as even heard of either of the issues above, I would
be grateful for some advice or pointers in the right direction.

Best regards,

James Johnston



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Ta

[WiX-users] DIFxApp and upgrades

[James Johnston]

Hi,

A couple questions, both regarding DIFxApp.  (We use it to install three
drivers for three plug-and-play USB devices for a hardware product that we
ship.)

1.  Some time ago Rob Mensching mentioned the following on this list:

"Yeah, there are some design issues in the DIFxApp code around Upgrades I'm
still trying to figure out what to do with DIFx since we don't have the code
to fix it here. I'll try to find someone to forward this thread to see if we
can't get some movement (not that it has worked yet)."
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg35219.html

I am very interested in knowing whether anybody here knows what some of
these design issues might be?  Can DIFxApp be used when an application must
be serviced in the future?  I looked through MSDN and did not find any
mention one way or the other regarding DIFxApp and upgrades.  If upgrades
are not supported (which would seem like a serious deficiency!), what is the
recommended way of servicing an app that uses DIFxApp?  Just what, exactly,
are the caveats involved with upgrades and DIFx?

The reason I ask is that upgrades are not going as well as we would like.
Currently we service our application very simply.  Every new version is a
major upgrade: new product code, new version number.  We have always
scheduled RemoveExistingProducts immediately after InstallInitialize.  We
have tested this in-house on just about every computer at our (small)
company without any issue: the upgrades generally go very smoothly.
Additionally, most of our customers have also done upgrades without issue.

However, there have been a few customers (i.e. about 10: enough for us to
not consider it to be an isolated incident) where they were unable to
upgrade.  The setup program will roll back and fail when upgrading.  Also,
they are then unable to uninstall the software: again, the setup program
rolls back when attempting to remove the product.  The MSI logs always point
to DIFx as the problem, with DIFx indicating that key DIFx information in
the registry is missing.  Searching Google seems to indicate that we may not
be the only people experiencing this issue.  The problem has been observed
on both Windows XP SP3 and Windows 7 (few customers use Vista).  Every setup
package uses the version of DIFx included with WiX 3.0 (I believe it's
version 2.1.1).

In order to get the customer working again, we have successfully used the
following workaround in every case: (1) delete the key file as specified by
the driver component, (2) do a repair of the existing product; the absence
of the key file triggers MSI/DIFx to successfully install the driver again,
(3) we can now uninstall the old product/MSI, (4) the new product/MSI can be
installed.  Unfortunately, we have not been able to reproduce the problem
locally.  That also means that we (obviously) haven't identified what it is
about the customer computer that causes problems. 

2.  The second question is also related to upgrades.  This one is easily
reproducible.  The problem is that the connected USB device is completely
removed from Device Manager after the upgrade, and does not reappear until
the "Scan for hardware changes" button in Device Manager is clicked.  What
seems to happen is the following:

a.  As part of the major upgrade, the old driver is uninstalled.  At this
time, the device is completely removed from Device Manager (like if I
right-clicked it and said to uninstall it).
b.  The new driver is installed, but does not install/upgrade any driver for
the connected device because it is no longer enumerated in Device Manager.
(i.e. DIFx does not think any such device is connected & needs setup).
c.  Of course, the user proceeds to use our application, and wonders why the
hardware device is no longer found.
d.  Clicking the "Scan for hardware changes" button in Device Manager (or
rebooting) will enumerate the USB device and load the appropriate drivers
from DIFx.  At this point, our application will work again.

It seems like this must be an extremely common occurrence with other
plug-and-play widgets that use DIFxApp and need upgrading.  I can easily
enough add a custom action at the end of setup that calls the
CM_Reenumerate_DevNode API (see http://support.microsoft.com/kb/259697).
But given the fact that this seems like it should be a common situation: is
this the recommended way to handle this?  What is the best practice to use
in this scenario?  Does a custom action already exist for this?  Am I doing
something wrong with DIFx (i.e. do I need to change my usage of DIFx instead
of write a custom action)?

If anyone has so much as even heard of either of the issues above, I would
be grateful for some advice or pointers in the right direction.

Best regards,

James Johnston


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Ta

Re: [WiX-users] DIFxApp and upgrades

[James Johnston]

In response to #2:  It looks like you are using the same / similar hardware
that we do.  We also use an FTDI product (FT232R).  However, there are some
differences:

(a)  We use our own product code so as not to mix the device up with normal
FTDI devices.

(b)  As a consequence, we renamed and modified the standard INF files while
following the documented FTDI procedures for doing so.  The result has not
yet been signed.

(c)  Our WiX fragment is nearly identical to yours.  The DIFxApp element is
as follows:



The key differences between our elements seems to be "ForceInstall"
attribute and "AddRemovePrograms" attribute.  Also the use of the Legacy
attribute.  Did you find these made much of a difference?  Reading the
MsiDriverPackages table documentation, I can't imagine it would:
http://msdn.microsoft.com/en-us/library/ff549362(VS.85).aspx.

ForceInstall "configures DIFxApp to force the installation of a new PnP
function driver on a device, even if the driver that is currently installed
on a device is a better match than the new driver" so did not seem to be
desirable.  Also it doesn't seem like it would be applicable in this case,
since the sequence is uninstall then reinstall (i.e. when installing, no
driver is installed at all so the value of ForceInstall would be ignored?)

The one reason I have read for having AddRemovePrograms="yes" is so that the
driver can be removed from Safe Mode (apparently MSI can't be invoked from
Safe Mode).  Is this still good advice?  Otherwise it just seems like
unnecessary clutter in ARP.

DeleteFiles="no" is the default; I included it anyway just to be explicit.
Documentation says it's not supported any more on Windows 7...

Best regards,

James Johnston

-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com] 
Sent: Monday, November 29, 2010 22:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp and upgrades

2. I do not see the second problem at all with our driver install. Any
devices that are plugged in are "immediately" available with the new drivers
after the install completes. In rare cases the user will be asked to restart
the PC. Are your drivers digitally signed? Here is what our WiX looks like
for the DifxAppExtension component. I did have to play around with the the
DIFxApp options (now encoded in the difxns:Driver element) back when we
first developed the driver to get the behavior I wanted.



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFxApp and upgrades

[James Johnston]

Perhaps you are right about the legacy="true" aspect and the need to
manually scan for new hardware after an upgrade if the device was plugged
in.  At any rate, for the moment - I already added a custom action that
follows MSKB http://support.microsoft.com/kb/259697 and placed it after
MsiProcessDrivers; it seems to have fixed the problem.  If/when I get signed
FTDI drivers then I'll see if removing the CA doesn't reintroduce the
problem.  (Your costs are $200 per driver signing plus the cost of the code
signing certificate?)

Since you also experience the rollback problem and use signed drivers, I
assume it is not related to having unsigned drivers.  So it sounds to me
like there is probably some bug in DIFxApp... ick.  (Wishing DIFx was open
source right now!)

I certainly feel your pain regarding bugs with FTDI.  Before the 2.04.06
driver - released 3/13/2008 - the FTDI driver would randomly lock up the
computer on multiprocessor systems.  Not like dual-core/hyper-threaded
systems didn't exist for years before then, let alone dual-processor systems
which are even older (but probably less common for FTDI's market)...  The
really fun thing is that last I checked they still hadn't updated Windows
Update with that driver (when using default VID/PID), so the unsuspecting
user who just lets Windows find the appropriate driver automatically for
their generic USB-to-serial dongle will end up with a system that randomly
freezes.  I guess they are too busy making high-speed USB versions of their
devices!  But, I haven't really seen any comparable products that are
carried by distributors like Digikey.  It seems like FTDI is one of the most
common choices for low-volume USB.

I did just check and Microchip seems to be getting into this market with the
MCP2200 that came out earlier this year.  It's less expensive than FT232R
but it needs an external crystal.  What's more fun is that nothing is WHQL
signed; in fact the "driver" consists of a single INF file that uses the
Microsoft usbser.sys.  It's not WHQL signed.  It sounds like it's a
composite device that is a CDC for the COM port provided via usbser.sys, and
an HID device for everything else.  Probably the HID is used for configuring
EEPROM, GPIO port, things like that; a provided DLL file interfaces with it
for doing those chip-specific tasks but it does not work with the UART.  I
don't see anything close to what FTDI has: no similar replacement for the
D2XX API (which allows customizing some of the USB parameters) and no
Microchip-provided SYS file for a driver.  My recollection is that the
Microsoft driver is buggy, too. 

James 

-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com] 
Sent: Tuesday, November 30, 2010 21:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp and upgrades

We use the FT245BM. We use our own PID and have a resold driver, but we kept
the filenames the same since they didn't support it. We have certified the
resold driver updated for our VID/PID.

I would not be surprised if what you're seeing (issue #2) is related to the
driver not being signed. I have generally just done the driver reseller
thing followed by a DUA submission just to get a driver that is fully
qualified and installs normally, then I do my testing on the driver and then
choose to either use or not use it. Each of the reseller and DUA steps cost
$100 each and only takes a few hours, and it seemed worth the cost of not
fussing quasi-signed drivers.

In terms of the Driver attributes:
(1) AddRemovePrograms="no" - I turned this off to keep it simple for the
user. Didn't consider the Safe Mode. Also, I think the problems with the
Driver store getting corrupted like you describe and goofing up
update/uninstall of our app may have contributed to trying to only have one
path for removal (uninstall the app).
(2) ForceInstall="yes" - I don't recall if there was a specific problem this
worked around. I wanted my app to determine the drivers that are used with
our VID/PID and therefore thought this would give us a better chance of
that. May have been related to paranoia about product updates failing.
(3) Legacy="no" - since I have signed drivers, I didn't need to allow legacy
drivers. Things weren't pretty when the drivers weren't signed, but I don't
remember the specifics.

As an aside, I haven't seen a viable FTDI driver since 2.04.16. The 2.06.x
one required safe removal, and the 2.08.2 one has some serious bugs on
32-bit Win7 and perhaps Vista. I'm currently fussing with trying to get back
to the 2.04.16 driver, since we didn't catch the 2.8.2 flakies until after
release. This is what is behind
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg42650.htm
l.

--Quinton

-Original Message-
From: James Johnston [mailto:j

Re: [WiX-users] Saving the MSI file

[James Johnston]

I thought about this but decided against it for some of the security reasons
you outline; I did not think it appropriate for the UAC prompt to appear
immediately upon running the bootstrapper.  The UAC prompt really should not
be presented until the user clicks the "Install" button in the UI to
actually start the installation.  This would be after they configured all
the features, etc.  They should not have a UAC prompt when invoking the
boot-strapper.  I know a lot of apps out there don't bother and just require
the boot-strapper to elevate; I suspect a lot of them don't even have
appropriate manifest resources.  It comes across as a little sloppy to me.

Also, you are hosed if someone invokes the MSI directly without using the
bootstrapper.  In my book, the MSI needs to work properly if invoked
directly.  If other prereqs installed by the bootstrapper are needed, then I
check for them via launch conditions to prevent installing if a needed
prereq isn't found.

The real problem is that MSI was designed for installing off of a CD (Office
2000) back when copying resources like this were unthinkable due to limited
hard drive space.  I wish Microsoft would address this shortcoming; you'd
think they could add a pre-defined property or table  (i.e. declarative,
simple, easy-to-understand-and-use method) that controls caching the MSI
file.  Instead everybody does it their own way and now we have this big
mess.

The solution I used was to create a component for the MSI like this:







Basically, use a zero-length file as the key and use CopyFile/RemoveFile
elements to cache the actual MSI.  SetupCache is a subdirectory underneath
the application.  Make additional similar components for other files needing
to be cached; in my case there were external CAB files to cache as well.
(If your MSI is of significant size then this is best; see
http://blogs.msdn.com/b/heaths/archive/2009/02/02/changes-to-package-caching
-in-windows-installer-5-0.aspx).

For MSI to actually use this SetupCache directory, add a custom action.  I
used a deferred action placed after PublishProduct.  This action calls
MsiSourceListAddSource to add the setup cache as a source.  Condition for
the action is that "$MYAPPMSI = 3" to avoid running on uninstall.

This has seemed to work reasonably well, although there must be a case
somehow where the MSI files themselves are left behind.  I haven't figured
out why yet, but usually the RemoveFile deletes them as expected.  Hasn't
been high priority to isolate the reason why and fix it.

James

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: Tuesday, November 30, 2010 22:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Saving the MSI file

Well, that could happen no matter where you put it.  InstallShield puts it
in [LocalAppDataFolder]\Downloaded Installations by default but I'm not sure
I agree with that.   They do this ( as I recall ) so that a setup.exe
manifested as Invoker could cache the file for a standard user.  Problem
(IMO) is that if this then elevates and gets installed for all-users it
becomes a managed installation and that user who cached it could then tamper
with the MSI and do a repair to inject untrusted code into the installer. 
Remote, but possible.

The used to cache it in [WindowsFolder]Downloaded Installations but that
required Admin privs.  I think personally I've
used [CommonAppDataFolder]Downloaded Installations before.  When I need a
setup.exe I typically manifest it as requireAdmin so that each of my prereqs
don't require elevation.  I've read that this isn't the best practice but I
really don't like the alternatives.

I've also written some code that's used during major upgrades to delete the
previous versions of the MSI that way they don't pile up into something
huge. I usually just leave the final MSI behind on uninstall as the size is
typically quite small.

I'd look at WiX 3.6 and see what approaches Rob is taking with Burn. 
 
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip,
know a secret or read a really good thread that deserves attention? E-Mail
Me



- Original Message 
From: Quinton Tormanen 
To: General discussion for Windows Installer XML toolset. 

Sent: Tue, November 30, 2010 4:10:52 PM
Subject: Re: [WiX-users] Saving the MSI file

Where do you cache it to? Everywhere else I thought of won't get cleaned up 
and/or might get erased prematurely (e.g. TMP folder).

--Quinton

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: Tuesday, November 30, 2010 2:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Saving the MSI file

I usually just let my boot

Re: [WiX-users] Registry Question...

[James Johnston]

Familiarize yourself with
http://msdn.microsoft.com/en-us/library/ms724072(VS.85).aspx

If you don't want your entry to go in the 32-bit entry then you have to
specify Win64="yes" on your component, but this makes / requires your MSI to
be supporting 64-bit.

32-bit apps don't need to worry about Wow6432Node; if your scripts are also
32-bit you should have nothing to worry about.

-Original Message-
From: John D. Marinuzzi [mailto:nu...@hypack.com] 
Sent: Wednesday, December 01, 2010 13:09
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry Question...

I am using a 64-bit Windows 7 machine.  I am installing our software with
the following script for the registry:

 

  



  

  



  

 

On the 64 bit machine the registry value is coming back as:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\My Company

 

Why the Wow6432?

 

We have some NSIS scripts to install some files after the fact.  I assume it
will not be able to find the key if I use:

 

HKEY_LOCAL_MACHINE\SOFTWARE\My Company

 

For the path in the script.

 

Thanks,

 

John

 

 

 


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Saving the MSI file

[James Johnston]

Eeesh, that's a ton of prereqs!  Indeed, in your case 20 UAC prompts would
be unacceptable.  I do wonder how you wound up with a 30 second timeout?
(What if installing on a slower computer and the prereq takes more time to
load?)

Our product's only chained prereq is .NET Framework 2.0, so we just use the
Visual Studio bootstrapper.  By sticking to only the NETFX 2.0 features it
allows us to jump straight into the MSI on Windows Vista/7.  Windows XP
users have only the 20-something megabyte download to contend with.  All the
other dependencies are handled via merge module (VC++2003/2005/2008, and
some 3rd-party libs as well).

I'd imagine introducing things like SQL Server Express, etc. complicates
things a good bit more.  You're right that the chaining situation is messy.
Just look at Add/Remove Programs these days if anyone says otherwise.

James

-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com] 
Sent: Wednesday, December 01, 2010 20:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Saving the MSI file

My typical bootstrapper installs between 10 and 20 prereqs.  I can't imagine
each of those packages prompting for elevation.  If you don't answer in 30
seconds or so it'll fail and the whole chain is broken.  I don't see how I
can't elevate up front.  I also do matching LaunchConditions in my MSI
to make sure the bootstrapper did it's thing. 


You are right about the caching only I'll take it one step farther.  The
multiple package per transaction story doesn't fit industry needs.  It
assumes that all of your packages are MSI and that's simply not the case for
me.  Heck, many/most things I download from MSFT (  .NET, C++, SQL so on )
are EXE's not MSI's.

So sure, I'd love to just click on an MSI, do my feature selection then
elevate and chain all my MSI's together but it's just not an option for me.

Chris
 
Christopher Painter, Author of Deployment Engineering Blog Have a hot tip,
know a secret or read a really good thread that deserves attention? E-Mail
Me



- Original Message 
From: James Johnston 
To: General discussion for Windows Installer XML toolset. 

Sent: Wed, December 1, 2010 1:36:12 PM
Subject: Re: [WiX-users] Saving the MSI file

I thought about this but decided against it for some of the security reasons
you outline; I did not think it appropriate for the UAC prompt to appear
immediately upon running the bootstrapper.  The UAC prompt really should not
be presented until the user clicks the "Install" button in the UI to
actually start the installation.  This would be after they configured all
the features, etc.  They should not have a UAC prompt when invoking the
boot-strapper.  I know a lot of apps out there don't bother and just require
the boot-strapper to elevate; I suspect a lot of them don't even have
appropriate manifest resources.  It comes across as a little sloppy to me.

Also, you are hosed if someone invokes the MSI directly without using the
bootstrapper.  In my book, the MSI needs to work properly if invoked
directly.  If other prereqs installed by the bootstrapper are needed, then I
check for them via launch conditions to prevent installing if a needed
prereq isn't found.

The real problem is that MSI was designed for installing off of a CD (Office
2000) back when copying resources like this were unthinkable due to limited
hard drive space.  I wish Microsoft would address this shortcoming; you'd
think they could add a pre-defined property or table  (i.e. declarative,
simple, easy-to-understand-and-use method) that controls caching the MSI
file.  Instead everybody does it their own way and now we have this big
mess.

The solution I used was to create a component for the MSI like this:

                
                    
                    
                    
                

Basically, use a zero-length file as the key and use CopyFile/RemoveFile
elements to cache the actual MSI.  SetupCache is a subdirectory underneath
the application.  Make additional similar components for other files needing
to be cached; in my case there were external CAB files to cache as well.
(If your MSI is of significant size then this is best; see
http://blogs.msdn.com/b/heaths/archive/2009/02/02/changes-to-package-caching
-in-windows-installer-5-0.aspx).

For MSI to actually use this SetupCache directory, add a custom action.  I
used a deferred action placed after PublishProduct.  This action calls
MsiSourceListAddSource to add the setup cache as a source.  Condition for
the action is that "$MYAPPMSI = 3" to avoid running on uninstall.

This has seemed to work reasonably well, although there must be a case
somehow where the MSI files themselves are left behind.  I haven't figured
out why yet, but usually the RemoveFile deletes them as expected.  H

Re: [WiX-users] cabbing for both 32-64-bit files

[James Johnston]

I wanted a unified self-extracting EXE for both 32- and 64-bit versions.
What I wound up doing was this:

1.  The build script combined with WiX conditional compilation /
preprocessor was used to compile to two different MSI files: one 32-bit and
one 64-bit.  Each was compiled individually.  (For example, 32-bit MSI has a
launch condition preventing use on 64-bit Windows).
2.  Files that are shared go into a common external cabinet file.  Because
they are shared, each variation of the build script compile/link should
produce the same CAB file.  I use a diff command just to make sure this is
the case before merging the 32-bit and 64-bit build output directories.
3.  Files that are not shared go into two cabinets: one for 32-bit files to
go with 32-bit MSI, and one for 64-bit files to go with 64-bit MSI.  Again,
the preprocessor is used to make this happen.

The final layout looks something like:
MyApp.cab
MyApp_x64.cab
MyApp_x86.cab
MyApp_x64.msi
MyApp_x86.msi

In my case, the application is 32-bit but I had to split the install like
this due to driver-related reasons.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Thursday, December 02, 2010 19:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] cabbing for both 32-64-bit files

Hi:
I'm currently building an instasllation that will eventually go on to 32 and
64 bit machines.How would people handle the fact that I have some files only
referenced by either the 32-bit/64-bit install (mainly com servers) and then
other files referenced by both. Should I use separate cab files?
Cheers
Sean.

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] cabbing for both 32-64-bit files

[James Johnston]

Right; it comes in a self-extracting EXE that then launching the VS2008
bootstrapper.  The generated VS2008 bootstrapper EXEs have the MSI name
embedded in them so there are two VS2008 bootstrapper EXEs: one for each
MSI.  I wrote a custom program in C that the self-extracting EXE launches.
This app determines which VS2008 bootstrapper EXE to start based on the
platform.  Also it moves the setup files to a different temp directory to
avoid trying to delete setup files that are still in use (see issue where
VS2008 bootstrapper returns immediately instead of waiting for the app to
finish installing).

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Friday, December 03, 2010 05:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Hi James:
Thanks for this, I'm assuming you then used a bundle to deal with the
extraction/running the msi?
Cheers
Sean.
-Original Message-
From: James Johnston [mailto:johnst...@inn-soft.com]
Sent: 02 December 2010 22:01
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

I wanted a unified self-extracting EXE for both 32- and 64-bit versions.
What I wound up doing was this:

1.  The build script combined with WiX conditional compilation /
preprocessor was used to compile to two different MSI files: one 32-bit and
one 64-bit.  Each was compiled individually.  (For example, 32-bit MSI has a
launch condition preventing use on 64-bit Windows).
2.  Files that are shared go into a common external cabinet file.  Because
they are shared, each variation of the build script compile/link should
produce the same CAB file.  I use a diff command just to make sure this is
the case before merging the 32-bit and 64-bit build output directories.
3.  Files that are not shared go into two cabinets: one for 32-bit files to
go with 32-bit MSI, and one for 64-bit files to go with 64-bit MSI.  Again,
the preprocessor is used to make this happen.

The final layout looks something like:
MyApp.cab
MyApp_x64.cab
MyApp_x86.cab
MyApp_x64.msi
MyApp_x86.msi

In my case, the application is 32-bit but I had to split the install like
this due to driver-related reasons.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Thursday, December 02, 2010 19:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] cabbing for both 32-64-bit files

Hi:
I'm currently building an instasllation that will eventually go on to 32 and
64 bit machines.How would people handle the fact that I have some files only
referenced by either the 32-bit/64-bit install (mainly com servers) and then
other files referenced by both. Should I use separate cab files?
Cheers
Sean.

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

Re: [WiX-users] cabbing for both 32-64-bit files

[James Johnston]

Probably, except that there were some reasons why I decided against
dotNetInstaller.  In the end, given that I had only one prereq (DOTNETFX
2.0), I used the VS2008 bootstrapper because it's supported by Microsoft;
seems to work well at what it does.  Also works with MSBuild.  If I replace
this with something I'm guessing it might be something like Burn, since that
has the backing and expertise of Microsoft employees; if Burn is anything
like the quality of WiX itself I expect it to be top-notch.

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Friday, December 03, 2010 16:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Wouldn't it be simpler to have 1 executable that does all the work for you
rather than this chain of executables ending in MSI's?

dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example could
simplify that whole convoluted process to 1 executable containing both your
MSI's & all your cab files.

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-
From: James Johnston [mailto:johnst...@inn-soft.com]
Sent: 03 December 2010 16:06
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Right; it comes in a self-extracting EXE that then launching the VS2008
bootstrapper.  The generated VS2008 bootstrapper EXEs have the MSI name
embedded in them so there are two VS2008 bootstrapper EXEs: one for each
MSI.  I wrote a custom program in C that the self-extracting EXE launches.
This app determines which VS2008 bootstrapper EXE to start based on the
platform.  Also it moves the setup files to a different temp directory to
avoid trying to delete setup files that are still in use (see issue where
VS2008 bootstrapper returns immediately instead of waiting for the app to
finish installing).

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Friday, December 03, 2010 05:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Hi James:
Thanks for this, I'm assuming you then used a bundle to deal with the
extraction/running the msi?
Cheers
Sean.
-Original Message-
From: James Johnston [mailto:johnst...@inn-soft.com]
Sent: 02 December 2010 22:01
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

I wanted a unified self-extracting EXE for both 32- and 64-bit versions.
What I wound up doing was this:

1.  The build script combined with WiX conditional compilation /
preprocessor was used to compile to two different MSI files: one 32-bit and
one 64-bit.  Each was compiled individually.  (For example, 32-bit MSI has a
launch condition preventing use on 64-bit Windows).
2.  Files that are shared go into a common external cabinet file.
Because they are shared, each variation of the build script compile/link
should produce the same CAB file.  I use a diff command just to make sure
this is the case before merging the 32-bit and 64-bit build output
directories.
3.  Files that are not shared go into two cabinets: one for 32-bit files to
go with 32-bit MSI, and one for 64-bit files to go with 64-bit MSI.
Again, the preprocessor is used to make this happen.

The final layout looks something like:
MyApp.cab
MyApp_x64.cab
MyApp_x86.cab
MyApp_x64.msi
MyApp_x86.msi

In my case, the application is 32-bit but I had to split the install like
this due to driver-related reasons.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Thursday, December 02, 2010 19:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] cabbing for both 32-64-bit files

Hi:
I'm currently building an instasllation that will eventually go on to 32 and
64 bit machines.How would people handle the fact that I have some files only
referenced by either the 32-bit/64-bit install (mainly com servers) and then
other files referenced by both. Should I use separate cab files?
Cheers
Sean.


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
WiX-users mailing list
WiX-users@lists

Re: [WiX-users] packaging large number of files

[James Johnston]

I was also immediately concerned with the serviceability ramifications as
outlined by Rob below.

What kind of files are being installed?  With some applications there might
not be much you can do about it.  But for other applications, you can do a
lot.  For example, the video game industry will compile the thousands of
constant, non-changing assets (textures, sounds, etc.) into a small number
of files so that the installer and the computer's file system don't have to
deal with so many files.

James

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Saturday, December 04, 2010 07:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] packaging large number of files

No, nothing in the Windows Installer supports that sort of scenario. Not
exactly sure what that would accomplish anyway. How would you patch or
update such files? Presumably you'd have to list them with the Windows
Installer somehow and that would get you right back where you are.

Now, it would be nice if the Windows Installer installed files faster than
it does... but that isn't something we can really fix in the WiX toolset.

On Fri, Dec 3, 2010 at 10:24 AM, Sanjay Rao
wrote:

> Hi All,
>
> Our software has to install a large number(more than 50,000) of files 
> at target machine and We followed one component per file strategy(as 
> recommended by WIX and MSI). While doing major upgrades it consumes a 
> lot of time(sometimes 30 minutes) on some of the screens.
>
> I want to compress some folders (holding larger number of files 25000) 
> and make a single file and then include the compresses file into msi 
> installer. After installer finishes, I want to decompress this 
> compressed file.
> My questions is :
> Is there any way in WIX to decompress the file after installation 
> completes ?
>
> Regards,
> Sanjay Rao
>


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] cabbing for both 32-64-bit files

[James Johnston]

LOL!  Naaah... if contributors know what they're doing and commit good
patches then the quality will be good and I don't care who they work for.
No offense intended to anybody.  :)

James

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Monday, December 06, 2010 12:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

I hope he works for Microsoft Rob otherwise James might be disappointed at
the quality of Burn ;)

Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the ** Integrated
Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 04 December 2010 07:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cabbing for both 32-64-bit files

Fredrik is working on Burn. Therefore, it rocks! 

On Fri, Dec 3, 2010 at 10:06 AM, James Johnston
wrote:

> Probably, except that there were some reasons why I decided against 
> dotNetInstaller.  In the end, given that I had only one prereq 
> (DOTNETFX 2.0), I used the VS2008 bootstrapper because it's supported 
> by Microsoft; seems to work well at what it does.  Also works with 
> MSBuild.  If I replace this with something I'm guessing it might be 
> something like Burn, since that has the backing and expertise of 
> Microsoft employees; if Burn is anything like the quality of WiX 
> itself I expect it to be top-notch.
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Friday, December 03, 2010 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Wouldn't it be simpler to have 1 executable that does all the work for

> you rather than this chain of executables ending in MSI's?
>
> dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example 
> could simplify that whole convoluted process to 1 executable 
> containing both your MSI's & all your cab files.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the ** 
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, 
> Glasgow G20 0SP Email Disclaimer
>
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 03 December 2010 16:06
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Right; it comes in a self-extracting EXE that then launching the
> VS2008 bootstrapper.  The generated VS2008 bootstrapper EXEs have the 
> MSI name embedded in them so there are two VS2008 bootstrapper EXEs:
> one for each MSI.  I wrote a custom program in C that the
self-extracting EXE launches.
> This app determines which VS2008 bootstrapper EXE to start based on 
> the platform.  Also it moves the setup files to a different temp 
> directory to avoid trying to delete setup files that are still in use 
> (see issue where
> VS2008 bootstrapper returns immediately instead of waiting for the app

> to finish installing).
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: Friday, December 03, 2010 05:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> Hi James:
> Thanks for this, I'm assuming you then used a bundle to deal with the 
> extraction/running the msi?
> Cheers
> Sean.
> -Original Message-
> From: James Johnston [mailto:johnst...@inn-soft.com]
> Sent: 02 December 2010 22:01
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] cabbing for both 32-64-bit files
>
> I wanted a unified self-extracting EXE for both 32- and 64-bit
versions.
> What I wound up doing was this:
>
> 1.  The build script combined with WiX conditional compilation / 
> preprocessor was used to compile to two different MSI files: one 
> 32-bit and one 64-bit.  Each was compiled individually.  (For example,

> 32-bit MSI has a launch condition preventing use on 64-bit Windows).
> 2.  Files that are shared go into a common external cabinet file.
> Because they are shared, each variation of the build script 
>

Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

[James Johnston]

(You can just open the difxapp_.wixlib files in 7-Zip to get to
the DLLs; I believe they are just MS cabinet files with some XML appended.
No need to look at WiX source code; just extract and rename.)

>From the OP:  "It would also be good if someone could verify with the
DIFxApp team that WiX should update to this version. They are quite poor at
documenting what's changed and versioning clearly, so there is some doubt in
my mind."  I am in 100% agreement with this.  I did some rooting around in
the WDK and WiX sources and came to some observations to summarize.

First, I wondered whether an update occurred from WiX 3.0 to WiX 3.5.  The
answer is no.  I compared DIFxApp DLL versions in Wix 3.0 vs. WiX 3.5
(escrow version from a couple days ago).  They have identical DIFxApp DLLs
(compared with diff).  Therefore, simply upgrading to WiX 3.5 probably won't
help anyone having problems with DIFx unless the WiX extension was having
trouble sequencing the custom actions, or some such problem like that and
was fixed in WiX 3.5 (I am not aware of a change like that, although I
didn't look).  These DIFxApp files included with WiX are dated 5/15/2009
02:27 UTC with a file version of 2.1.1.0; product version 2.1.1.  The
signing time of the digital signature was 8/27/2008 00:06 UTC.

Then I downloaded the Windows driver kit 7.1.0 a few days ago; it installed
to directory named 7600.16385.1 so I guess that is the exact version.  Under
C:\WinDDK\7600.16385.1\redist\DIFx\DIFxApp\WixLib\x86 I found some DIFxApp
DLLs.  They are not the same as the files included with WiX.  Strangely
enough, I also found a 3 KB wixlib file in that directory with only the XML.
These DLLs are dated 2/8/2010 21:59 UTC with a file version 2.1.0.0; product
version 2.1.  The signing time on the digital signature was 2/9/2010 06:00
UTC.

To summarize:

 * WiX 3.0/3.5: DIFxApp version 2.1.1 signed 8/27/2008.
 * WDK 7.1.0: DIFxApp version 2.1.0 signed 2/09/2010.

Some conclusions:

 * Apparently the DIFx team at Microsoft isn't properly versioning DIFxApp.
How do we have newer files being distributed with older version numbers?
Probably the only reliable method of versioning DIFxApp at this point is
using the digital signatures!

 * Communication between the DIFx team and the WiX team could be improved.
Why is there a wixlib file included with the WDK yet no mention is made of
an update to DIFxApp in WiX?  I searched the WiX bug tracker for DIFx; the
only thing I have seen is the ticket submitted by Quinton earlier today.  It
would be great if they could take responsibility & contribute DIFx updates
to the WiX project?  The actual MSDN pages regarding DIFxApp have
documentation on using DIFxApp with WiX; it would be only logical to assume
that they would be helping to maintain the system that they advocate in the
documentation.  Updating WiX's DIFxApp only when users have problems seems
like a poor long-term strategy.  Perhaps the best thing might be if the DIFx
wixlib files were removed completely from WiX if they aren't maintained?
The definitive place to get these wixlib files could then become the WDK.

(Side note:  it would be very useful if Microsoft could publish a changelog
for DIFxApp; I am wondering whether the new version might fix some of the
problems Quinton Tormanen and I have been having with DIFxApp...)

In the meantime, perhaps the best strategy for DIFxApp users to take might
be to link in the wixlib file from the WDK and avoid what comes bundled with
WiX?

The OP created a ticket at:
http://sourceforge.net/tracker/?func=detail&aid=3130590&group_id=105970&atid
=642717
but since OP didn't include this link I thought I would add it to this
discussion.

James

-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com] 
Sent: Monday, December 06, 2010 18:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] What version of DIFxApp is in DIFxAppExtension?

Sorry to subject you all to my conversation with myself as I figure out
what's what, but I thought one final(?) update on what I found out may be
useful to someone else out there:

* The latest version of the DIFx tools was included in WDK 7.1.0
  (7600.16385.1) and includes files built on 2/8/2010. The WDK
  documentation recommends that although previous WDK's included
  2.1 DIFx tools, the ones from WDK 7.1.0 should be used, which
  they are currently not.

Hopefully the DIFxAppExtension can be updated soon with the current
versions.

--Quinton

-Original Message-
From: Quinton Tormanen
Sent: Monday, December 06, 2010 10:17 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: What version of DIFxApp is in DIFxAppExtension?

I think I figured it out. The files do appear to match the MultiLin versions
of the 8/26/2008 versions (shipped with WinDDK 6001.18002) (I was comparing
with the English versions).

So, what 

Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max)

[James Johnston]

Windows Installer limits directory identifiers to 72 characters max; that ID
is 73 chars.

http://msdn.microsoft.com/en-us/library/aa368295(VS.85).aspx

You can see this in ORCA by running Orca, making a new MSI file and adding
the Directory table.  Then Adjust Schema and look at the data type of the
directory ID column.  So, the directory ID will need to be shortened.

James

-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com] 
Sent: Monday, December 06, 2010 22:48
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

I need some guidance as to how to fix this error... it looks like the id is
generated during the compile process... 

I am getting this error:

The DirectoryRef/@Id of attributes value,
'Application.managementserver.plugins.authentication.native.client.symbols'
is too long for an identifier, standard identifiers are 72 characters or
less.

This is what is in my wxs source (that I wrote)


  
  


It appears that this is the location of the error, it is in a generated
file.












--
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
What happens now with your Lotus Notes apps - do you make another costly 
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus 
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] DIFxApp does not properly rollback to the old driver when doing a major upgrade

[James Johnston]

s on reading the log:
 * Some information was sanitized; for example the GUID of the driver
component is shown as "{driver component GUID}" because I removed the actual
GUID from this public e-mail list.
 * Large portions of the log file were removed; only relevant data was
included.  Line numbers are sometimes indicated as "Line XYZ:".
 * If lines were removed, this is indicated by "<.hundreds of lines.>"

Best regards,

James Johnston

Log files below.

Attempts to uninstall after upgrade:

DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for
component '{driver component GUID}'
DIFXAPP: UninstallDriverPackages failed with error 0x2
DIFXAPP: RETURN: UninstallDriverPackages() 2 (0x2)

Upgrade:

Line 226:  Action start 22:26:17: RemoveExistingProducts.
<.hundreds of lines.>
Action 22:26:22: MsiProcessDrivers. 
Action start 22:26:22: MsiProcessDrivers.
DIFXAPP: ENTER: ProcessDriverPackages()
DIFXAPP: INFO: 'Component' is 'MyDriverComponent'
DIFXAPP: INFO: Component state 0x3 -> 0x2
DIFXAPP: INFO: 'ComponentId' is {driver component GUID}
DIFXAPP: INFO: 'Flags' is 10
DIFXAPP: INFO: component path is 
DIFXAPP: INFO: user SID of user performing the install is
'S-1-5-21-1644491937-2147298945-839522115-1003'.
DIFXAPP: INFO: creating
HKEY_USERS\S-1-5-21-1644491937-2147298945-839522115-1003\Software\Microsoft\
Windows\CurrentVersion\DIFxApp\Components\{driver component GUID} (User's
SID: 'S-1-5-21-1644491937-2147298945-839522115-1003') ...
Action 22:26:22: MsiUninstallDrivers. 
Action start 22:26:22: MsiUninstallDrivers.
MsiUninstallDrivers: 
Action ended 22:26:22: MsiUninstallDrivers. Return value 1.
DIFXAPP: RETURN: ProcessDriverPackages() 0 (0x0)
Line 460:  Action ended 22:26:22: MsiProcessDrivers. Return value 1.
<.hundreds of lines.>
Action 22:26:28: MsiUninstallDrivers. 
DIFXAPP: UninstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {driver component
GUID}.
DIFXAPP: 'CustomActionData' property 'flags' is 0xA.
DIFXAPP: 'CustomActionData' property 'ProductName' is My Product.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is My Company.
DIFXAPP: INFO: user SID of user performing the install is
'S-1-5-21-1644491937-2147298945-839522115-1003'.
DIFXAPP: INFO: opening
HKEY_USERS\S-1-5-21-1644491937-2147298945-839522115-1003\Software\Microsoft\
Windows\CurrentVersion\DIFxApp\Components\{driver component GUID} (User's
SID: 'S-1-5-21-1644491937-2147298945-839522115-1003') ...
DIFXAPP: INFO:   ENTER:  DriverPackageUninstallW
DIFXAPP: INFO:   Uninstalling driver package
C:\WINDOWS\system32\DRVSTORE\productbus_some_big_guid_here\productbus.inf...
DIFXAPP: INFO:   Successfully removed 'C:\WINDOWS\INF\oem8.inf'.
DIFXAPP: INFO:   No devices found for
C:\WINDOWS\system32\DRVSTORE\productbus_some_big_guid_here\productbus.inf
uninstall.
DIFXAPP: INFO:   Driver store entry
'C:\WINDOWS\system32\DRVSTORE\productbus_some_big_guid_here\productbus.inf'
removed.
DIFXAPP: SUCCESS:Uninstall completed.
DIFXAPP: INFO:   RETURN: DriverPackageUninstallW  (0x0)
DIFXAPP: INFO: driver store
'C:\WINDOWS\system32\DRVSTORE\productbus_some_big_guid_here\productbus.inf'
uninstalled.
DIFXAPP: INFO: deleted add remove programs key for
'C:\WINDOWS\system32\DRVSTORE\productbus_some_big_guid_here\productbus.inf'.
DIFXAPP: A reboot is not needed to uninstall the driver package '{driver
component GUID}'.
2186:  DIFXAPP: RETURN: UninstallDriverPackages() 0 (0x0)
<.hundreds of lines.>
Action 22:26:49: MsiCleanupOnSuccess. 
Action start 22:26:49: MsiCleanupOnSuccess.
DIFXAPP: ENTER: CleanupOnSuccess()
DIFXAPP: INFO: 'Component' is 'MyDriverComponent'
DIFXAPP: INFO: 'ComponentId' is {driver component GUID}
DIFXAPP: INFO: user SID of user performing the install is
'S-1-5-21-1644491937-2147298945-839522115-1003'.
DIFXAPP: INFO: opening
HKEY_USERS\S-1-5-21-1644491937-2147298945-839522115-1003\Software\Microsoft\
Windows\CurrentVersion\DIFxApp\Components\{driver component GUID} (User's
SID: 'S-1-5-21-1644491937-2147298945-839522115-1003') ...
DIFXAPP: RETURN: CleanupOnSuccess() 0 (0x0)
8765:  Action ended 22:26:49: MsiCleanupOnSuccess. Return value 1.
<.hundreds of lines.>
9332:  Action ended 22:26:50: RemoveExistingProducts. Return value 1.
Action 22:26:51: MsiProcessDrivers. 
Action start 22:26:51: MsiProcessDrivers.
DIFXAPP: ENTER: ProcessDriverPackages()
DIFXAPP: INFO: 'Component' is 'MyDriverComponent'
DIFXAPP: INFO: Component state 0x2 -> 0x3
DIFXAPP: INFO: 'ComponentId' is {driv

Re: [WiX-users] DIFxApp does not properly rollback to the old driverwhen doing a major upgrade

[James Johnston]

.  (Some drivers had MSI files for
helper/utility programs but did not have the MsiDriverPackages table so I
conclude they do something else).

Best regards,

James Johnston

-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com] 
Sent: Friday, December 10, 2010 17:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp does not properly rollback to the old
driverwhen doing a major upgrade

Thanks for digging into this further. The support e-mail for DIFx Tools is
difxt...@microsoft.com. I have received responses over the years from
different people, but never any resolution to my problems. If that e-mail
address is no longer valid, then I can give you the addresses of the
specific people that replied. Please keep me posted on what you find out.

--Quinton

-Original Message-
From: James Johnston [mailto:johnst...@inn-soft.com]
Sent: Thursday, December 09, 2010 3:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DIFxApp does not properly rollback to the old
driverwhen doing a major upgrade

> Hi,
> 
> As some of you have probably noticed, there has been some discussion 
> recently regarding problems with DIFxApp causing rollbacks.  I did
some more
> investigation and was able to reliably reproduce the issue and come up
with
> a very good idea on what is causing the problem.  All investigation
was done
> with the version of DIFxApp included with Windows DDK version
7600.16385.1;
> note that this will also reproduce with the version included with WiX
3.0 /
> 3.5.  It was done on a clean Windows XP SP2 virtual machine with .NET 
> Framework 2.0; however we have observed the same problems on Windows
7.
>
> As far as I can tell, this is a bug in the DIFxApp DLLs and/or the WiX 
> extension for DIFxApp.  If anyone knows some good workarounds, or how
to
> report this to the proper channels and get it fixed it would be much 
> appreciated!  From what I can tell, there exist situations in any
DIFxApp
> setup program doing an upgrade where if the user cancels the setup at
a
> certain point (or there is an error in the installation of the new
product)
> then the user's system will be hosed and they would be unable to
uninstall
> the product without some involved technical support.
>
> If the bug can't be fixed or worked around, I don't see how DIFxApp is 
> suitable for use in a commercial product that needs to support
upgrades
> (i.e. all products).  And since DIFxApp isn't open source, I can't go
in and
> just fix the problem.  Very frustrating! 
>
> ...


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages, 
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

[James Johnston]

http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=2820

Maybe there are some issues with the driver package itself?  i.e.
bad/missing catalog file.  Be sure that the driver files is completely
installed & that all required files are in the appropriate locations.

If the driver isn't WHQL signed then you have to set the legacy attribute on
the DIFX driver element; otherwise that could maybe be another factor?

-Original Message-
From: Jury BURA [mailto:jury.b...@visutechsystem.by] 
Sent: Wednesday, February 09, 2011 14:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

Hi!

I have this error (WiX 3.6.1321):

DIFXAPP: ENTER: InstallDriverPackages()
DIFXAPP: INFO: 'CustomActionData' property 'DIFxApp Version' is '2.1'.
DIFXAPP: INFO: 'CustomActionData' property 'UI Level' is '5'.
DIFXAPP: INFO: 'CustomActionData' property 'componentId' is '{GUID}'.
DIFXAPP: INFO: 'CustomActionData' property 'componentPath' is 'C:\PATH1\'.
DIFXAPP: INFO: 'CustomActionData' property 'flags' is 0xA.
DIFXAPP: INFO: 'CustomActionData' property 'installState' is '2'.
DIFXAPP: INFO: 'CustomActionData' property 'ProductName' is
'[product_name]'.
DIFXAPP: INFO: 'CustomActionData' property 'ManufacturerName' is
'[manufacturer_name]'.
DIFXAPP: INFO: user SID of user performing the install is 'SID'.
DIFXAPP: INFO: opening
HKEY_USERS\SID\Software\Microsoft\Windows\CurrentVersion\DIFxApp\Components\
{GUID}
(User's SID: 'SID') ...
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: ERROR: Failed to calculate strong name. (Error code 0x52: The
directory or file cannot be created.)
DIFXAPP: INFO: Successfully removed '{GUID}' from reference list of driver
store entry ''
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x52)
DIFXAPP: ERROR: encountered while installing driver package
'C:\PATH1\driver.inf'
DIFXAPP: ERROR: InstallDriverPackages failed with error 0x52
DIFXAPP: RETURN: InstallDriverPackages() 82 (0x52)

Any ideas to fix this problem?

Thanks!


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

[James Johnston]

Someone more familiar with DIFx might be able to shed some more light here.

Your WiX code looks OK to me.  If this problem is reproducible on multiple 
computers then I would blame the driver package.  You could also try installing 
the driver using DPInst and see if that works or not.

But I'm suspecting it might have to do with catalogs somehow?  There's no 
catalog file in your list... does the INF file specify an (apparently missing) 
catalog file?

Not sure if you've seen this topic, but you might want to review the topics in 
this section in MSDN for any potential gotchas:
http://msdn.microsoft.com/en-us/library/ff543645(VS.85).aspx

-Original Message-
From: Jury BURA [mailto:jury.b...@visutechsystem.by] 
Sent: Thursday, February 10, 2011 16:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

Wix code for my driver:

 

Driver isn't WHQL signed.
And... typical error message for missed cat file is:
DIFXAPP: ERROR: Failed to calculate strong name from 'file-path'.
This error message doesn't contain file path.

Thanks!


10.02.2011 17:39, James Johnston пишет:
> http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=2820
>
> Maybe there are some issues with the driver package itself?  i.e.
> bad/missing catalog file.  Be sure that the driver files is completely 
> installed&  that all required files are in the appropriate locations.
>
> If the driver isn't WHQL signed then you have to set the legacy 
> attribute on the DIFX driver element; otherwise that could maybe be another 
> factor?
>
> -Original Message-
> From: Jury BURA [mailto:jury.b...@visutechsystem.by]
> Sent: Wednesday, February 09, 2011 14:24
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.
>
> Hi!
>
> I have this error (WiX 3.6.1321):
>
> DIFXAPP: ENTER: InstallDriverPackages()
> DIFXAPP: INFO: 'CustomActionData' property 'DIFxApp Version' is '2.1'.
> DIFXAPP: INFO: 'CustomActionData' property 'UI Level' is '5'.
> DIFXAPP: INFO: 'CustomActionData' property 'componentId' is '{GUID}'.
> DIFXAPP: INFO: 'CustomActionData' property 'componentPath' is 'C:\PATH1\'.
> DIFXAPP: INFO: 'CustomActionData' property 'flags' is 0xA.
> DIFXAPP: INFO: 'CustomActionData' property 'installState' is '2'.
> DIFXAPP: INFO: 'CustomActionData' property 'ProductName' is 
> '[product_name]'.
> DIFXAPP: INFO: 'CustomActionData' property 'ManufacturerName' is 
> '[manufacturer_name]'.
> DIFXAPP: INFO: user SID of user performing the install is 'SID'.
> DIFXAPP: INFO: opening
> HKEY_USERS\SID\Software\Microsoft\Windows\CurrentVersion\DIFxApp\Compo
> nents\
> {GUID}
> (User's SID: 'SID') ...
> DIFXAPP: INFO: ENTER: DriverPackageInstallW
> DIFXAPP: ERROR: Failed to calculate strong name. (Error code 0x52: The 
> directory or file cannot be created.)
> DIFXAPP: INFO: Successfully removed '{GUID}' from reference list of 
> driver store entry ''
> DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x52)
> DIFXAPP: ERROR: encountered while installing driver package 
> 'C:\PATH1\driver.inf'
> DIFXAPP: ERROR: InstallDriverPackages failed with error 0x52
> DIFXAPP: RETURN: InstallDriverPackages() 82 (0x52)
>
> Any ideas to fix this problem?
>
> Thanks!
>
> --
> --
> --
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
>  The ultimate all-in-one performance toolkit: Intel(R) 
> Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/li

Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

[James Johnston]

If it's only one PC and it works fine on other computers of similar 
configuration (same version of Windows, etc.) then maybe also check some 
registry entries:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DIFxApp
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DIFx
HKCU\Software\Microsoft\Windows\CurrentVersion\DIFxApp

If it's a DIFX problem then it might be helpful to uninstall your software and 
then clean those areas up to remove traces of the drivers, in case there was 
some problems with corruption in DIFx.

Also maybe check into Windows settings and group policy that might be 
preventing the driver from being installed (especially since it's unsigned).

I would also recommend inspecting the SetupAPI log file.  Delete any existing 
log file, configure the system for the desired level of logging, and then run 
the installer again.  The SetupAPI log can give far more detail than DIFx as to 
why a driver install has failed.  Often the MSI log will have a message from 
DIFx saying in effect, "the driver install failed" with not much detail.  
SetupAPI log may be more helpful.

Info on setup API logs:
Vista/7: http://msdn.microsoft.com/en-us/library/ff550887(VS.85).aspx
Windows XP & probably 2000:
http://msdn.microsoft.com/en-us/library/ff550882(VS.85).aspx
http://www.microsoft.com/whdc/archive/setupapilog.mspx
http://www.osronline.com/ddkx/install/troubleshoot_9g87.htm

My guess is you will discover some unique configuration setting or some 
corrupted settings/files to that computer that is causing it to fail.  This has 
been my experience so far with DIFx.

-Original Message-
From: Jury BURA [mailto:jury.b...@visutechsystem.by] 
Sent: Thursday, February 10, 2011 17:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.

INF file doesn't  specify cat-file (only DLL and SYS).

This problem appear for only one PC configuration.
Ok, I'll try install this driver using DPInst and I'll read the topic.

Thanks a lot.

10.02.2011 18:52, James Johnston пишет:
> Someone more familiar with DIFx might be able to shed some more light here.
>
> Your WiX code looks OK to me.  If this problem is reproducible on multiple 
> computers then I would blame the driver package.  You could also try 
> installing the driver using DPInst and see if that works or not.
>
> But I'm suspecting it might have to do with catalogs somehow?  There's no 
> catalog file in your list... does the INF file specify an (apparently 
> missing) catalog file?
>
> Not sure if you've seen this topic, but you might want to review the topics 
> in this section in MSDN for any potential gotchas:
> http://msdn.microsoft.com/en-us/library/ff543645(VS.85).aspx
>
> -Original Message-
> From: Jury BURA [mailto:jury.b...@visutechsystem.by]
> Sent: Thursday, February 10, 2011 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.
>
> Wix code for my driver:
>
>Id="mydrv.sys" Name="mydrv.sys" />   Name="mydrv.dll" />
>   
>
> Driver isn't WHQL signed.
> And... typical error message for missed cat file is:
> DIFXAPP: ERROR: Failed to calculate strong name from 'file-path'.
> This error message doesn't contain file path.
>
> Thanks!
>
>
> 10.02.2011 17:39, James Johnston пишет:
>> http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=2820
>>
>> Maybe there are some issues with the driver package itself?  i.e.
>> bad/missing catalog file.  Be sure that the driver files is completely
>> installed&   that all required files are in the appropriate locations.
>>
>> If the driver isn't WHQL signed then you have to set the legacy 
>> attribute on the DIFX driver element; otherwise that could maybe be another 
>> factor?
>>
>> -Original Message-
>> From: Jury BURA [mailto:jury.b...@visutechsystem.by]
>> Sent: Wednesday, February 09, 2011 14:24
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.
>>
>> Hi!
>>
>> I have this error (WiX 3.6.1321):
>>
>> DIFXAPP: ENTER: InstallDriverPackages()
>> DIFXAPP: INFO: 'CustomActionData' property 'DIFxApp Version' is '2.1'.
>> DIFXAPP: INFO: 'CustomActionData' property 'UI Level' is '5'.
>> DIFXAPP: INFO: 'CustomActionData' property 'componentId' is '{GUID}'.
>> DIFXAPP: INFO: 'CustomActionData' property 'componentPath' is 'C:\PATH1\'.
>> DIFXAPP: INFO: 'CustomActi

Re: [WiX-users] DIFxAPP and Properties question

[James Johnston]

If I remember correctly, the justification for adding dedicated driver
entries to ARP is so that if the driver causes the computer to fail to boot
into normal mode, you can still uninstall the driver in safe mode.  You
can't use Windows Installer in safe mode, so the only mechanism would be the
dedicated ARP entry.

-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com] 
Sent: Wednesday, December 07, 2011 16:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxAPP and Properties question

Personally I tend to set AddRemovePrograms="no" to prevent drivers from
showing up in ARP. Mean otherwise the user could uninstall the drivers while
leaving back the application which IMHO makes no sense.

Back to your question AFAIK configuring the ARP entries is done inside the
DifX driver.

Regards
Tobias


--
Cloud Services Checklist: Pricing and Packaging Optimization This white
paper is intended to serve as a reference, checklist and point of discussion
for anyone considering optimizing the pricing and packaging model of a cloud
services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] My First Bundle! :)

[James Green]

Hi,

Thanks for that Rob.  Looked at the logs and solved that particular issue.  The 
only issue I have left now is that the Bundle itself appears in the Add/Remove 
programs.

Is there a way to hide it? Or should I be thinking about "hiding" the 
application and use the bundle as the UnInstaller?

Jammer

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 11 January 2012 05:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] My First Bundle! :)

Take a look at the log file that should be created in your %TEMP% directory. 
Hopefully that will show how the condition evaluated and explain why uninstall 
failed.

On Tue, Jan 10, 2012 at 12:00 PM, Jammer  wrote:

> Hi All,
>
> I'm creating my first bootstapper installer and I have a few questions.
>
> My entire script looks like this:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>  Version="1.0.0.0"
> Manufacturer="Mango-Solutions"
> UpgradeCode="340fe3b1-b98d-42fc-9a15-d1d36ca83922"
> HelpTelephone="+44 (0)1249 767700"
> HelpUrl="http://www.mango-solutions.com";
> Compressed="yes">
>
>
>  icense"/>
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client"
> Value="Install"
> Variable="DotNetFramework40ClientInstallRegValue"/>
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full"
> Value="Install"
> Variable="DotNetFramework40FullInstallRegValue"/>
> 
>
>  SourceFile="..\..\lib\net_client_profile\dotNetFx40_Client_x86_x64.exe
> "/>  SourceFile="..\Build\Mango.Analyse.Installer.msi"/>
> 
> 
> 
>
> Even though I have a conditional set on the client profile exe it 
> always runs this package.  As far as I can tell this is correct syntax.
>
> I also just noticed that in the Add/Remove Programs under winXP SP3 I 
> ended up with .NET 4.0 client profile installed, the Mango.Analyse 
> application AND an entry for this boot strapper ... when I tried to 
> uninstall the bootstrapper it just gave an error saying that it 
> couldn't proceed ...
>
> Would appreciate any pointers as I don't seem to be able to find much 
> documentation for this task.
> --
> *Jammer*
> WWW.JAMMER.BIZ  TWITTER 
>  LINKEDIN
> **
>
> --
> 
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. 
> Create new or port existing apps to sell to consumers worldwide. 
> Explore the Intel AppUpSM program developer opportunity. 
> appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually, Rob Mensching - http://RobMensching.com LLC
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex 
infrastructure or vast IT resources to deliver seamless, secure access to 
virtual desktops. With this all-in-one solution, easily deploy virtual desktops 
for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it 
free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] My First Bundle! :)

[James Green]

Hi Again,

I spoke too soon.

I've confirmed that .NET 4.0 isn't installed on the machine.  My Bundle has an 
install condition of:

FindDotNet40ClientInstallRegValue = 0

Which is a RegistrySearch:



[011C:0408][2012-01-11T09:44:42]: Condition 'FindDotNet40ClientInstallRegValue 
= 0' evaluates to false.

Which according to the log evaluated to false, I'm obviously terribly mistaken 
but I would assume that if the key isn't present it would evaluate to 0 meaning 
that " FindDotNet40ClientInstallRegValue = 0" would evaluate to true and 
install .net on the machine.  

[011C:0408][2012-01-11T09:44:40]: Registry key not found. Key = 
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client'
[011C:0408][2012-01-11T09:44:40]: Registry key not found. Key = 
'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'

Then the entire packaged failed to install anything subsequently.

[011C:0408][2012-01-11T09:44:46]: Error 0x80070643: Failed to execute apply.


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 11 January 2012 05:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] My First Bundle! :)

Take a look at the log file that should be created in your %TEMP% directory. 
Hopefully that will show how the condition evaluated and explain why uninstall 
failed.

On Tue, Jan 10, 2012 at 12:00 PM, Jammer  wrote:

> Hi All,
>
> I'm creating my first bootstapper installer and I have a few questions.
>
> My entire script looks like this:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>  Version="1.0.0.0"
> Manufacturer="Mango-Solutions"
> UpgradeCode="340fe3b1-b98d-42fc-9a15-d1d36ca83922"
> HelpTelephone="+44 (0)1249 767700"
> HelpUrl="http://www.mango-solutions.com";
> Compressed="yes">
>
>
>  icense"/>
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client"
> Value="Install"
> Variable="DotNetFramework40ClientInstallRegValue"/>
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full"
> Value="Install"
> Variable="DotNetFramework40FullInstallRegValue"/>
> 
>
>  SourceFile="..\..\lib\net_client_profile\dotNetFx40_Client_x86_x64.exe
> "/>  SourceFile="..\Build\Mango.Analyse.Installer.msi"/>
> 
> 
> 
>
> Even though I have a conditional set on the client profile exe it 
> always runs this package.  As far as I can tell this is correct syntax.
>
> I also just noticed that in the Add/Remove Programs under winXP SP3 I 
> ended up with .NET 4.0 client profile installed, the Mango.Analyse 
> application AND an entry for this boot strapper ... when I tried to 
> uninstall the bootstrapper it just gave an error saying that it 
> couldn't proceed ...
>
> Would appreciate any pointers as I don't seem to be able to find much 
> documentation for this task.
> --
> *Jammer*
> WWW.JAMMER.BIZ  TWITTER 
>  LINKEDIN
> **
>
> --
> 
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. 
> Create new or port existing apps to sell to consumers worldwide. 
> Explore the Intel AppUpSM program developer opportunity. 
> appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
virtually, Rob Mensching - http://RobMensching.com LLC
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex 
infrastructure or vast IT resources to deliver seamless, secure access to 
virtual desktops. With this all-in-one solution, easily deploy virtual desktops 
for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it 
free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual 

Re: [WiX-users] My First Bundle! :)

[James Green]

Hi Rob, yeah I noticed I was using the Id rather than the variable name just 
after posting this and that worked.  Just a bit confusing since sometimes you 
need to reference things by ID and sometimes by variable name.

I'm using the latest 3.6 Beta build of WiX.

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 11 January 2012 15:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] My First Bundle! :)

Can you try chaning your condition to "NOT FindDotNet40ClientInstallRegValue" 
and let's see if that works. I agree this should work, I'm a little surprised 
it doesn't.

What version of WIX toolset are you using?

On Wed, Jan 11, 2012 at 2:00 AM, James Green wrote:

> Hi Again,
>
> I spoke too soon.
>
> I've confirmed that .NET 4.0 isn't installed on the machine.  My 
> Bundle has an install condition of:
>
> FindDotNet40ClientInstallRegValue = 0
>
> Which is a RegistrySearch:
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\NET Framework 
> Setup\NDP\v4\Client"
> Value="Install"
> Variable="DotNetFramework40ClientInstallRegValue"
> />
>
> [011C:0408][2012-01-11T09:44:42]: Condition 
> 'FindDotNet40ClientInstallRegValue = 0' evaluates to false.
>
> Which according to the log evaluated to false, I'm obviously terribly 
> mistaken but I would assume that if the key isn't present it would 
> evaluate to 0 meaning that " FindDotNet40ClientInstallRegValue = 0" 
> would evaluate to true and install .net on the machine.
>
> [011C:0408][2012-01-11T09:44:40]: Registry key not found. Key = 
> 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client'
> [011C:0408][2012-01-11T09:44:40]: Registry key not found. Key = 
> 'SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'
>
> Then the entire packaged failed to install anything subsequently.
>
> [011C:0408][2012-01-11T09:44:46]: Error 0x80070643: Failed to execute 
> apply.
>
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 11 January 2012 05:26
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] My First Bundle! :)
>
> Take a look at the log file that should be created in your %TEMP% 
> directory. Hopefully that will show how the condition evaluated and 
> explain why uninstall failed.
>
> On Tue, Jan 10, 2012 at 12:00 PM, Jammer  wrote:
>
> > Hi All,
> >
> > I'm creating my first bootstapper installer and I have a few questions.
> >
> > My entire script looks like this:
> >
> > 
> > http://schemas.microsoft.com/wix/2006/wi";
> > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
> >
> >  > Version="1.0.0.0"
> > Manufacturer="Mango-Solutions"
> > UpgradeCode="340fe3b1-b98d-42fc-9a15-d1d36ca83922"
> > HelpTelephone="+44 (0)1249 767700"
> > HelpUrl="http://www.mango-solutions.com";
> > Compressed="yes">
> >
> >
> >  > fL
> > icense"/>
> >
> >  > Root="HKLM"
> > Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client"
> > Value="Install"
> > Variable="DotNetFramework40ClientInstallRegValue"/>
> >
> >  > Root="HKLM"
> > Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full"
> > Value="Install"
> > Variable="DotNetFramework40FullInstallRegValue"/>
> > 
> >
> >  > SourceFile="..\..\lib\net_client_profile\dotNetFx40_Client_x86_x64.e
> > xe "/>  > SourceFile="..\Build\Mango.Analyse.Installer.msi"/>
> > 
> > 
> > 
> >
> > Even though I have a conditional set on the client profile exe it 
> > always runs this package.  As far as I can tell this is correct syntax.
> >
> > I also just noticed that in the Add/Remove Programs under winXP SP3 
> > I ended up with .NET 4.0 client profile installed, the Mango.Analyse 
> > application AND an entry for this boot strapper ... when I tried to 
> > uninstall the bootstrapper it just gave an error saying that it 
> > couldn't proceed ...
> >
> > Would appreciate any pointers as I don't seem to be able to find 
> > much documentation for this task.
> > --
> > *Jammer*
> > WWW.JAMMER.BIZ <http://www.jammer.biz> TWITTER 
> > <http://twitter.com/findjammer> LIN

[WiX-users] Cab File

[James Green]

Hi All,

I have a large set of files to distribute with our installer (1100 files) and I 
was hoping to be able to do this with a zip file but that doesn't seem possible 
(nor a good idea) so I was wondering if it was possible to use a cab file 
instead?

I'm wondering if the Cab will also be able to maintain the directory structure?

Regards,

James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cab File

[James Green]

Hi Peter,

Not sure I understand.  I already have a "default" cab file for our application 
declared like:



This currently contains all the application files for our file defined by hand 
inside Component declarations within the script.  The problem I'm trying to 
solve is that I have another 'sub app' that will be installed with our 
application in the form of a set of files the problem is there are actually 
over 2000 files and 650+ directories and I really don't want to type that lot 
in (nor maintain it ...) so I was originally looking at including a zip and 
running an unzip during the install process.  Seeing how problematic that is I 
started looking at using a cab file.

Can a cab maintain the original directory structure automatically on 
decompressing?

Cheers,

James

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 16 January 2012 14:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Add Compressed="yes" to the package element and EmbedCab="yes"
Cabinet="Product.cab" to the media element of your installer and it will 
compress the files into a cabinet inside it.

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:14
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cab File

Hi All,

I have a large set of files to distribute with our installer (1100 files) and I 
was hoping to be able to do this with a zip file but that doesn't seem possible 
(nor a good idea) so I was wondering if it was possible to use a cab file 
instead?

I'm wondering if the Cab will also be able to maintain the directory structure?

Regards,

James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
-
-
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cab File

[James Green]

Thanks & sorry.

I ALWAYS prefer a WiX solution :)

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 16 January 2012 15:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Look at the Wix help regarding the "heat" tool. That will do the tedious 
initial script generation for you. Then you can tweak it by hand to maintain 
the diffs in future versions.

If you're not asking for a Wix-based solution then the Wix mailing list isn't 
really the place to be asking. The cab format is documented on the msdn at 
http://msdn.microsoft.com/en-us/library/bb417343.aspx I dont see how that's any 
different from doing it with a zip though.

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi Peter,

Not sure I understand.  I already have a "default" cab file for our application 
declared like:



This currently contains all the application files for our file defined by hand 
inside Component declarations within the script.  The problem I'm trying to 
solve is that I have another 'sub app' that will be installed with our 
application in the form of a set of files the problem is there are actually 
over 2000 files and 650+ directories and I really don't want to type that lot 
in (nor maintain it ...) so I was originally looking at including a zip and 
running an unzip during the install process.  Seeing how problematic that is I 
started looking at using a cab file.

Can a cab maintain the original directory structure automatically on 
decompressing?

Cheers,

James

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 16 January 2012 14:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Add Compressed="yes" to the package element and EmbedCab="yes"
Cabinet="Product.cab" to the media element of your installer and it will 
compress the files into a cabinet inside it.

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:14
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cab File

Hi All,

I have a large set of files to distribute with our installer (1100 files) and I 
was hoping to be able to do this with a zip file but that doesn't seem possible 
(nor a good idea) so I was wondering if it was possible to use a cab file 
instead?

I'm wondering if the Cab will also be able to maintain the directory structure?

Regards,

James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
-
-
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


-
-
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
---

Re: [WiX-users] Cab File

[James Green]

Hi Dan,

Yeah, I'm just getting my batch command setup for this.  It's building OK as a 
fragment but I'm can't work out how to incorporate it into the features so that 
it will actually execute during the install process.

James.

-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com] 
Sent: 16 January 2012 15:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi James,

You can use the "heat" harvesting tool that comes with WiX to generate an 
initial WxS installer file for your 2000 files and 650+ directories and then 
add that WxS file to your installer.

Dan

-----Original Message-
From: James Green [mailto:jgr...@mango-solutions.com] 
Sent: January-16-12 9:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi Peter,

Not sure I understand.  I already have a "default" cab file for our application 
declared like:



This currently contains all the application files for our file defined by hand 
inside Component declarations within the script.  The problem I'm trying to 
solve is that I have another 'sub app' that will be installed with our 
application in the form of a set of files the problem is there are actually 
over 2000 files and 650+ directories and I really don't want to type that lot 
in (nor maintain it ...) so I was originally looking at including a zip and 
running an unzip during the install process.  Seeing how problematic that is I 
started looking at using a cab file.

Can a cab maintain the original directory structure automatically on 
decompressing?

Cheers,

James

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 16 January 2012 14:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Add Compressed="yes" to the package element and EmbedCab="yes"
Cabinet="Product.cab" to the media element of your installer and it will 
compress the files into a cabinet inside it.

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:14
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cab File

Hi All,

I have a large set of files to distribute with our installer (1100 files) and I 
was hoping to be able to do this with a zip file but that doesn't seem possible 
(nor a good idea) so I was wondering if it was possible to use a cab file 
instead?

I'm wondering if the Cab will also be able to maintain the directory structure?

Regards,

James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
-
-
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) 

Re: [WiX-users] Cab File

[James Green]

Hey Dan,

Yeah, I've just gotten all this working, thanks.  Just trying to get the file 
source path all configured and working now ... installer joy!  And indeed that 
would be a drag!

james 
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cab File

[James Green]

Hey Again,

I'm not sure how to go about getting this working now, I've tried a few things 
and I just get Undefined veriables erros:

I have  in 
Product.wxs

Then I have heat producing a fragment with -cg RInstall -var var.RFileSource

But the build fails saying that "Undefined preprocessor variable 
'$(var.RFileSource)"

How can I reference a variable in the main wxs file without hand editing the 
generated fragment?

Cheers,

James
 
-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com] 
Sent: 16 January 2012 16:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi James,

I haven't used heat for quite a while, but I think you can use the -cg  
option to get it to create a ComponentGroup containing all your components and 
then include that component group in your Feature using a ComponentGroupRef. 
Otherwise I think you have to use a ComponentRef to refer to each component 
individually ... and that would clearly be a drag. :-)

Dan

-----Original Message-
From: James Green [mailto:jgr...@mango-solutions.com] 
Sent: January-16-12 11:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi Dan,

Yeah, I'm just getting my batch command setup for this.  It's building OK as a 
fragment but I'm can't work out how to incorporate it into the features so that 
it will actually execute during the install process.

James.

-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com] 
Sent: 16 January 2012 15:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi James,

You can use the "heat" harvesting tool that comes with WiX to generate an 
initial WxS installer file for your 2000 files and 650+ directories and then 
add that WxS file to your installer.

Dan

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com] 
Sent: January-16-12 9:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi Peter,

Not sure I understand.  I already have a "default" cab file for our application 
declared like:



This currently contains all the application files for our file defined by hand 
inside Component declarations within the script.  The problem I'm trying to 
solve is that I have another 'sub app' that will be installed with our 
application in the form of a set of files the problem is there are actually 
over 2000 files and 650+ directories and I really don't want to type that lot 
in (nor maintain it ...) so I was originally looking at including a zip and 
running an unzip during the install process.  Seeing how problematic that is I 
started looking at using a cab file.

Can a cab maintain the original directory structure automatically on 
decompressing?

Cheers,

James

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: 16 January 2012 14:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Add Compressed="yes" to the package element and EmbedCab="yes"
Cabinet="Product.cab" to the media element of your installer and it will 
compress the files into a cabinet inside it.

-Original Message-
From: James Green [mailto:jgr...@mango-solutions.com]
Sent: 16 January 2012 14:14
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cab File

Hi All,

I have a large set of files to distribute with our installer (1100 files) and I 
was hoping to be able to do this with a zip file but that doesn't seem possible 
(nor a good idea) so I was wondering if it was possible to use a cab file 
instead?

I'm wondering if the Cab will also be able to maintain the directory structure?

Regards,

James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
-
-
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying an

Re: [WiX-users] Cab File

[James Green]

Urgh!  That sounds horrendous.  That's a significant count of files!

-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com] 
Sent: 16 January 2012 16:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi James,

I have an idea how you were feeling about adding 2000+ files because I had a 
similar situation with over 12000 files and more than 1000 folders. Glad to 
hear you got it working! :-)

Dan 
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Cab File

[James Green]

Hey Dan,

Thanks for that, I just read the section on that just after posting to the 
list.  It works fine if I put it in the generated .wxs file but not if I put it 
in the non-generated Product.wxs file so anytime someone reruns the batch file 
this key bit of info will get obliterated ...

How can I get around this in a repeatable fashion so that the generated 
fragment is always valid?

Cheers,

James

-Original Message-
From: Daniel Madill [mailto:dan.mad...@quanser.com] 
Sent: 16 January 2012 16:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cab File

Hi James,

Preprocessor variables and WixVariable's are not the same thing. A preprocessor 
variable is defined using . For example:



Preprocessor variables are handled much like the C preprocessor handles #define 
macros.

Dan 
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only and may 
contain confidential and / or privileged information. If you are not the 
intended recipient, please contact the sender and delete this message. Any 
unauthorised use of the information contained in this message is prohibited.
Mango Business Solutions Limited is registered in England under No. 4560258 
with its registered office at Suite 3, Middlesex House, Rutherford Close, 
Stevenage, Herts, SG1 2EF, UK.

PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users