I have developed a chromecast app for our streaming website. in our cast console we had registered multiple apps and all were discoverable , but after publishing one app , other apps are undetectable by sender app. Do we need to create another developer account for managing the other apps or we can handle them from the same dev console. We want to use that for staging server
We registered the a new app in the dev console after publishing an exsisting app.We were expecting the registered ubpublised app will be discoverable by the registered device but unfortunalty sender app are unable to detect the new unpublished app
Related
I would like to understand what Azure does while creating a Web App Bot in Portal.
An Azure Bot Service Bot deployed to an Azure App Service Web App...
After creating a bot with Azure Bot Service i got the following ressources:
What's the difference or the connection between the resources (Web App Bot and App Service)?
The code should be located in Web App Bot right? Here the magic happens, development, channels, etc.
The user is interacting with the App Service throw an HTTP call. What happens if App Service receives the call?
And why I could configure CD on the App Service instead of Web App Bot?
From my understanding, the Web App Bot is the "locale" Bot I'm publishing to App Service to make him available?
Can anyone help me out to get a clear understanding?
Let us break down the different components involved.
The Web Bot (which is a web application) needs a web site to be deployed to. That is the App Service. That web site needs a web server to run on. That is the App Service Plan.
The Web Bot is the main part which you configure. The other components are infrastructure components and you don't need to worry about them much.
Your bot is actually an API, which will be hosted on App Service. So in case your bot receives many requests, You'll scale App Service to handle that.
Web App Bot is where you enable and configure the channels your bot will work with (e.g. Direct Line for voice)
I have two App services which I deployed to the same resource groups within the same region. The icon associated with them are different while both of them identify as App Service. Why are the icons different and what do they mean? Any cost implications?
Azure App Services come in different flavors including Web Apps, API Apps, Mobile Apps, and technically Function Apps (Azure Functions). The first App Service in the above image is a Mobile App and the second is a standard Web App. They are all technically web apps but the Mobile and API apps offer some subtly different default configurations and features that target the specific needs of supporting mobile app back ends or hosting APIs for example.
You should ensure you're deploying to the desired app service type before continuing. Generally speaking you would know if you needed to deploy to a Mobile App so if this is by accident I would recreate the resource as a standard Web App App Service. More details available at https://learn.microsoft.com/en-us/azure/app-service/app-service-web-overview
Best way to get notifications to Angular Client from an Azure hosted Web API
I'm creating an app where users can interact on articles. The back-end is asp.net core 2 web api. Front end is nodejs Angular universal app. I've decided to host on azure.
I need to get user notifications from server to the client. So if an user wrote a document and another user liked it, the notification will be sent to the user that wrote it, if the user is running the site.
I know I can achieve this using SignalR or Socket.io, but I was looking for something that azure provides.
Is there anything in azure that I can use, such as Event Hub, Event Grid or NServiceBus where there's already a javascript client that works on the browser, listening on Events?
hi best way notification is azure web job with azure web hook
using web job you can get notification to any devices
for more details please see
enter link description here
We got caught by Microsoft's abandonment of Silverlight and focus on UWP. This has ended up with us having to develop two dually focused apps (UWP and Silverlight), which has left us with two apps that cannot be bundled/packed together. We have therefore decided to have of the apps as a companion app.
Both apps use authentication, at present time it is with Microsoft authentication. The services used for authentication is of the type Azure App Service - Mobile. The services besides authentication also provides interfaces to a notification hub, blob storage and SQL storage.
The question is therefore is it possible to have one App Service - Mobile (not mobileservice), and authenticate two different apps using the same service?
Additionally can the same Notification Hub be used to send notifications towards different apps?
Or is it needed that we create two different services for each application to facilitate the use of authentication and push messages. Then we can link the same database to the two App Service - Mobile ? But this would leave the issue of the notification hubs not having the same registrations ?
I dont think you can have more than one apps connected to one Azure mobile app. You can connect same app on different platforms but not multiple applications for same platform as Mobile app is designed to be an individual app back end.
Check this feedback request.
https://feedback.azure.com/forums/218849-notification-hubs/suggestions/3821272-push-notifications-for-multiple-apps
As answered by product group, the idea behind Mobile App is to be the individual backend. For that, Mobile Apps dashboard should have not one field for the PackageId/..., but two or more to be the backend for a different apps. Every connection between app and external service like a authentication provider or push notification platform is "personalized" - by IDs and password or certificates, or many ways.
I can imagine the scenario when someone would need to connect one backend to different apps, but the Azure Mobile App idea is different. And, as App Service is a service, i think that in the current situation what you want to do is impossible.
an Azure Mobile App consists of the client app and a backend in Azure. There's no stopping you reusing the same backend for more than one app.
I just want to know from which device logged in our website and where from (Location)
I'm currently working on azure mobile service API
Per my understanding, Azure mobile service APIs provided functions to approach resources on Azure but collect devices information.
If you want to detect device on website, I think How to detect mobile device and get user agent info send and save that information to database on server, only once maybe the similar thread on SO.
And to get the location of mobile devices on Web apps, I think How web apps ask location of mobile device will be the similar thread.
If you are creating a mobile application, and a Azure Mobile Apps with node.js as a backend for your application. We can create a custom API, and hit the API to send device information and location when your user login the app. For different platform, there are built-in functions in their SDKs to collect devices information and location.