manifiesto de ClickOnce

Actualmente estamos implementando una aplicación WPF 4 a través del ClickOnce y hay un escenario en el que falla la instalación.manifiesto de ClickOnce

Si el usuario no tiene .NET 4.0 Instalación completa e intenta instalar nuestra aplicación, la infraestructura se instala bien, pero la aplicación no se instala. Si volvemos a ejecutar la instalación, la aplicación se instala correctamente.

Aquí está una copia del registro:

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.

estoy desconcertado. ¿Qué podría ser esto?

Me he dado cuenta de que dfsvc.exe que se ejecuta inmediatamente después de la instalación se encuentra en la carpeta .NET 2. Cuando vuelvo a ejecutar el instalador, el dfsvc.exe se encuentra en la carpeta .NET 4.

He estado hablando con el apoyo de Microsoft y hemos encontrado que, debido al hecho de que una versión anterior de .NET 4 (beta en nuestro caso) se ha instalado y desinstalado dejó detrás de varios archivos . Cuando se ejecutaba el instalador para .NET, era necesario cambiar el nombre de algunos archivos y luego reiniciar, pero como los archivos habían quedado de la versión anterior, el instalador pensó que el cambio de nombre ya había tenido lugar y no solicitó un reinicio.

Fuente

2010-05-20 TWith2Sugars

¿Realiza todos los proyectos de su solución .NET 4.0?
¿Es .NET 4.0 Client Framework o el shebang completo?
¿Está implementando la versión correcta del marco en los requisitos previos?

Voy a enviar este al equipo de producto C/O y ver si tienen alguna entrada.

Fuente

2010-05-20 17:48:27 RobinDotNet

He hablado con el cliente potencial de C/O en Microsoft. ¿Le gustaría saber si el usuario final reinició la máquina después de instalar .NET 4.0? .NET 4.0 requiere un reinicio. – RobinDotNet

Es el marco completo para todos los proyectos, el clic una vez pre-requisitos también se dirige a él. La máquina no se reinició, pero no había ninguna opción/advertencia para decir que necesitaba una. – TWith2Sugars

Supongo que mi pregunta sería esta: ¿se le solicitó al usuario reiniciar y eligió no? Cada máquina en la que instalé .NET 4.0 ha solicitado un reinicio. Si esta máquina no lo hiciera, eso indicaría un problema con la instalación de .NET 4.0. ¿Qué sistema operativo está ejecutando la máquina? – RobinDotNet

Microsoft ahora afirma que es known issue, pero que no tienen tiempo para arreglarlo en Visual Studio 2010, y que será "considerado en versiones futuras".

Fuente

2011-01-11 20:06:48 kwill

Un pequeño porcentaje de nuestros clientes recibió este mensaje en los registros cuando la aplicación se actualizó o recién se instaló, aunque no tenía que ver si .NET 4 ya estaba instalado o no.

Resulta que Panda Antivirus lo estropeó de alguna manera.

Al deshabilitarlo temporalmente, se completa la instalación de ClickOnce. Esto funcionó para nosotros.

Fuente

2016-03-18 10:58:32

Respuesta

Cuestiones relacionadas