Add your comments
DLS Archives
May 2012
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC
Reader Comments (Page 1 of 1)
(Unverified)Jun 5th 2007 4:21PM
"You can do teh same things witha good 3r dparty system as you can with microsoft. the only real differnce is window sinstaller is part of the os"
That's exactly my point at the end of the article. I can certainly have the same capability with 3rd party system but MSI provides a lot of built-in functionality that make life easier to deal with UAC.
And setting execution level at the beginning of the installation process is just one of many aspect required for adapting existing installer for Vista. What about the repair process or Advertising? MSI allows both without UAC elevation out of the box, whereas extra work is needed for 3rd party system. In fact, Advertising is not possible without MSI running as an OS service.
Again, the question for developers is whether to spend the time on the system they already know (NSIS, Inno, InstallShield, etc.) or convert to MSI which requires starting from scratch.