Click here to Skip to main content
15,877,168 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I have created a vb.net 2013 application, I have published it and installed it on my work pc (windows 7) and my laptop (also windows 7) and they both work fine. I tried installing it on the pc this application is to go on which is windows xp, I got an error with the following details:

PLATFORM VERSION INFO
Windows             : 5.1.2600.196608 (Win32NT)
Common Language Runtime     : 4.0.30319.1022
System.Deployment.dll       : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll             : 4.0.30319.1022 (RTMGDR.030319-1000)
dfdll.dll           : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll          : 4.0.31106.0 (Main.031106-0000)

SOURCES
Deployment url          : file:///D:/Visitors.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of D:\Visitors.application resulted in exception. Following failure messages were detected:
    + Exception reading manifest from file:///D:/Visitors.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
* [14/08/2014 13:43:54] : Activation of D:\Visitors.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [14/08/2014 13:44:00] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
    - Exception reading manifest from file:///D:/Visitors.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.


This is the first time I have published an application so I don't know why this is happening, I can only assume that it has something to do with windows xp. I would appreciate any help with this problem.

Update:
The .NET framework is targeted at 4.0, and the target cpu was 'Any CPU' and I changed it to x86. The xp pc in question has .NET4.0, XP SP3 and is 32-bit but this still hasn't solved my problem. Also, I am using sql server 2008r2 express in this application if that makes any difference.
The old error is not coming up and the new one says:
'SqlExpress2008R2 is not a valid Win32 application.'

Update 2:

As well as having to do what I said in my first update, I also had to change the signing from 'Sign the ClickOnce manifests' to 'Sign the assembly' and my application is now working on windows xp.
Posted
Updated 15-Aug-14 0:32am
v5
Comments
Richard Deeming 14-Aug-14 9:49am    
Windows XP doesn't support .NET 4.5 - you'll need to change your project's target framework to 4.0 before it will work on XP.
Member 10804519 14-Aug-14 10:25am    
@Richard Deeming I have set prerequisites to .NET 4.0, do I have to change it to 4.0 somewhere else aswell?
Richard Deeming 14-Aug-14 10:28am    
You've set the prerequisites on the deployment project, but you'll need to change the target framework of the project you're deploying as well. It should be somewhere prominent in the project property pages.
Member 10804519 14-Aug-14 10:30am    
Changed target framework to .NET 4.0, it should work now I hope.

1 solution

Check the application properties. 5.1.2600.196608 (Win32NT) is a 32 bit version of XP, so if you have built your app for 64 bit then it will fail to load even if it is built for the right version of .NET

Try rebuilding it for "x86" under the "Platform Target" dropdown of the "Buld" tab of the Properties page and see if the problem goes away.
 
Share this answer
 
Comments
Member 10804519 14-Aug-14 11:14am    
Thanks @OriginalGriff, I'll try that and let you know how I get on.
Member 10804519 14-Aug-14 12:28pm    
The .NET framework is targeted at 4.0, and the target cpu was 'Any CPU' and I changed it to x86. The xp pc in question has .NET4.0, XP SP3 and is 32-bit but this still hasn't solved my problem. Any other ideas?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900