|This is the talk page for discussing improvements to the Windows Installer article.|
|WikiProject Computing / Software||(Rated B-class, Low-importance)|
|WikiProject Microsoft / Windows||(Rated B-class, Mid-importance)|
- 1 advertisement
- 2 uninstall
- 3 unattended?
- 4 lack of cross platform support and free software creators
- 5 Section 1.1 unclear
- 6 Updates
- 7 Self-Repair and Package Integrity are not mentioned as "Advantages" while "Disadvantages" has irrelevant and over-opinionated comments.
- 8 what do they mean by "modern" windows
- 9 Multiple issues with 'Disadvantages' section
- 10 Table of Contents link to Advertisement
- 11 Criticism section needs to be written
- 12 Tool inclusion criteria
- 13 InstallShield is shareware?
The article states 'The user must have administrator privileges to complete the advertised installation...'. This is clearly contradicted in http://support.microsoft.com/kb/259459, which states 'The administrator uses elevated privileges to advertise the package. If a nonadministrator user then installs the application, the installation can run with elevated privileges.'
it might be worth mentioning how to uninstall Windows Installer packages --Spoon! 06:34, 6 March 2007 (UTC)
MSI installers are great for network admins... someone with more wiki skills should add in that MSIs can be easily deployed through ADs. 18.104.22.168 22:46, 23 March 2007 (UTC)
lack of cross platform support and free software creators
It seems one disadvantage is lack of free software for creating MSI, also across platforms. With NSIS, you can build installer packages for Windows on a GNU/Linux system. With MSI, there does not seem to exist a solution for this as of yet. 10:59, 30 October 2007 (UTC)
- WiX is a free package that allows you to build MSIs.
- As for lack of cross-platform support, do you mean making install packages that will work on different platforms, or just the creation of the MSIs that you would like to be able to do on a non-Windows platform? --RenniePet 13:34, 30 October 2007 (UTC)
- The latter, I assume.
Section 1.1 unclear
I have added the "cleanup-confusing " template, as it suggests both a "product", in this sense, may AND may not be more than a single program.Bettering the Wiki 03:56, 20 July 2008 (UTC)
I was surprised when my TL mentioned it also related to update menegement for windows.
Self-Repair and Package Integrity are not mentioned as "Advantages" while "Disadvantages" has irrelevant and over-opinionated comments.
Why is self-repair not mentioned as a feature, if a poorly written install or uninstall toasts some portion of your Windows Installer managed installation, when the application is launched the stub MSI database is scanned and missing components are restored if an admin user is logged in, and if it is just a normal user, they will have a very specific error to call support with, and the application can be repaired by an admin user (even remotely using VBScript).
Also, any per-user settings for your application are propagated using this technology, and the user does not have to be an administrator for that to happen. Most enterprises deploy applications using a specific (domain or local) account. —Preceding unsigned comment added by 22.214.171.124 (talk) 16:21, 15 April 2009 (UTC)
what do they mean by "modern" windows
what do they mean, modern windows as in 3.1 up, 95 up, 98 up, 98 SE up, ME up, XP and up.126.96.36.199 (talk) 19:12, 14 July 2009 (UTC) The Windows Installer (previously known as Microsoft Installer) is an engine for the installation, maintenance, and removal of software on "modern"Italic text Microsoft Windows systems. —Preceding unsigned comment added by 188.8.131.52 (talk) 19:14, 14 July 2009 (UTC)
Multiple issues with 'Disadvantages' section
|“||During installation, a copy of the .MSI package may be[weasel words] copied to the user's temporary directory prior to installation, even if the same package is stored locally. InstallShield products[clarification needed Installers created by InstallShield or products with InstallShield brand name?] sometimes[weasel words] create an additional copy of the MSI in the temporary directory[clarification needed Will there be two copies of MSI in temporary folder or one?] if the install package is localized[clarification needed What does localized means? "Stored locally"? or "customized for a certain culture" as used below?]. In general, the author of the MSI package controls this to an extent[weasel words][clarification needed To what extent?].[original research?]
To prevent requiring the original installation source, Windows Installer packages and patches are cached in the %WinDir%\Installer directory (hidden by default). If the package builder chooses to use Installation on Demand or Repair feature in the package, the entire package (except for localization messages) and a stub .MSI package are copied to the %WinDir%\Installer directory.[original research?] A machine may be configured via group policy to create logs of all installation operations, such logs being created in the Windows temporary directory. These log files may be quite large with a full verbose log for a large package constituting several tens of megabytes.[original research?] The log files can be useful for diagnostics, but if a user performs install related operations (install, uninstall, modify, repair or patching) with Windows Installer often, the space consumed by the logs can get out of hand.[original research?]
- Hi, Little Professor
- Thanks for your efforts to improve the article readability. Yes, I confess the article readability was not very pleasing.
- However, completely removing those tags is also wrong. Removing those tags is analogous to accusing someone of "committing crimes" and arresting him on that effect. So, I think we should leave mellow versions of those tags in place. One or two of them can also be ignored. In the end, they are just six tags. Six is not counted as tag bombing, is it?
- Fleet Command (talk) 11:38, 8 September 2009 (UTC)
I can't figure out why it's not working... on my browser, the Advertisement subsection is contained in the source for the page, but it is not displayed. Is this a problem for others as well? Amit ► 21:19, 25 August 2010 (UTC)
Criticism section needs to be written
Tool inclusion criteria
I would like to include a tool of mine called SharpSetup in the list of tools. As the tool has a paid version I do have a commercial interest in such inclusion. However, I really do think that the tool is more relevant to the list that 7-zip (which just happens to unpack msi files) or IsWix which according to codeplex stats got exactly two changesets this year and two discussion topics in its lifetime. So again: what are the inclusion criteria and does SharpSetup qualify? — Preceding unsigned comment added by Grobelny (talk • contribs) 20:20, 1 October 2013 (UTC)
- I'm going to trim the list down to only entries with either their own article and products from companies with their own articles. --Ronz (talk) 23:38, 20 June 2014 (UTC)
In the table of installers near the end of the article, it is stated that InstallShield is shareware. They have a free demo version, but the main version costs big $$$! — Preceding unsigned comment added by 184.108.40.206 (talk) 19:44, 31 March 2014 (UTC)