UAC in MSI Notes: How I Root Cause The Problem

How UAC in Vista will impact your Setup

InstallSite Blog — Fri, 22 Sep 2006 10:43:38 GMT

Windows Vista introduces a security concept called User Account Control (UAC) which has multiple impacts

DevInstall.Com’s WebLog » Understanding UAC in Vista and Windows Installer

DevInstall.Com’s WebLog » Understanding UAC in Vista and Windows Installer — Mon, 25 Sep 2006 05:36:14 GMT

PingBack from http://blog.devinstall.com/?p=6

How Windows Installer interacts with UAC in Windows Vista

Aaron Stebner's WebLog — Sun, 01 Oct 2006 04:44:21 GMT

Robert Flaming has been posting a series of articles describing how Windows Installer interacts with...

re: UAC in MSI Notes: How I Root Cause The Problem

Tue, 10 Oct 2006 02:02:48 GMT

I am not sure what is meant by "Windows Installer itself has been around since 1995" - it has only been around since the release of Office 2000.

I think the first generation of user and machine seperation was the unified "Registry" memory resident namespace having a user oriented section and a computer oriented section. This approach propagated into NT from it's birth on OS/2.

Having a single memory resident namespace that is only complete when a specific user context is completely loaded has actually (IMHO) been the source of much frustration and work in software installation since it always needs to be accounted for. File based name spaces can be accessed from any user context since - such as UNIX home directories and computers directories for storing applications.

.NET is actually reeling us back to the pre-registry days by allowing the storage the equivalent of COM registrations on disk (manifest files) alleviating the burden of the constant need to maintain a memory based, user specific name space.