I need to upload a progressive web app appx file generated by pwabuilder.com to the MicroSoft partner Center. It must include in its list of capabilities
I could not see any way to add capabilities during the pwabuilder.com appx generation process. So I
renamed windows.appx to windows.zip
unzipped windows.zip
edited AppxManifest.xml and added in the location capability DeviceCapability Name="location"
zipped it up again
renamed it back to windows.appx
submitted it to the Microsoft partner center
Without adding the capability in the appx file upload fine but with the capability in I get
Package acceptance validation error: The package file format for windows.appx is invalid: Exception from HRESULT: 0x80510007. Update the package and try again.
How can I include the capability and get the package uploaded ?
The above error was a certificate signing error. The solution was to add the following to the web app manifest file
"mjs_capabilities": [
"location"
],
and submit as before using pwabuilder.com . Full details at
https://github.com/pwa-builder/PWABuilder-CLI/wiki/Accessing-the-Windows-10-Runtime
Related
We're using EvoPDF in an NET6 C# MVC application to convert HTML to PDF files for display and emailing as attachments.
Using EvoPdf.HtmlToPdf.NetCore in our development environment works fine.
If we publish from Visual Studio using Deployment Mode = Framework-dependent then EvoPdf works ok.
If we publish from Visual Studio using Deployment Mode = Self-contained and run EvoPdf we get an error
Could not create image object. Could not load type 'System.StubHelpers.InterfaceMarshaler' from assembly 'System.Private.Corelib, Version=6.0.0.0, Culture=neutral, ....
As we'd rather have a self-contained install on our Live servers this is a major pain !
Any suggestions gratefully received.
I have same issue, you can try uncheck Trim unused code option in publish setting.
you can use dnspy load this dll & search InterfaceMarshaler check whether it exists in published dll, maybe it exists in debug folder but not exists in publish folder.
System.Private.CoreLib.dll take 10.4MB size in dotnet 7.0 shared directory.
You can simply copy dll from shared directory to publish directory.
I have an application that I'm trying to publish to my website. The error I'm getting is that when done publishing, it says:
So it looks like it succeeded, but didn't.
My website is located at www.mywebsite.com.
In my build properties, under the publish tab, I click options->deployment, then set deployment webpage title to 'rdl', then I check automatically generate deployment webpage after every publish
I then go through the Publish Wizard:
Specify the location to publish this application: ftp://www.mywebsite.com/
Click next.
Check From a website: Specify the url: http://www.mywebsite.com/
Check Yes, this application will be available online or offline
The final page then states:
The application will be published to:
ftp://www.mywebsite.com/
Users will launch this application from:
http://www.mywebsite.com/
Click Finish
I am then left with the error described in the image above.
When I go to cPanel (my web host), I am able to see the Application Files folder which includes my application folder inside it.My .deploy and .application file are also located there along with any assets I had.
This Application Files folder is on the same level as the public_html folder if that matters.
Any help would be appreciated, I'm not exactly sure where I'm going wrong!
Everytime I upload a package on my QA server via Package Manager, it keeps loading it for a long time and then throws an error saying "package file parameter missing"
The error logs show absolutely no activity regarding the package.
This happens for both code packages (/apps/...) and content packages (/content/...)
Make sure your server has a tmp (linux) or temp (windows) folder accessible to the AEM process with full permission. This error occurs when the aem process cannot find the temp folder which it uses to temporarily store packages when they are being uploaded.
I downloaded todo.txt-touch-ios-master zip file from github.But when i open this applicaiton in xcode 4.4.DropboxApiKey.h file is not found.I got the erors like \
'<'command line'>':1:10: fatal error: 'DropboxApiKey.h' file not found
In file included from '<'built-in'>'
project folder path'<'command line'>':1: 'DropboxApiKey.h' file not found in project folder path /'<'command line'>'
How can i get that file.I added manually That file.But it's not working.Again same errors came.
I found a project on GitHub called todo.txt-touch-ios, so I assume that's what you're looking at. If so, I see a file there called sample-DropboxApiKey.h. My guess would be that you should copy or rename that file to DropboxApiKey.h and plug in your own app key and secret.
You can obtain your own app key and secret by creating an app at the Dropbox app console: https://www.dropbox.com/developers/apps. Create a "core API" app, as it appears that's what this code uses. I can't quickly tell from reading the code whether the app needs to have "app folder" or "full Dropbox" permission, so you might try one and then the other.
See also https://github.com/ginatrapani/todo.txt-touch-ios/issues/163, which seems to confirm my guess.
What I do: Publishing .Net 3.5 application via VS, or msbuild (whatever), and now I need to insert to the published application separate directory (Modules - not added as a reference to the project - our project architecture does not allow this). So I'm copying the folder to published location then runs mageUI.exe select the application manifest and then the problems starts. As I press the populate button it's adding also hidden directory? So I remove the directory, after I want to save the manifest file I get the
"Warning MSB3110: Assembly 'NAME.Shell.application.deploy' has mismatched identity 'NAME.Shell.application', expected file name: 'NAME.Shell.application.application'".
Did you have the same problems, according to http://smartclient.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=5060 it should be easy as 1-2-3 but it's not.
On the irony side, I am currently updating the SCSF documentation for ClickOnce deployment for .NET 4.0, and now I know exactly what the problem it.
First, you want to publish to a disk location, not directly to the webserver. So do that, and then copy the dll's you want to add to the deployment into the version folder with the application manifest (.manifest). Rename them yourself -- just add .deploy on the end.
Bring up MageUI and open the application manifest in that folder, then uncheck the box that says "add .deploy to the file names". Click "populate".
Then remove the deployment manifest from the list; it's called something like appname.application. You don't want it to be included in the manifest's list of files.
Now you can save and sign the application manifest. Then without exiting mageUI, open the deployment manifest that is in the root folder (NOT the one in the version folder). Click on "Application Reference", then click Select Manifest. Dig down to the application manifest in the version folder that you just signed and select it. Then just save and sign the deployment manifest. It puts a relative path in there, so if you modify the .application file in the version folder, it won't work right when deployed.
Now take that .application file from the root folder and copy it into the version folder (replacing the one that's there) so you have the right copy for that version in case you need it later.
Now copy the whole shebang out to the webserver. it should work.
I think you are saying you need to add a folder of stuff to your ClickOnce deployment? What exactly are you adding? You say modules -- are they going to be compiled in, or is it something else?
If you want to add files to the deployment you have already created, you need to use MageUI to edit the application manifest, which is called something like appname.exe.manifest. (The appname.application is actually called the deployment manifest, which is confusing but true.) After adding the files, you will need to re-sign the deployment manifest as well (assuming you signed it in the first place).
It would be easier just to add what you want included to your project and re-publish. Depending on what it is, you can set the build action to 'content' (jpegs, html, etc) or 'none' (dll's) and then set "copy to output directory" to true, and it will include it in your deployment.
I'm not sure exactly what you are including. Give me more info, and I can provide more specific help.
RobinDotNet