vs中丢失帮助查看器(HelpViewer)如何处理
来源:互联网 发布:分布式数据库架构师 编辑:程序博客网 时间:2024/04/28 23:16
参考网上的一个教程,在此做一下记录!
1. 在ios镜像安装文件中找到 packages\Help 路径。
2. 打开控制台命令,cd到这个路径下
3. 在控制台中键入以下命令进行安装
msiexec /i help3_vs_net.msi vs_setup=1
有的时候还会出现点击帮助管理器,管理器一直卡在启动页面的情况,即使多次卸载重装help viewer也解决不了,这种情况貌似没有别的办法,点击控制面板,卸载程序,到vs然后修复即可,有时候即使修复问题仍然没有解决,可以尝试将help viewer(帮助管理器)删除,按照上面的方法再次装一遍,还不行,我也没辙!
关于msiexec的用法:
The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives you full control over the installation process, allowing you to set:
windows安装技术使用Msiexec.exe来安装msi和msp的包,这种工具使你能够完全控制安装过程,允许你设置:
- install options (install, uninstall, administrative install, advertise a product)
- 安装选项(安装,卸载,管理员身份安装...)
- display options (full, basic or no UI during the installation)
- 表现的选项(完全,基本,或者在安装时没有UI)
- restart options (if the machine will be restarted after the installation)
- 重启选项(在安装完成后如果机器要重启的话)
- logging options
- 日志选项
- update options (apply or remove updates)
- 更新选项(运用或移除更新)
- repair options (only for an installed package)
- 修复选项(只为一个已经安装好了的包)
- public properties which are used by the installation
- 安装时软件公开的权限(比如当前用户和全部用户)
The usual form of the msiexec command line is this:
msiexec命令的用法如下:
msiexec.exe <install_option> <path_to_package> [package_parameters]
Install Options
When launching an installation package, you can set the install type through these options:
安装一个包是,你可以选择以下选项:
msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>
- /i - normal installation 一般安装
- /a - administrative install 管理员形式安装
- /j - advertise the product
- u - advertise to the current user 只为当前用户安装
- m - advertise to all users 全部用户
- /g - the language identifier used by the advertised package
- /t - apply transform to advertise package
- /x - uninstall the package 移除包
Sample command line:
例子
msiexec.exe /i "C:\Example.msi"
Display Options
The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:
msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]
- /quiet - quiet mode (there is no user interaction)
- /passive - unattended mode (the installation shows only a progress bar)
- /q - set the UI level:
- n - no UI
- b - basic UI
- r - reduced UI
- f - full UI
Sample command line:
msiexec.exe /i "C:\Example.msi" /qn
Restart Options
Sometimes an installation overwrites files which are in use or needs to reboot the machine in order to finish it. The reboot policy used by the installation can be set through these options:
msiexec.exe /i <path_to_package> [/norestart][/promptrestart][/forcerestart]
- /norestart - the machine will not be restarted after the installation is complete
- /promptrestart - the user will be prompted if a reboot is required
- /forcerestart - the machine will be restarted after the installation is complete
Sample command line:
msiexec.exe /i "C:\Example.msi" /norestart
Logging Options
When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:
msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>
- /L - enable logging
- i - include status messages
- w - include non-fatal warnings
- e - include all error messages
- a - mention when an action is started
- r - include action-specific records
- u - include user requests
- c - include the initial UI parameters
- m - include out-of-memory or fatal exit information
- o - include out-of-disk-space messages
- p - include terminal properties
- v - verbose output
- x - include extra debugging information
- + - append to an existing log file
- ! - flush each line to the log
- * - log all information, except for v and x options
- /log - the equivalent of /l*
Sample command line:
msiexec.exe /i "C:\Example.msi" /L*V "C:\package.log"
Update Options
The Windows Installer command line can apply or remove updates (patches for example) through these options:
msiexec.exe [/p][/update][/uninstall[/package<product_code_of_package>]] <path_to_package>
- /p - install a MSP patch. When installing a patch silently, you need to set REINSTALLMODE property to "ecmus" and REINSTALL to "ALL". Otherwise the patch will simply update the MSI cached on the target machine.
- /update - apply updates (if there are multiple updates, you can separate them through the ";" character).
- /uninstall - remove an update for a product (if there are multiple updates, you can separate them through the ";" character)
- /package - specifies the package for which the update is removed.
Sample command lines:
msiexec.exe /p "C:\MyPatch.msp"msiexec.exe /p "C:\MyPatch.msp" /qb REINSTALLMODE="ecmus" REINSTALL="ALL"msiexec.exe /update "C:\MyPatch.msp"msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318} /package {AAD3D77A-7476-469F-ADF4-04424124E91D}
Repair Options
If you have an installed package, you can use the Windows Installer command line for repairing it:
msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>
- /f - repair a package
- p - repair only if a file is missing
- o - repair if a file is missing or an older version is installed
- e - repair if file is missing or an equal or older version is installed
- d - repair if a file is missing or a different version is installed
- c - repair if a file is missing or the checksum does not match the calculated value
- a - forces all files to be reinstalled
- u - repair all the required user-specific registry entries
- m - repair all the required computer-specific registry entries
- s - repair all existing shortcuts
- v - run from source and recache the local package
Sample command line:
msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}
Set public properties
The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY="value".
Sample command line:
msiexec.exe /i "C:\Example.msi" MY_PROP="myValue"
- vs中丢失帮助查看器(HelpViewer)如何处理
- 教你如何让VisualStudio的HelpViewer帮助文档独立运行
- 如何查看Android帮助文档
- 如何查看VS中预设的路径变量
- eclipse中即时查看帮助
- PowerShell中查看命令帮助
- 【NTLDR文件丢失如何处理】
- Ipad照片丢失如何处理
- Direct3D中设备丢失处理
- 批处理的“帮助”如何来查看
- 如何运行Perl和查看帮助
- 如何查看gdb子命令的帮助
- 如何 echo --help查看echo帮助
- 如何充分利用python的帮助查看
- vs中如何像vc6一样增加windows消息处理
- VS2010帮助查看器推荐
- VS2010帮助查看器推荐
- VS2010帮助查看器推荐
- 在屏幕上显示0—360的cos(x)曲线与直线f(x)=45*(y-1)+31的迭加图形。
- 汉诺塔II
- Q3.6 sort a stack in ascending order
- 解决eclipse出现This Android SDK requires Andro...date ADT to the latest version.问题
- 《敏捷软件开发》读书笔记(四)
- vs中丢失帮助查看器(HelpViewer)如何处理
- 图解数据结构之算法
- TortoiseSVN中Branching和Merging实践
- 邢帅——一个逆袭的草根
- 多柱汉诺塔最优算法设计探究
- Eclipse中clear工程以后,R文件消失及解决办法
- pitch yaw roll 的区别
- 黑马程序员——还没有想好
- 【第27篇】JackJson的ObjectMapper封装