ClickOnce manifest problem #3606
sinanakyazici
started this conversation in
General
Replies: 1 comment
-
When targeting .Net Core 3.1/.Net 5 you should be using the https://www.nuget.org/packages/CefSharp.Wpf.NETCore/ package. Follow the instructions at #3284 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys, I'm trying simple demo .net core 3.1 application for clickonce like below.
I get an error " the manifest may not be valid or the file could not be opened." when I try to publish application.
I uninstalled CefSharp.WinForms package. I don't get any error when I publish application.
Why does CefSharp.WinForms cause an error for manifest ?
This error log:
`PLATFORM VERSION INFO
Windows : 10.0.19042.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.8.4270.0 built by: NET48REL1LAST_C
clr.dll : 4.8.4341.0 built by: NET48REL1LAST_C
dfdll.dll : 4.8.4270.0 built by: NET48REL1LAST_C
dfshim.dll : 10.0.19041.1 (WinBuild.160101.0800)
SOURCES
Deployment url : http://192.168.1.101/aw/WinFormsApp1.application
Server : Microsoft-IIS/10.0
Deployment Provider url : http://192.168.1.101/aw/WinFormsApp1.application
IDENTITIES
Deployment Identity : WinFormsApp1.application, Version=1.0.0.4, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=msil
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.1.101/aw/WinFormsApp1.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://192.168.1.101/aw/Application%20Files/WinFormsApp1_1_0_0_4/WinFormsApp1.dll.manifest: the manifest may not be valid or the file could not be opened.
+ Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x80070c89
Start line: 0
Start column: 0
Host file:
+ Master did not send an update notice for directory at the expected time. (Exception from HRESULT: 0x80070C89)
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.
OPERATION PROGRESS STATUS
* [6/6/2021 12:27:33 PM] : Activation of http://192.168.1.101/aw/WinFormsApp1.application has started.
* [6/6/2021 12:27:33 PM] : Processing of deployment manifest has successfully completed.
* [6/6/2021 12:27:33 PM] : Installation of the application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [6/6/2021 12:27:33 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://192.168.1.101/aw/Application%20Files/WinFormsApp1_1_0_0_4/WinFormsApp1.dll.manifest: 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.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
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)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x80070c89
Start line: 0
Start column: 0
Host file:
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
at System.Deployment.Application.Manifest.AssemblyManifest..ctor(FileStream fileStream)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Runtime.InteropServices.COMException
- Master did not send an update notice for directory at the expected time. (Exception from HRESULT: 0x80070C89)
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IsolationInterop.CreateCMSFromXml(Byte[] buffer, UInt32 bufferSize, IManifestParseErrorCallback Callback, Guid& riid)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
`
Beta Was this translation helpful? Give feedback.
All reactions