Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-05 Thread Bob Arnson
On 04-Oct-14 17:47, Phill Hogland wrote: > I had inferred from other threads to the effect that the msi file name could > not/should not be changed after it was signed. The only restriction I'm aware of is that once you install an .msi package, you need a major upgrade to give it another name. Gl

Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-04 Thread Phill Hogland
Hey Bob, thanks a lot for responding to that old post. I finally understood what you were saying and got it working. I was tripping over an impression I had inferred from other threads to the effect that the msi file name could not/should not be changed after it was signed. I was also getting co

Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-04 Thread Phill Hogland
Hi Bob and group; Using Media/@Layout I achived a folder structure like this: Release\cabs\mycab.cab Release\culture1\mymsi.msi Release\culture2\mymsi.msi The cab is being signed by the MSBuild SignCab target but then I get Insignia error INSG0258 cab file not found in culture2 folder. Also whe

Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-04 Thread Phill Hogland
Phill Hogland wrote > I'd do it this way: Set cab cache path to a common directory then let > wix.targets do its thing. Then assemble a new image you use to build the > bundle from. Bob; I am currently using in each MSI project the following: cabs True along with: If I change to exte

Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-03 Thread Phill Hogland
Interesting. Thanks for the suggestion. I will look into it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-tp7596991p7597117.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Using external cab for multiple language msi packages.

2014-10-02 Thread Bob Arnson
On 25-Sep-14 13:24, Phill Hogland wrote: > Using a Burn driven MSIs, without using language transforms, results in MSI > packages, of the same name, in a culture named folder tree. I have also > been evaluating using external cabs for the common files. From what I have > reviewed the cab gets cre

[WiX-users] Using external cab for multiple language msi packages.

2014-09-25 Thread Phill Hogland
Using a Burn driven MSIs, without using language transforms, results in MSI packages, of the same name, in a culture named folder tree. I have also been evaluating using external cabs for the common files. From what I have reviewed the cab gets created in the MSI output folder (or subfolder below