Click here to Skip to main content
15,886,831 members
Articles / Windows Installer

Creating a Localized Windows Installer & Bootstrapper: Part 3

Rate me:
Please Sign up or sign in to vote.
4.60/5 (3 votes)
25 Feb 2013CPOL5 min read 55.8K   537   17  
This series of articles is a complete end-to-end solution for building a localizable Windows Installer & Bootstrapper using some real-world requirements.
<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="en-GB" xmlns="http://schemas.microsoft.com/wix/2006/localization" Codepage='1252'>
  <String Id='LANG' Overridable="yes">1033</String>
  <String Id="Feature.Title" Overridable="yes">MyApp Core</String>
  <String Id="Feature.Description" Overridable="yes">The main executable.</String>
  <String Id="Installer.Description" Overridable="yes">MyApp developed by TheCodeKing.</String>
  <String Id="Installation" Overridable="yes">Installation</String>
  <String Id="Net40ClientRequired" Overridable="yes">This application requires Microsoft .NET Framework 4 Client Profile. Please install the framework and then run this installer again.</String>
  <String Id="Windows7Required" Overridable="yes">This application only runs on Windows 7.</String>
  <String Id="HardwareFail" Overridable="yes">This application cannot be installed on this hardware.</String>
</WixLocalization>

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect
United Kingdom United Kingdom
Mike Carlisle - Technical Architect with over 20 years experience in a wide range of technologies.

@TheCodeKing

Comments and Discussions