We Keep Coding

How to add window service exe (as external exe) in clickonce

i have a solution that having the desktop ui wpf project and a window service. I need to create clickonce installer. I have successfully created the installer for wpf application. For window service i just added the reference of project into wpf project. Including the window service exe in application files and then publish the application. I got following error message while installation of clickonce setup
PLATFORM VERSION INFO Windows : 10.0.18363.0 (Win32NT) Common
Language Runtime : 4.0.30319.42000 System.Deployment.dll :
4.8.3752.0 built by: NET48REL1 clr.dll : 4.8.4121.0 built by: NET48REL1LAST_C dfdll.dll : 4.8.3752.0 built by: NET48REL1
dfshim.dll : 10.0.18362.1 (WinBuild.160101.0800)
SOURCES Deployment url :
http://192.168.0.162:8189/Netsolace.Edible.Partner.Desktop.application
Server : Microsoft-IIS/10.0
X-Powered-By : ASP.NET Deployment Provider url : http://192.168.0.162:8189/Netsolace.Edible.Partner.Desktop.application
Application url :
http://192.168.0.162:8189/Application%20Files/Netsolace.Edible.Partner.Desktop_1_0_0_53/Netsolace.Edible.Partner.Desktop.exe.manifest
Server : Microsoft-IIS/10.0
X-Powered-By : ASP.NET
IDENTITIES Deployment Identity :
Netsolace.Edible.Partner.Desktop.application, Version=1.0.0.53,
Culture=neutral, PublicKeyToken=cd5358bf47526dee,
processorArchitecture=msil Application Identity :
Netsolace.Edible.Partner.Desktop.exe, Version=1.0.0.53,
Culture=neutral, PublicKeyToken=cd5358bf47526dee,
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. * Activation of
http://192.168.0.162:8189/Netsolace.Edible.Partner.Desktop.application
resulted in exception. Following failure messages were detected: +
Reference in the manifest does not match the identity of the
downloaded assembly Netsolace.Edible.Partner.WindowServices.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY No transaction error was
detected.
WARNINGS There were no warnings during this operation.
OPERATION PROGRESS STATUS * [10/21/2020 12:47:03 PM] : Activation of
http://192.168.0.162:8189/Netsolace.Edible.Partner.Desktop.application
has started. * [10/21/2020 12:47:03 PM] : Processing of deployment
manifest has successfully completed. * [10/21/2020 12:47:03 PM] :
Installation of the application has started. * [10/21/2020 12:47:04
PM] : Processing of application manifest has successfully completed.
[10/21/2020 12:47:06 PM] : Found compatible runtime version
4.0.30319. * [10/21/2020 12:47:06 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS Following errors were detected during this operation.
[10/21/2020 12:47:08 PM]
System.Deployment.Application.InvalidDeploymentException
(RefDefValidation)
Reference in the manifest does not match the identity of the downloaded assembly Netsolace.Edible.Partner.WindowServices.exe.
Source: System.Deployment
Stack trace: 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.OnModified() at
System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem
next) at
System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Download(SubscriptionState
subState, X509Certificate2 clientCertificate) 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, Uri& deploymentUri) at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri
activationUri, Boolean isShortcut, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings,
String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown --- at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri
activationUri, Boolean isShortcut, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings,
String& errorPageUrl) at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)
COMPONENT STORE TRANSACTION DETAILS No transaction information is
available.

You can add that exe in your current solution using
Add->Add Existing Files (All files).
If that exe still not produce in ClickOnce setup, then check properties of that added
exe by pressing F4 key .
Hope this answer helpful.

LightSwitch Desktop Application Installation failing: "Strong name signature not valid for this assembly vslshost.exe"

