When a company builds and ships software, the installation process is often the first opportunity for a customer to view the the product and the company--and the installation experience can make or break a lasting impression. So this book is ideal for companies and developers who want to impress their clientele. This book covers every aspect of using the Windows Installer, the underlying installer technology in Windows. A valuable tool for you software developers, this book helps ensure thorough and reliable installation for your customers. Most other books for software developers end too abruptly and omit critical information, like how to create the necessary installation software. But The Definitive Guide to Windows Installer picks up where the other books trail off.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Commentaires client les plus utiles sur Amazon.com (beta)
16 internautes sur 16 ont trouvé ce commentaire utile
Good But Not Definitive28 juillet 2005
William E. Blum
- Publié sur Amazon.com
I say it's not definitive because I think that means there's nothing more to be said on the subject. The MS Windows Installer technology is huge, and it would take a book five times the length of this one to be definitive. This book describes the client/server architecture of the installer and explains about the important tables in the database. It demonstrates how to make an installation package with Visual Studio, but assumes you will be using a commercial package in real life. To get the most out of the book, you'll need to install Orca, which is available in the Microsoft Installer SDK. Orca lets you view and edit the tables in an installation package.
After a bit of orientation, each chapter tackles a common installation topic: patches, ASP.NET, .NET assemblies, windows services, and the installer APIs. Wilson is good about explaining why something should be done a certain way and giving you the background to understand it.
My only disappointment is that, due to the shortness of the book, there is no room to go into more detail about some of the standard actions. I'd like to have seen an example of the minimal set of actions needed to install a file; kind of the hello world of installer. The beginning example he provides is built with Visual Studio, and I'm sure it puts in a lot more actions than are really needed, so it's hard to mentally associate what the package is doing with the action records that are doing it. To really understand how the installer works, you should be able to build a package from scratch with Orca.
There are few or no typos, which is amazing for a computer book nowadays, and I didn't find any errors of fact.
25 internautes sur 30 ont trouvé ce commentaire utile
Very elegant new approach18 juin 2004
- Publié sur Amazon.com
Many developers who write applications for a Microsoft operating system know all too well of installation hazards. The possibility of introducing DLLs that are incompatible with existing DLLs, for example. Plus lots more things that could fail. Wilson starts off his book with a listing of what could traditionally go wrong in an installation. Not to put too fine a point on it, but this was a wretched state of affairs. You typically had programming expertise in your particular field. But there should have been no a priori reason why this expertise should have to stretch to the installation process. Right? Wilson gives an alternative. He details how you can use Windows Installer to install and uninstall your application. The process is still nontrivial, mind you. Which is why we have a book of this length. But it shows how, if you fit your application within WI's strictures, then the entire install is now much easier and safer. Perhaps the single best advantage is that WI makes your install a transaction. Either it all works, or the install will fail and your system will be unaffected. Atomic. We have rollback ability. Those of you familiar with SQL and transaction processing will recognise this. Wilson shows that WI is in fact based on SQL tables and relational processing. Some people at Microsoft made a nice design! By undergirding the installation with SQL tables. It lets WI have an inner coherent structure, into which third party applications can fit, in a disciplined way. Plus, it allows the panoply of SQL queries. At the right level, it is an elegant approach.
4 internautes sur 4 ont trouvé ce commentaire utile
An excellent place to start to learn about Windows Installer11 juin 2009
- Publié sur Amazon.com
I purchased this book in a panic after I inherited a pile of WiX installer responsibilities as a result of a layoff. We live in interesting times.
This book covers creation of Windows Installers using Visual Studio. (This book does not cover WiX.) A key point is that an MSI file is a database, comprised of many tables. This books shows hows to exploit this architecture.
The process of creating installers with Visual Studio is a little unusual, but makes sense when you try it. Visual Studio can produce an impressive, somewhat customized installer quite easily. I literally started with nothing, and in 12 minutes, I had built an installer for a large project. However, the resultant installer may not be exactly what you had in mind. To customize the installer, use Orca to edit the resultant MSI installer manually. Write scripted SQL queries to edit the resultant process automatically, possibly as a post-build event. This book takes you through that process.
This book advanced my skills from knowing nothing about installers to being the local expert. (I am now converting WiX installers to Visual Studio installers.) It was a great starting point, but I found that I needed to search MSDN to find some details. The book is VB-centric with regards to scripting, which for me is a negative, but may be positive for you. I would like to see coverage of MSI manipulation in tools more typical of a build environment, namely Perl or PowerShell.
In summary, read this book to get the big picture and lots of details, and then plan to get other details from MSDN.
3 internautes sur 4 ont trouvé ce commentaire utile
Very useful book11 juin 2007
- Publié sur Amazon.com
This book covers in a simply and useful way several aspects of Windows Installer. I suggest this book as a "bible" for those programmers who needs to customize their installation procedure. Obviously this book does not resolve all the problems related to Windows Installer, but offers a valid guide to start to resolve them.
The NOT Definitive Guide to Windows Installer29 novembre 2014
- Publié sur Amazon.com
This review was originally written in 2006:
1. 50,000 Foot Overview a. Covers a few (it even mentions that the list is NOT exhaustive) of the issues with installations b. Future NOT covered c. Summary introduces an entirely new and IMPORTANT concept 2. Hello World a. Same as every example on the internet b. GUIDS, an integral part of the Installer are only overviewed in a few paragraphs c. A section covering the Installer API, huh why is this in with the Hello World example 3. COM a. This chapter SUCKS b. Does mention the issues with Shared Components c. Merge Module, why here? d. More API stuff stuck in the middle of Side-by-side install… e. Does NOT cover i. Isolated Applications ii. COM+ Applications iii. Self Registration vs. Registry Table use iv. Assemblies v. GAC vi. COM Interop vii. Strong naming viii. Uninstall of COM Components ix. Upgrade of COM Components and the issues with Interface changes. 4. Search and Conditionals a. Not much here that is not covered in the SDK 5. Sequence and Custom Actions a. Some stuff covered here b. Leaves out the issues with execution order and custom actions c. Covers nested installations which are no longer supported 6. How Do you Fix It? a. Covers updates only nothing about the Repair feature b. Does cover several other issues decently 7. ASP .NET Installations a. Sample app b. Does cover not installing to the root 8. .Net Assemblies a. GACaphobia i. More FUD ii. Does not really cover GAC versioning at all b. COM Clients i. Not in the chapter with COM c. Acceptable coverage of other areas. 9. Install Design a. One great point here about Application prerequisites b. A good discussion regarding the issues with, and possible solutions to those issues, when dealing with self-extracting executables and installation prerequisites. c. Rounds out with a decent discussion of UI and several other issues 10. Windows Services a. Good Coverage of Win32 and .NET Service installations 11. The GAC and Updating Assemblies a. Ultimately good coverage of GAC issues, and how to work through them. b. However, this chapter still presents an unhealthy dose of FUD regarding the GAC 12. Using Patches a. Update the Hello World example b. Did not read this chapter in-depth 13. Installation Environments a. Terminal Services b. 64 Bit machines c. Privileges d. Internet Installations 14. Tips and Tricks a. One warning, “VBScript Custom Actions Are Easy” does NOTHING to cover the issues regarding Custom Actions in General and specifically the issues with VBScript custom actions. This Tip is downright dangerous. 15. Installer API 16. Tools a. Leaves out the free tools, the most glaring Omission here is WIX which is used by most internal MS installer teams, and is free.