As a consequence, WiX is not equally suited to all developers. The relatively steep learning curve (although our primary goal is to help overcome this difficulty with our tutorial) and the unavoidable exposure to the internal details and, sometimes, intricacies of the underlying Windows Installer technology suggest that less experienced developers or those who don't really need the unlimited and unparalleled performance WiX can offer might be better served by a simpler, GUI-based setup authoring tool, of which there are both commercial and freeware solutions available.
Awesome Amanda! I’m confused because you state title tags are to be 66 characters yet yours is 87, and being cut off in search results. Was that your intention? Help me understand why, writing as an authoritative SEO professional, blatantly promoting your own brand in this article, stating what we should do, would begin with contradictory statements and get it wrong.
Use canonical tags on duplicate content. If you need to publish content that is already published on another webpage (whether it is on your site or another website), use a canonical tag that tells search bots to ignore the duplicate content. This tag points the crawler to the original copy. It doesn’t add SEO value to your site, but it helps you avoid duplicate content penalties.
In addition to this integration, providing basically nothing more but developer comfort, WiX offers another level of integration, far more advantageous than the first one: the integration of the setup development process with that of the application. Traditionally, setup programs were only written when the main application had already been finished; often even by different developers. This approach requires a tedious and error prone process of collecting information about all the resources making up the application. While the files themselves are usually obvious, registry entries, services and most forms of inter-resource dependencies are often hard to reconstruct in a later stage: if solid development documentation is lacking, the setup developers have to collect all pieces of information from the original developers or try to extract it from the source code.
The toolset we are about to introduce, WiX, uses a different approach. Instead of a tool with a graphical interface that allows the developers to collect the files and other related tasks making up the installation process manually, it is much more like a programming language. Integrating perfectly with the usual process of creating applications, it uses a text file (based on the XML format) to describe all the elements of the installation process. The toolset has a compiler and a linker that will create the setup program just like our usual compiler creates our application from the source files. Therefore, WiX can be made part of any automated application build process very easily, be that based either on the classical technology of makefiles or the similar features of contemporary integrated development environments.
Finally, create web pages for the content you collected for the site and add the web page parts such as images, videos, headlines, and text. If a template includes pages that you don’t need, either delete those pages or save the pages as drafts. If you save the pages as drafts, you’ll have access to them in the future. There are a few essential pages that you should consider adding: