Hi,
Thanks for your answer! I have been trying long and hard, but this is what i
get in the log:
-------------------------
Project "C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Deploy.proj" (Patch
target(s)):
Target Patch:
Touching "xxxPatch\xxxPatch.wixproj".
Building patch
cscript WiLangId.vbs
"C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\output\Deploy\xxxSetup.msi"
Codepage 0
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.
Package language = 1033, ProductLanguage = 1033, Database codepage = 0
torch.exe -nologo -v -p -xi Latestwixpdb\xxxSetup.wixpdb
output\Deploy\xxxSetup.wixpdb -out xxxPatch\obj\Deploy\Diff.Wixmst
C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Latestwixpdb\xxxSetup.wixpdb :
error TRCH0228: The code pages of the outputs do not match. One output's
code page is '0' while the other is '1252'.
C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\output\Deploy\xxxSetup.wixpdb :
error TRCH0229: The location of the mismatched code page related to the
previous warning.
C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Latestwixpdb\xxxSetup.wixpdb :
error TRCH0279: The table definition of 'WixVariable' in the target database
does not match the table definition in the updated database. A transform
requires that the target database schema match the updated database schema.
C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Deploy.proj(30,5): error
MSB3073: The command "torch.exe -nologo -v -p -xi
Latestwixpdb\xxxSetup.wixpdb output\Deploy\xxxSetup.wixpdb -out
xxxPatch\obj\Deploy\Diff.Wixmst" exited with code 279.
Done building target "Patch" in project "Deploy.proj" -- FAILED.
-------------------------
It seems to be exactly the same as before I ran the script, how can that be?
Any suggestions?
Thanks!
Leo
2011/10/11 David Watson <dwat...@sdl.com>
> Hi,
>
> To support building patches against our old releases that were built with
> Wix
> 3.0. and now our release branches are being built on machines with Wix 3.5
> installed.
>
> So we have RTM msis from wix 3.0 these have codepage 0.
> We now make an updated MSIs with wix 3.5 which now forces a codepage onto
> MSIs.
>
> There is a step in our patch creation msbuild project that updates the
> codepage of the new version of the MSI back to 0 from 1252 (or whatever it
> is
> by default).
>
> That step is using the microsoft vbscript utility WiLangId.vbs available in
> the windows installer SDK.
>
> How all this relates to your workflow I don't know specifically you will
> probably need to call the vbs somehow (post build step?) so you can build
> patches against an old wix 3.0 MSI.
>
> Note : there is a bug about this but it will not be addressed until Wix 4.0
>
> http://sourceforge.net/tracker/?func=detail&aid=3134424&group_id=105970&atid=
> 642714
>
>
> Dave
>
> -----Original Message-----
> From: Leo Koivuniemi [mailto:universalserial...@gmail.com]
> Sent: 11 October 2011 14:55
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] error TRCH0228 : The codepages of the outputs
> donotmatch
>
> Oh thanks, will try that, if I find out how (very new to this, really). So
> I
> put that in deploy.proj right? And what do I have to do in my C++ code to
> run it?
>
> Really appreciate any help, thanks!
> Rgds Leo
>
> 2011/10/11 David Watson <dwat...@sdl.com>
>
> > We had this and had to run a step in our patch building scripts to set
> the
> > codepage to 1251.
> >
> > <Target Name="FixCodepage">
> > <Message Text="Fixing codepage" />
> > <Exec Command='cscript WiLangId.vbs "$(UpdateMSIDir)\$(MSIName)"
> > Codepage 0' />
> > </Target>
> >
> > See
> >
> >
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa369791(v=vs.85).asp
> > x
> > For the vbs file.
> >
> >
> > -----Original Message-----
> > From: Rob Mensching [mailto:r...@robmensching.com]
> > Sent: 11 October 2011 14:01
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] error TRCH0228 : The codepages of the outputs
> > donot
> > match
> >
> > Trying to create a patch across WiX versions is not supported. Patching
> is
> > very fragile and there are too many small changes in the tools that can
> > break patching.
> >
> > That said, you may be able to get this to work by explicitly setting the
> > code page on your Products. It's possible the default in WiX changed (due
> > to
> > some bug) and explicitly setting it might be able to get around it.
> >
> > On Tue, Oct 11, 2011 at 5:54 AM, Leo Koivuniemi <
> > universalserial...@gmail.com> wrote:
> >
> > > I am totally new to wix and have now a project in front of me using it.
> > > Upgrading to Visual Studio 2010 means I had to try to upgrade from 3.0
> to
> > > 3.5 of the wix package. I have solved some errors resulting from that,
> > but
> > > now I am stuck.
> > > When a patch is compiled I get the following error:
> > > error TRCH0228 : The codepages of the outputs do not match. One
> output's
> > > codepage is '0' while the other is '1251'.
> > > That is strange, because nothing else has changed in the project except
> > > from
> > > the wix version (still trying to make it run under VS2005 first).
> > > Googling I only really get one relevant hit, but the answers or
> comments
> > > don't tell me much.
> > > How do I deal with this easily? Anyone, please?
> > >
> > >
> >
> >
>
> -----------------------------------------------------------------------------
> > -
> > > All the data continuously generated in your IT infrastructure contains
> a
> > > definitive record of customers, application performance, security
> > > threats, fraudulent activity and more. Splunk takes this data and makes
> > > sense of it. Business sense. IT sense. Common sense.
> > > http://p.sf.net/sfu/splunk-d2d-oct
> > > _______________________________________________
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> >
> >
> > --
> > virtually, Rob Mensching - http://RobMensching.com LLC
> >
> >
>
> -----------------------------------------------------------------------------
> > -
> > All the data continuously generated in your IT infrastructure contains a
> > definitive record of customers, application performance, security
> > threats, fraudulent activity and more. Splunk takes this data and makes
> > sense of it. Business sense. IT sense. Common sense.
> > http://p.sf.net/sfu/splunk-d2d-oct
> > _______________________________________________
> > 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.
> >
> >
> >
> >
>
> -----------------------------------------------------------------------------
> -
> > All the data continuously generated in your IT infrastructure contains a
> > definitive record of customers, application performance, security
> > threats, fraudulent activity and more. Splunk takes this data and makes
> > sense of it. Business sense. IT sense. Common sense.
> > http://p.sf.net/sfu/splunk-d2d-oct
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> -----------------------------------------------------------------------------
> -
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
