.net-4.0 - ClickOnce list

Question

我们目前正在通过 ClickOnce 部署 WPF 4 应用程序并且有安装失败的场景。

如果用户没有 .NET 4.0 完全安装并尝试安装我们的应用程序，则框架安装正常，但应用程序安装失败。如果我们再次重新运行安装，应用程序安装正常。

这是日志的副本:

    PLATFORM VERSION INFO
    Windows             : 6.1.7600.0 (Win32NT)
    Common Language Runtime     : 2.0.50727.4927
    System.Deployment.dll         : 2.0.50727.4927 (NetFXspW7.050727-4900)
    mscorwks.dll             : 2.0.50727.4927 (NetFXspW7.050727-4900)
    dfdll.dll             : 2.0.50727.4927 (NetFXspW7.050727-4900)
    dfshim.dll             : 4.0.31106.0 (Main.031106-0000)

SOURCES
    Deployment url            : [URL REMOVED]
                        Server        : Apache/2.0.54
    Application url            : [URL REMOVED]
                        Server        : Apache/2.0.54

IDENTITIES
    Deployment Identity        : Graphicly.App.application, Version=0.3.2.0, Culture=neutral, PublicKeyToken=c982228345371fbc, processorArchitecture=msil
    Application Identity        : Graphicly.App.exe, Version=0.3.2.0, Culture=neutral, PublicKeyToken=c982228345371fbc, 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.
    * Dependency Graphicly.WCFClient.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.WCFClient.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Microsoft.Surface.Presentation.Design.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Microsoft.Surface.Presentation.Design.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency GalaSoft.MvvmLight.WPF4.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file GalaSoft.MvvmLight.WPF4.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.Infrastructure.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.Infrastructure.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.AutoUpdater.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.AutoUpdater.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency System.Windows.Interactivity.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file System.Windows.Interactivity.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Microsoft.Surface.Presentation.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Microsoft.Surface.Presentation.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.Fonts.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.Fonts.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.Reader.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.Reader.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Microsoft.Surface.Presentation.Generic.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Microsoft.Surface.Presentation.Generic.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.Controls.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.Controls.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.SocialNetwork.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.SocialNetwork.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.Archive.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.Archive.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency Graphicly.App.exe cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file Graphicly.App.exe: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Dependency GalaSoft.MvvmLight.Extras.WPF4.dll cannot be processed for patching. Following failure messages were detected:
        + Exception occurred loading manifest from file GalaSoft.MvvmLight.Extras.WPF4.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.
    * Activation of [URL REMOVED] resulted in exception. Following failure messages were detected:
        + Exception occurred loading manifest from file GalaSoft.MvvmLight.Extras.WPF4.dll: the manifest may not be valid or the file could not be opened.
        + Cannot load internal manifest from component file.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
    No transaction error was detected.

WARNINGS
    * The file named Microsoft.Windows.Design.Extensibility.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Ionic.Zip.Reduced.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Newtonsoft.Json.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Microsoft.WindowsAzure.StorageClient.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Dimebrain.TweetSharp.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Microsoft.Windows.Design.Interaction.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named HtmlAgilityPack.dll does not have a hash specified in the manifest. Hash validation will be ignored.
    * The file named Facebook.dll does not have a hash specified in the manifest. Hash validation will be ignored.

OPERATION PROGRESS STATUS
    * [20/05/2010 09:17:33] : Activation of [URL REMOVED] has started.
    * [20/05/2010 09:17:38] : Processing of deployment manifest has successfully completed.
    * [20/05/2010 09:17:38] : Installation of the application has started.
    * [20/05/2010 09:17:39] : Processing of application manifest has successfully completed.
    * [20/05/2010 09:17:40] : Request of trust and detection of platform is complete.

ERROR DETAILS
    Following errors were detected during this operation.
    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.WCFClient.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Microsoft.Surface.Presentation.Design.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file GalaSoft.MvvmLight.WPF4.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.Infrastructure.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.AutoUpdater.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file System.Windows.Interactivity.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Microsoft.Surface.Presentation.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.Fonts.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.Reader.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:40] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Microsoft.Surface.Presentation.Generic.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.Controls.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.SocialNetwork.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.Archive.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file Graphicly.App.exe: 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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file GalaSoft.MvvmLight.Extras.WPF4.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.FileDownloader.AddFilesInHashtable(Hashtable hashtable, AssemblyManifest applicationManifest, String applicationFolder)
        --- Inner Exception ---
        System.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:

    * [20/05/2010 09:17:41] System.Deployment.Application.InvalidDeploymentException (ManifestLoad)
        - Exception occurred loading manifest from file GalaSoft.MvvmLight.Extras.WPF4.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.FileDownloader.PatchSingleFile(DownloadQueueItem item, Hashtable dependencyTable)
            at System.Deployment.Application.FileDownloader.PatchFiles(SubscriptionState subState)
            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.Deployment.Application.DeploymentException (InvalidManifest)
        - Cannot load internal manifest from component file.
        - Source:
        - Stack trace:


COMPONENT STORE TRANSACTION DETAILS
    No transaction information is available.

我很困惑。这可能是什么？

我注意到安装后立即运行的 dfsvc.exe 位于 .NET 2 文件夹中。当我重新运行安装程序时，dfsvc.exe 位于 .NET 4 文件夹中。

我一直在与 Microsoft 的支持人员交谈，我们发现由于安装和卸载以前版本的 .NET 4(在我们的例子中是 beta)，它留下了几个文件。当执行 .NET 安装程序时，它需要重命名一些文件然后重新启动，但由于文件是以前版本留下的，安装程序认为重命名已经发生，并没有请求重新启动。

Answer 1

您的解决方案中的所有项目是否都针对 .NET 4.0？
它是 .NET 4.0 Client Framework 还是完整的 shebang？
您是否在先决条件中部署了正确版本的框架？

我将把这个发送给 C/O 产品团队，看看他们是否有任何意见。