我们正在创建一个通过 Office 2007 PIA 使用 Excel Interop 的软件项目(VS 2010、.NET 3.5 SP1)。我们正在将其部署到 Internet 以进行 clickonce 安装。在大多数情况下，它工作得很好。但最近一位客户在安装它时遇到了问题(请参阅下面的日志文件)。
据我在互联网上的阅读发现，它可能在某种程度上与另一个应用程序注册的 PIA 有关。
谁能提供一些有用的提示(也许还有关于该主题的一些阅读资源)？
非常感谢!
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.269
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.269 (RTMGDR.030319-2600)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : http://***/***.application
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Deployment Provider url : http://***/***.application
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
Application url : http://***/***.manifest
Server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
IDENTITIES
Deployment Identity : ***, Version=1.1.0.893, Culture=neutral, PublicKeyToken=b5867eb738db6c5c, processorArchitecture=msil
Application Identity : ***, Version=1.1.0.893, Culture=neutral, PublicKeyToken=b5867eb738db6c5c, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://***/***.application resulted in exception. Following failure messages were detected:
+ Exception occurred loading manifest from file Microsoft.Office.Interop.Excel.dll: the manifest may not be valid or the file could not be opened.
+ File Microsoft.Office.Interop.Excel.dll is not a valid Portable Executable (PE) file.
+ File {0} is not a valid Portable Executable (PE) file.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [9/20/2012 2:44:56 PM] : Activation of http://***/***.application has started.
* [9/20/2012 2:44:57 PM] : Processing of deployment manifest has successfully completed.
* [9/20/2012 2:44:57 PM] : Installation of the application has started.
* [9/20/2012 2:44:58 PM] : Processing of application manifest has successfully completed.
* [9/20/2012 2:45:00 PM] : Found compatible runtime version 2.0.50727.
* [9/20/2012 2:45:00 PM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil.
* [9/20/2012 2:45:00 PM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.
* [9/20/2012 2:45:00 PM] : Detecting dependent assembly WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil using WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=msil.
* [9/20/2012 2:45:00 PM] : Detecting dependent assembly System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.
* [9/20/2012 2:45:00 PM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil.
* [9/20/2012 2:45:00 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [9/20/2012 2:45:34 PM] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
- Exception occurred loading manifest from file Microsoft.Office.Interop.Excel.dll: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ManifestLoadExceptionHelper(Exception exception, String filePath)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath)
at System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e)
at System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e)
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.IO.IOException
- File Microsoft.Office.Interop.Excel.dll is not a valid Portable Executable (PE) file.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.PEStream.ConstructFromFile(String filePath, Boolean partialConstruct)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath)
--- Inner Exception ---
System.ComponentModel.Win32Exception
- File {0} is not a valid Portable Executable (PE) file.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.PEStream.DosHeader..ctor(FileStream file)
at System.Deployment.Application.PEStream.ConstructPEImage(FileStream file, Boolean partialConstruct)
at System.Deployment.Application.PEStream.ConstructFromFile(String filePath, Boolean partialConstruct)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
最佳答案
我们有一个与我们自己的 ClickOnce 应用程序几乎相同的日志文件，尽管它在下载第一个文件时失败(ClickOnce 似乎按字母顺序下载文件)。我们让用户将部署我们的应用程序的域列入白名单，问题已解决。
https://answers.atlassian.com/questions/154127/sourcetree-for-windows-install .
在我的店里，ClickOnce 通常用于 super 锁定的 IT 环境(工厂的机器只有我们的软件可用，用户甚至无法将文件保存到他们的桌面)，因此将站点列入白名单可以解决一系列问题.
关于c# - Excel Interop DLL 的 Clickonce 异常，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/12565250/