I've created a LighSwitch desktop application in Visual Studio 2013 which installs perfectly fine on my development machine but fails during installation on my client's machine with the following error message:
Strong name signature not valid for this assembly vslshost.exe
I found a similar issue that was also raised on the MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/28736d83-db94-4d0b-adb9-2ff2e6d0ba95/installation-failing-strong-name-signature-not-valid-for-this-assembly-vslshostexe?forum=lightswitch
One person replied stating that other people have previously given solutions to this error but neither I nor the original poster could find these solutions.
I've followed the How to: Deploy a Two-tier LightSwitch Application guide found here:
http://msdn.microsoft.com/en-us/library/ff852056.aspx
However, the problem persists for my client but not for me.
Can anyone help with this?
Here are some details from the error log:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.1022
System.Deployment.dll : 4.0.30319.245 (RTMGDR.030319-2400)
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)
IDENTITIES
Deployment Identity : [APPLICATION], Version=1.0.7.0, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=x86
Application Identity : [APPLICATION_EXE], Version=1.0.7.0, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=x86, type=win32
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of [APPLICATION] resulted in exception. Following failure messages were detected:
+ Strong name signature not valid for this assembly vslshost.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
* The manifest for this application does not have a signature. Signature validation will be ignored.
* The manifest for this application does not have a signature. Signature validation will be ignored.
* The file named default.htm does not have a hash specified in the manifest. Hash validation will be ignored.
* The file named web.config does not have a hash specified in the manifest. Hash validation will be ignored.
OPERATION PROGRESS STATUS
* [25/02/2014 8:11:42 AM] : Activation of [APPLICATION] has started.
* [25/02/2014 8:11:42 AM] : Processing of deployment manifest has successfully completed.
* [25/02/2014 8:11:42 AM] : Installation of the application has started.
* [25/02/2014 8:11:42 AM] : Processing of application manifest has successfully completed.
* [25/02/2014 8:11:45 AM] : Found compatible runtime version 4.0.30319.
* [25/02/2014 8:11:45 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [25/02/2014 8:11:46 AM] System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Strong name signature not valid for this assembly vslshost.exe.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyStrongNameAssembly(String filePath, AssemblyManifest assemblyManifest)
at System.Deployment.Application.ComponentVerifier.StrongNameAssemblyComponent.Verify()
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
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)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Any help with this would be greatly appreciated. Please let me know if further information would be useful in diagnosing the issue.

cannot install program onto other computers

i have published a "preview" version of my winforms application, and i have put it out to 2 different computers. When I run the ClickOnce, it says cannot be installed, contact vendor, and the Setup file doesnt even run, it just shows the loading mouse for a tenth of a second and thats it, nothing in task manager, nothing. Can anyone help?
Here is the clickonce log:
PLATFORM VERSION INFO Windows : 6.0.6002.131072 (Win32NT) Common Language Runtime : 2.0.50727.4016 System.Deployment.dll :
2.0.50727.4016 (NetFxQFE.050727-4000) mscorwks.dll : 2.0.50727.4016 (NetFxQFE.050727-4000) dfdll.dll : 2.0.50727.4016 (NetFxQFE.050727-4000) dfshim.dll : 2.0.50727.4016
(NetFxQFE.050727-4000)
SOURCES Deployment url :
file:///C:/Users/testMachine/Desktop/Event%20Control.application
ERROR SUMMARY Below is a summary of the errors, details of these
errors are listed later in the log. * Activation of
C:\Users\testMachine\Desktop\Event Control.application resulted in
exception. Following failure messages were detected: + Exception
reading manifest from
file:///C:/Users/testMachine/Desktop/Event%20Control.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 * [11/10/2013 21:40:23] : Activation of
C:\Users\testMachine\Desktop\Event Control.application has started.
ERROR DETAILS Following errors were detected during this operation.
* [11/10/2013 21:40:23]
System.Deployment.Application.InvalidDeploymentException
(ManifestParse)
- Exception reading manifest from file:///C:/Users/testMachine/Desktop/Event%20Control.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.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.

First, in the Signing tab for the project properties, be sure to sign your deployment, even if you just use a test certificate created by Visual Studio. Second, in the Security tab for the project properties, be sure you have ClickOnce security settings enabled. Also, are you editing any of the files after publishing them?
Also be sure your installation URL points to the same location as the deployment, whether it's local disk or a file share or a webserver.

"Manifest XML signature is not valid"

