This is the seventh in a series of notes about UAC in MSI. Per the earlier caveat, these are just my notes and not an official position from the Windows Installer team. The previous entries
When talking about UAC in MSI, I need to lay the foundation of how the Windows Installer architecture works. Given most programmers haven't worked with the type of technology and architecture underlying the Windows Installer, I start with drawing the following diagram.
In the earlier review in trying to publish my notes, I've received feedback that this is not a customer ready diagram. Fair feedback I said but I'm not a graphic artist and I've been able to use this as a tool to explain things in person. I don't know that this will play to a blog any better than it played in the early review document but it's the best I've got. I apologize in advance if I loose you here as it was suggested.
There are three regions of the drawing
The workflow starts in the upper left hand corner and proceeds to the lower left hand corner of the diagram.
On the whiteboard, I can look at the person's reaction to tailor down the "saw tooth" to the problem they are interested in. If the trajectory of the customer concern was small and problem specific, I'd cut to the chase and draw the red circle in this diagram to represent their actual problem. If the trajectory of the customer concern was broad or involved integration, I'd talk through each of these lines and their relationships to the Windows Installer architecture.
The next set of blog entries in this series will talk to customers concerns that are small and problem specific. If your a customer with a passion to understand more about the Windows Installer architecture, I'm trusting you'll find these instances interesting cases and hang in there until I get to the next architectural bucket.