Abstract
For some reason, during my time as an application development consultant, I (Rob Walters) ended up working on a few projects where I was writing an InstallShield or Windows Installer package for a client. As a former developer working in various environments, I have made my own hypothesis that, in general, whoever gets stuck writing install scripts must feel like the little kid who got picked last for a kickball team in fifth grade. There is nothing glamorous about setup. Your code is run only when the application is installed, updated, or removed. If my hypothesis is correct and writing setup scripts is not the most exciting task for developers, one can assume that, in general, the overall experience to the end user might not be optimal. After all, as a developer, why should you put much effort in something that is going to run only a few times in the life of the product?
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Rob Walters, Grant Fritchey
About this chapter
Cite this chapter
Walters, R., Fritchey, G. (2012). Planning and Installing SQL Server 2012. In: Beginning SQL Server 2012 Administration. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-3982-6_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3982-6_2
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-3981-9
Online ISBN: 978-1-4302-3982-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books