2016-07-28 1 views
0

Excuses pour mon manque de connaissance car je n'ai pas beaucoup d'expérience.Projet Visual Basic 2015 pour que VB.NET fonctionne sous XP

J'ai créé une application VB.NET en utilisant Visual Basic 2015 mais lorsque j'ai essayé d'exécuter l'application sur XP Professional Version 2002 SP3, j'ai reçu le message d'erreur suivant.

J'ai pour la vie de moi ne sais pas comment résoudre ce problème. Le framework .net dans lequel l'application a été créée était 4.5.2.

L'application fonctionne parfaitement sur Windows 7 et Windows 10.

Cependant, les problèmes ne sont que sur XP

PLATFORM VERSION INFO 
Windows    : 5.1.2600.196608 (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   : file:///C:/Documents%20and%20Settings/rwuser/Desktop/Disk%20Cleanup%20Toolkit/drive_cleanup.application 

ERROR SUMMARY 
    Below is a summary of the errors, details of these errors are listed later in the log. 
    * Activation of C:\Documents and Settings\rwuser\Desktop\Disk Cleanup Toolkit\drive_cleanup.application resulted in exception. Following failure messages were detected: 
     + Exception reading manifest from file:///C:/Documents%20and%20Settings/rwuser/Desktop/Disk%20Cleanup%20Toolkit/drive_cleanup.application: the manifest may not be valid or the file could not be opened. 
     + Manifest XML signature is not valid. 
     + SignatureDescription could not be created for the signature algorithm supplied. 

COMPONENT STORE TRANSACTION FAILURE SUMMARY 
    No transaction error was detected. 

WARNINGS 
    There were no warnings during this operation. 

OPERATION PROGRESS STATUS 
    * [28/07/2016 09:56:20] : Activation of C:\Documents and Settings\rwuser\Desktop\Disk Cleanup Toolkit\drive_cleanup.application has started. 

ERROR DETAILS 
    Following errors were detected during this operation. 
    * [28/07/2016 09:56:21] System.Deployment.Application.InvalidDeploymentException (ManifestParse) 
     - Exception reading manifest from file:///C:/Documents%20and%20Settings/rwuser/Desktop/Disk%20Cleanup%20Toolkit/drive_cleanup.application: the manifest may not be valid or the file could not be opened. 
     - Source: System.Deployment 
     - Stack trace: 
      at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri) 
      at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation) 
      at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options) 
      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.InvalidDeploymentException (SignatureValidation) 
     - Manifest XML signature is not valid. 
     - Source: System.Deployment 
     - Stack trace: 
      at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s) 
      at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri) 
     --- Inner Exception --- 
     System.Security.Cryptography.CryptographicException 
     - SignatureDescription could not be created for the signature algorithm supplied. 
     - Source: System.Security 
     - Stack trace: 
      at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key) 
      at System.Security.Cryptography.Xml.SignedXml.CheckSignature(AsymmetricAlgorithm key) 
      at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey) 
      at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags) 
      at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s) 

COMPONENT STORE TRANSACTION DETAILS 
    No transaction information is available. 
+0

Windows XP est maintenant obsolète. Mieux vaut ne pas y penser. –

+0

Je sais mais la compagnie pour laquelle je travaille utilise encore XP !! lol. –

Répondre

0

XP prend en charge que le .NET Framework jusqu'à version 4.0. Si vous voulez l'exécuter sous XP, vous devrez changer le framework cible en 4 et recompiler le projet.

https://blogs.msdn.microsoft.com/dotnet/p/dotnet45xp/

+0

Je l'ai fait, mais après avoir beaucoup joué, ça n'a pas résolu le problème. Au lieu de cela sur mon script j'utilisais une requête WMI qui en fait ne fonctionnait pas bien avec XP .. donc WIM a changé pour system managementSearch et ça a fonctionné. –