Created several app packages for a windows store app some time ago in order to show a client the progression of the application. Now I would like to load a much older version of the application onto the device, however PowerShell says that the certificate has expired and thus the application does not install. Is there a way to regen the certificate without recreating the entire app package and/or get around an expired certificate and just manually install the app on the device?
Related
I am developing an invoice app with Angular + NodeJs + MySql.
The thing is, the app is planned to be used by one employee in his office. No need for online servers.
It is not problematic to deploy the app online, but the internet is unstable in the zone (Latinamerican problem. You may lose connection for hours, and even voltage variations that may shut down the PC).
So the app must be self sufficient to always work offline.
So my questions are:
Can I simply deploy the app offline? Like in local. If that is the case, I would need for everything to be initialized automatically when the user opens the app (server open, database connected...).
If I have no way but to deploy the app online, should I use Firebase? Also, what happen if the internet service shut downs for hours? Is there a way for the database to be available offline and sync when the internet gets back?
You could build the app as an Electron App, then its becomes a locally run program. https://www.electronjs.org/
You can host it anywhere, but turn the app in to a PWA, which means it will work locally in the browser after a successful visit (gets installed with a service worker in browser) For the database it self, you can store data in the browser but some are limited to 5mb of data in the localstorage / sessionStorage / indexdb. Firebase does have some locally cached data. But if the browser is closed it can be lost.
If it needs to run locally i would go the electron route. Its slightly harder to do but it fills out your usecase better.
You can use both ways if you want to be sync like situation you have to hold data if your internet is not working in local storage or indexed db.
and it is fine you can deploy locally also or make one dedicated server which is always on.so any body in same network can use that angular app easily.
Just take care of backup plan when you system corrupt you should have proper backup of database for such scenario.
I have an RPi2 iot-core app which has run fine for months on the previous iot-core os release. I access it regularly via the iot-hub and it writes to Azure blobs ... until the automatic update last week to version 10.0.14393.67 at which time my UWP-headless-app, although still running (I see this in my reference version via the local device portal app), no longer communicates with iot-hub or azure.
Any ideas what going on and what can I do without having to start from scratch?
I know what is metro app (just did some research) my question is where metro app runs. By my understanding :
Detktop app: running on your local machine with .net framework, and present data to user, you can launch/close it.
Web app: Publishing on IIS server, running from server render html to client, user can send request and get result.
Now, Metro app: is it just distributed on windows store, user can download/install it and run from local as same as desktop? or run from store, render something to user like web? or maybe some new working styles, can user close it?
Metro Style App was a working name before Microsoft settled on Windows Store Apps.
Windows Store Apps just like desktop apps run on local machine, but are often architected in more modern ways where the app would often connect to web services or push notifications that run in a data center. The UI though usually runs on local machine even if it is written in html/js with winjs.
The biggest difference is distribution - web apps run on the server so you only need to navigate to them in your browser to run the latest version. Desktop apps need to be installed - either with xcopy-style install, Windows installer or perhaps the ClickOnce technology. Store apps are distributed through the store which makes them easier to install and update than desktop apps as well as monetize, but are sandboxed (have limited access to local machine resources) for security.
The Windows Store App Cert kit fails to start.
Normally the flow is:
Start App Cert Kit
Choose Windows Store Application
Choose App
Choose Certs to Run
Run Certs
Save results
Currently, it fails just before 'Choose App'.
I get this result:
I have tried uninstalling and reinstalling, installed all updates, running appcert.exe reset. All to no avail.
I think it may have to do with the same issue I get with the Windows Store app. I have 38 languages installed (our app supports all of them) and the Windows Store app doesn't like it. I've had to escalate with customer support repeatedly for this, and have not had it resolved properly. I wonder if the same issue applies here.
So I was unable to start the UI, but I was still able to run the appcert by manually calling it on the command line as described here. It worked fine. One thing to note is that between each attempt, make sure to run appcert.exe reset.
I need help on code signing of my windows store app to deploy to target audience. When i try to change default certificate provided by visual studio at the time of Windows Store 8.1 project creation to my company certificate. Visual studio is throwing error
"The Manifest designer could not import the certificate.The certificate you selected is not valid for signing because it is either expired or has another issue. "
Is there any way for code signing in windows store 8.1 i see most of the blog targeted for windows 8. I need any info targetting in windows 8.1
My end goal is to deploy my windows store (LOB) without any developer license.
The certificate publisher name needs to match the publisher name defined in your app manifest. This means you will likely need to make a new certificate. You can, however, install the new certificate on your devices, including using something like a group policy (if they're all on the same domain).
We were getting that same error when trying to sign our packages with our existing code-signing certs. We resolved the issue by modifying our code-signing certificate template to include the "Basic Constraints Extension".
After changing the template and issuing a new certificate, we were able to sign the windows app package with the new certificate, and install the app on domain computers.
Here is the walkthrough that put us on the right path:
Side Loading Deployment of Windows Store Apps in Enterprises – Step by Step
We didn't exactly follow these steps... all we did was modify our template (as he does) and then requested a new certificate from the old certsrv asp page like we've been doing for years.