如下圖所示,安裝時會出現”無法剖析屬性’type’的值。錯誤為:無法載入檔案或組件”的錯誤訊息

螢幕擷取畫面 2022-02-22 165701.jpg

解決方式:

  1. 如下圖所示,進入 c:\program files(x86)\Common Files\microsoft shared\VSTO\10.0 目錄 或 c:\program files\Common Files\microsoft shared\VSTO\10.0 目錄,尋找一個叫做 VSTOInstaller.exe.config的檔案

Untitled

  1. 將VSTOInstaller.exe.config改名為VSTOInstaller.exe.config.old

Untitled

  1. 點擊setup.exe檔,開始安裝本程式

Untitled

  1. 安裝好程式後,再把剛剛的VSTOInstaller.exe.config.old改回VSTOInstaller.exe.config即可

Untitled

  1. 以下為英文參考說明

"The value of the property 'type' cannot be parsed. The error is: Could not load file or assembly 'Microsoft.Office.BusinessApplications.Fba, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependancies. The system cannot find the file specified. (C:\Program Files (x86)\Common Files\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe.Config line 10)”

  1. After trying a couple of basic steps (repairing VSTO 2010, Office) we tried re-naming the VSTOInstaller.exe.Config to 'hide' it from the installation and it appears to be working. Client then re-named the file back as a precaution, in case anything else was using this file.
  2. This clarification may help: Apparently, VSTOInstaller.config is present after standard installations of some Office products, at least under "Program Files\..." on a 64-bit machine. When present, it references "Microsoft.Office.BusinessApplications.Runtime.DeploymentAction.HttpFbaRequestCreator". This is not a problem. On some machines (I also have customers with this problem) there is, in addition to VSTOInstaller.config, a file VSTOInstaller.exe.config. This file takes preference over VSTOInstaller.config when it exists. In this file (VSTOInstaller.exe.config) the reference is to "Microsoft.Office.BusinessApplications.Fba.HttpFbaRequestCreator" and this is the case that fails. So someone needs to find out who is installing VSTOInstaller.exe.config, not who is installing VSTOInstaller.config.
  3. This should definitely be handled as a highest priority bug at Microsoft, since this is currently killing Office Add-In businesses, and any workaround which involves Administrator priviledges is not ok, since that goes against the entire Add-In business model, which says any user can install. The workaround is “run as admin and then run as the user”. Here some details of the initial state of the workstation (before doing anything) 1 – the GAC does not contain any Microsoft.Office.BusinessApplications.Fba, 2 - VSTOInstaller.exe.config is present in x86 path (C:\Program Files (x86)\Common Files\Microsoft Shared\VSTO\10.0) but not in x64 (C:\Program Files\Common Files\Microsoft Shared\VSTO\10.0) Other remarks 1 – After having run the installer as admin I found Microsoft.Office.BusinessApplications.Fba v14.0.0.0 registed inside the GAC 2- monitored installation process running as admin, found there are calls to c:\windows\systems32\consent.exe
  4. 參考來源 https://social.msdn.microsoft.com/Forums/vstudio/en-US/c26d3f76-be37-4e1b-9d9a-84edae351e18/problem-with-vstoinstallerconfig?forum=vsto