I am in the digital signage business for small businesses. We have created an app that runs digital signage through the raspberry pi using Windows iot. Everything works great but what if one day we wanted to make changes to the app. Is there a way to update the app without having to manually do it on site. I would prefer having the app do it programmically through regular checks but I'm not finding anything. Wish there was a App Store mechanism for the pi to update apps. Any ideas on this?
All devices running Windows IoT Core run a small webserver instance on port 8080. You can reach this by visiting http://DEVICEIPADDRESS:8080
The default credentials are:
U:Administrator
P:p#ssw0rd
Within the portal, you can provision and deploy apps remotely using the App Manager by selecting "Apps" along the left-hand pane.
If you setup firewall rules to allow outbound traffic to the Windows IoT Core device you may be able to deploy updates remotely.
Currently there is no app store for windows iot but it is possible to create your own. You could implement this functionality using a push or pull system with Azure.
Push - azure pushes updates to the devices.
Pull - the device asks azure for updates
Get started with Event Hubs (tutorial describing how to implement Event Hubs in Azure)
Another option could be to write your own REST API on a server (Azure or your own server).
Related
I'm new to Federation Services and I'm trying to understand how ADFS works as a whole and I've started to get down into the details. I followed along with creating an app using OIDC to authenticate a user, however, within the tutorial, they specified using a "Server Application" when setting up an Application Group. This ended up not working for me so I tried setting up a "Native Application" application group for kicks and was able to successfully login.
The thing that threw me off is, I ended up hosting ADFS on a server outside of the domain in which I had my application running, so I'm confused as to how that is "native" in terms of ADFS.
I went looking for this answer within microsoft's documentation but I didn't find the information very clear.
Native Application:
"Sometimes called a public client, this is intended to be a client app that runs on a pc or device and with which the user interacts."
Server Application:
"A web application that runs on a server and is generally accessible to users via a browser. Because it is capable of maintaining its own client 'secret' or credential, it is sometimes called a confidential client."
This may seem simple to some, but I'm trying to really get a grip on what would be used when. To me it sounds like a native application is used when you're running the application natively on a pc in which the user is also using the same pc, and the server application is run remotely in which the user would not be using the same machine. Is it really that simple or am I misunderstanding?
A native application (in Microsoft speak) is something that is not browser based e.g. mobile. The code runs client side. It may use JavaScript in which case the secret key is publicly accessible. (The secret key is one of the OAuth parameters). You use ADAL / MSAL to access it.
A server application runs server side e.g a web API. The secret key is not publicly accessible. You use OWIN to access it.
These terms have no relevance to where ADFS is actually installed. Native applications typically are not domain joined.
I made a Web Program which runs perfect on my localhost.
Now I want to bring it in the App Store and Google Playstore.
I hope someone of you can give me a tip which Plattform I should use as a Server.
T thought about azure or firebase.
But by firebase i have to Change my whole code because of tht nosql and it is not really possbile to make dynmaic pages.
on azure I only can bring it on the Marketplace.
does anyone know other pltfforms?
Ionic / Cordova / Phongap / Appcelerator are all names to look up for building a hybrid app and distributing to app stores.
Amazon EC2 or RDS can host a database for you which the app can connect to, I'm sure there are many others.
While working with Windows Phone Push Notifications, I got myself stuck in the part of creating the "cloud web service" to receive the negotiated URL and retrieve updates to the mobile device.Is it possible to create this Web Service without using Windows Azure services (I don't want to pay anything, I just want to push with my services to my apps)? And how can I create this Cloud Web Service.
I haven't worked extensively with Windows Phone 8.1. Check this webpage for Windows Phone 8 -
https://msdn.microsoft.com/en-us/library/windows/apps/hh202970%28v=vs.105%29.aspx
You will get a URL for each device you want to get notification on through the app you create. Taking help from the above link, you can create a local server (Cloud Web Service) for testing push notifications for your test devices.
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.
What I want
I want to allow in app SSO between the Live Connect SDK and a single Mobile Services instance that I'll use as the backend for 2 applications, WP8 & W8.1. I want to do this without affecting existing users of the WP8 app that is already in the Windows Phone Store. Both apps will use the Live SDK for OneDrive access.
Existing Situation
I have a Windows Phone 8 application that uses Azure Mobile Services and the Live Connect SDK and I have set up SSO by
Registering the app in the Live Connect Developer Center
Setting the redirect URL in the Developer Center to the Mobile Services URL (used in the Live Connect authentication token)
Copying the Client ID into my app and passing it to the Live Connect SDK methods when I log in
Retrieving the Live Connect authentication token after login and passing it to the Mobile services login
Issues
This is fine but now I want to start building a companion Windows 8.1 app that uses the same Mobile Services instance and SSO but I'm running into a difficulty as below:
The Live Connect Developer Center app associated with the Windows 8.1 app needs to have the Package SID and the only way I can find to do this is to use the 'associate my app with the Windows Store' tool within Visual Studio. This creates a new app in the Live Connect Developer Center with the Windows 8.1 Package SID. I can't find any way to add this Package SID to my existing Live Connect app (i.e. the one used for the WP8 app).
I believe I need to use a single, shared Live Connect Developer Center app, and associated Client ID, for both my WP8 and W8.1 apps as the authentication token from Live Connect (documentation here) seems to include the 'user identifier - uid' that is 'An identifier for the user, which is unique to the app'. To me this also implies that if I change the client ID (i.e. effectively a new app from Live Connect's point of view) then it will appear to mobile services as if a new user is signing in and all their old data will no longer be accessible to them.
I have researched other people doing SSO across both platforms and they seem to be using a single app in the Live Connect Developer Center but in all cases that I have seen so far they use the Windows 8.1 app, because this has the Package SID, and set it to 'Mobile or desktop client app'. I have started from the other direction with the phone app first and I can't find any information about this. I'm also trying to avoid testing this all out in a live app in case it does cause issues.
I have posted in both the Mobile Services and Live Connect forums about these issues but without a reply. (I can only provide 2 links, check my profile in the Mobile Services forum for my other post).
My Question
How can I add Azure Mobile Services SSO to my new Window 8.1 app without breaking my existing WP8 app?
Thanks.
It looks like this question may have already been covered here:
Live Connect Authentication Token for use on Azure Mobile Services (REST)
Hope that helps!
This question has been answered by Matthew Henderson in the Azure Mobile Services forum
The simplified version is you need to use one Live Connect app in the Developer Center (i.e. the same Client ID used by both the W8.1 & WP8 apps)
To do this you either need to either:
a) Start with the Windows 8.1 app which will register the SID with the Live Connect app (this is the documented and easiest path) and then re-use this Client ID in the Windows Phone 8 app
OR
b) If you already have a Windows Phone 8 app as I did then you can change the automatically created SID association in the Live Connect Developer Center to allow the Windows 8.1 app to use the existing Windows Phone 8 Client ID. This is a less well documented feature.