OS: Windows 7 64 bit using Visual Studio Pro 2012 with .NET 4.5 installed.
I used the Publish option within Visual Studios and ensured that I had clicked the Sign the clickOnce manifest and Sign the Assembly. It will still not run on another computer and says I do not have a valid XML signature. I have pasted the error message below.
I have also read: How to move a ClickOnce deployment package, Do I have to sign my ClickOnce manifest?. VS2012 .NET 4.0 Clickonce VSTO CryptographicException: SignatureDescription could not be created for the signature algorithm supplied and several others.
I need to be able to deploy my program on .NET 4.0 at the minimum and I do not have access to another version of Visual Studios. Thanks in Advance!
complete Error Below:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 2.0.50727.3603
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3603 (GDR.050727-3600)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : file:///C:/Documents%20and%20Settings/Administrator/Desktop/EatonWizard.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\Administrator\Desktop\EatonWizard.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from file:///C:/Documents%20and%20Settings/Administrator/Desktop/EatonWizard.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
* [10/10/2012 2:05:02 PM] : Activation of C:\Documents and Settings\Administrator\Desktop\EatonWizard.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [10/10/2012 2:05:02 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from file:///C:/Documents%20and%20Settings/Administrator/Desktop/EatonWizard.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.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.

I had the same problem today. This is how I solved:
What caused the problem:
We created a clickonce project using vs2012 and framework 4.5.
Then we changed the target framework to 4.0 (client asked to).
The problem is: Framework 4.5 uses SHA-256 algorithm for the signature, and 4.0 uses SHA-1. When we changed the target framework to 4.0 and vs2012 didn't changed the algorithm.
Solution: Change the algorithm manually, generating a new certificate.
Go to Project properties -> signing
You will see the algorithm that is being used in 'Signature Algorithm'. You can create a new test certificate and then you will notice that it changes to 'sha1RSA'

Note, I would have added this as a comment, but due to silly Reputation rules, I can only add an answer!
Beware new code signing certificates
I had this problem recently because our Code Signing certificate needed renewal. So, being blind to the fact that Microsoft haven't patch the XP version of Framework 4 to work with SHA2 certificates during ClickOnce deployment, I told all my clickonce projects to use the new code signing certificate.
As I also do code-based updates of the app rather than just let Microsoft handle it, so that it's a more seamless experience to the end user without them required to press buttons and in the style of my app.
However, I hit a bug where my program didn't report the manifest error, instead it just hung (my bad!). In order to get an update our after working until 3am to discover this problem, I had to create a temporary certificate issued by Visual Studio. The problem with that? Code updates are not seamless any more because microsoft put a stupid dialog up as the publisher is unknown!
So my biggest concern is that yes, OK, XP is not supposedly supported from Monday but that shouldn't mean the Framework 4 shouldn't accept the new certificates if that's what they are pushing to everyone. Microsoft are even actively involved in that push!
The only working answer is as above, you MUST use Visual Studio to create an untrusted temporary certicate, which is rediculous!!! (I still have hope that maybe I didn't find the correct way to use the new certicate)

Installation problems of C# deployment

I have a program I deployed using ClickOnce deployment and then installed on my machine. I tried running it, and it gave me the following error:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 2.0.50727.3053
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)
SOURCES
Deployment url : file:///C:/../MyProg.appref-ms%7C
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\..\MyProg.appref-ms| resulted in exception. Following failure messages were detected:
+ The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/30/09 2:45:10 PM] : Activation of C:\..\MyProg.appref-ms| has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/30/09 2:45:16 PM] System.Runtime.InteropServices.COMException
- The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IStore.GetAssemblyInformation(UInt32 Flags, IDefinitionIdentity DefinitionIdentity, Guid& riid)
at System.Deployment.Internal.Isolation.Store.GetAssemblyManifest(UInt32 Flags, IDefinitionIdentity DefinitionIdentity)
at System.Deployment.Application.ComponentStore.GetAssemblyManifest(DefinitionIdentity asmId)
at System.Deployment.Application.ComponentStore.GetSubscriptionStateInternal(DefinitionIdentity subId)
at System.Deployment.Application.SubscriptionStore.GetSubscriptionStateInternal(SubscriptionState subState)
at System.Deployment.Application.SubscriptionState.Validate()
at System.Deployment.Application.SubscriptionState.get_IsInstalled()
at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, String& errorPageUrl, TempFile& deployFile)
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)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
I cannot uninstall the program, but I can't see why (a dialog pops up for a second and disappears before I can read it), and I can't reinstall the application until I have uninstalled the old version.
What might the problem is, and what I can do about it?
Previous versions were deployed using Visual Studio 2008. This version was deployed using Visual C# Express Edition. There is a dependency for the MySQL Connection package. I have not customized any of the settings when publishing, beyond the location of the directory and the version number (non-duplicate version number).

Your application store may be messed up. You can try deleting this key (it will all remove any currently installed Click-Once applications):
HKEY_CURRENT_USER\Software\Classes\SOFTWARE\Microsoft\Windows\CurrentVersion\Deployment\SideBySide
As a note, if your application 'works' besides that error or on other machines, then this is likely your issue.