1. Zuhause
  2. Frage und Antwort
  3. ClickOnce-Manifest

ClickOnce-Manifest

2010-05-20 14 views
5

Wir implementieren derzeit eine WPF 4-Anwendung über ClickOnce und es gibt ein Szenario, wenn die Installation fehlschlägt.ClickOnce-Manifest

Wenn der Benutzer .NET 4.0 Vollinstallation nicht hat und versucht, unsere Anwendung zu installieren, installiert das Framework ordnungsgemäß, aber die Anwendung kann nicht installiert werden. Wenn wir die Installation erneut ausführen, wird die Anwendung ordnungsgemäß installiert.

Hier ist eine Kopie des Protokolls:

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.

Ich bin verwirrt. Was könnte das sein?

Ich habe festgestellt, dass dfsvc.exe, die direkt nach der Installation ausgeführt wird im Ordner ".NET 2" befindet. Wenn ich das Installationsprogramm erneut ausführe, befindet sich dfsvc.exe im Ordner ".NET 4".

Ich habe auf Microsoft-Support zu sprechen, und wir haben, dass aufgrund der Tatsache, dass eine frühere Version von .NET 4 (Beta in unserem Fall) installiert wurde, und un-installiert es hinter mehrere Dateien links . Wenn das Installationsprogramm für .NET ausgeführt wurde, mussten einige Dateien umbenannt und anschließend neu gestartet werden. Da die Dateien jedoch von der vorherigen Version übernommen wurden, dachte das Installationsprogramm, dass die Umbenennung bereits stattgefunden hatte und forderte keinen Neustart an.

Quelle

2010-05-20 TWith2Sugars

Antwort

2

Erzielen alle Projekte in Ihrer Lösung .NET 4.0?
Ist es .NET 4.0 Client Framework oder der vollständige Shebang?
Implementieren Sie die richtige Version des Frameworks in den Voraussetzungen?

Ich werde diese an das C/O-Produktteam senden und sehen, ob sie irgendwelche Eingaben haben.

Quelle

2010-05-20 17:48:27 RobinDotNet

+0

Ich habe mit der C/O Produktleitung bei Microsoft gesprochen. Er möchte wissen, ob der Endbenutzer den Computer neu gestartet hat, nachdem .NET 4.0 installiert wurde? .NET 4.0 erfordert einen Neustart. – RobinDotNet

+0

Es ist das vollständige Framework für alle Projekte, das Click-On-Pre-Reqs-Ziel auch. Die Maschine hat keinen Neustart durchgeführt, aber es gab keine Option/Warnung, um zu sagen, dass sie benötigt wird. – TWith2Sugars

+0

Ich denke, meine Frage wäre dies: Wurde der Benutzer aufgefordert, neu zu starten, und entschied sich nicht zu? Jeder Rechner, auf dem ich .NET 4.0 installiert habe, hat einen Neustart angefordert. Wenn dies nicht der Fall ist, deutet dies auf ein Problem mit der Installation von .NET 4.0 hin. Auf welchem ​​Betriebssystem läuft die Maschine? – RobinDotNet

1

Microsoft behauptet jetzt, dies ist ein known issue, aber sie haben keine Zeit, um es in Visual Studio 2010 zu beheben, und dass es "in zukünftigen Versionen berücksichtigt werden."

Quelle

2011-01-11 20:06:48 kwill

0

Ein kleiner Prozentsatz unserer Kunden hat diese Nachricht in den Protokollen erhalten, wenn sich die Anwendung selbst aktualisiert oder neu installiert wurde, obwohl es nicht damit zu tun hatte, ob .NET 4 bereits installiert war oder nicht.

Es stellt sich heraus, dass es Panda Antivirus ist es irgendwie versauen.

Durch vorübergehende Deaktivierung wurde die ClickOnce-Installation abgeschlossen. Das hat für uns funktioniert.

Quelle

2016-03-18 10:58:32

 Verwandte Themen

  • Keine verwandten Themen^_^