I have a SignalR enabled Web API server on Azure, and I have created a Windows Phone 8 client app that works perfectly well with the server on my WP8 Emulator.
After deploying to my Nokia Lumia 925 device, none of the components that demonstrate Server - Client push work.
Like, literally, nothing Signal R works on the app, but when I run it again on my Emulator everything works.
I just don't get what is going on.
I need help, please.
Thanks
UPDATE
The REST API and the SignalR powered streaming API are live on Azure.
Basically, I can make posts to the rest API, but then the Streaming API which is meant to broadcast that post to all connected clients including the originating client fails on the deployed device, but not on the emulator.
Could be proxy/connection related.
On the emulator you could be using a debug/emulated version of your Azure Service in which case the WP8 client app can see it fine. You may want to make sure the WCF Service has actually been deployed to Azure it is accessible over the web and its not actually pointing to locahost.
Then once your sure of all that just make sure your phone's browser can see the services end-points on azure and the client app should see it fine.
Maybe also try using Fiddler to see what network traffic is coming from your emulator and also the app once on-device. Also check you're not trying to hit "localhost" once deployed to your device. See here for how to use Fiddler with WP8 emulator and devices: http://www.spikie.be/blog/post/2013/01/04/Windows-Phone-8-and-Fiddler.aspx
Related
I am working in project which uses Bot Framework, and We are implementing DirectLine with websockets connection. For this, we are using Direct Line App Service extension. We are following these steps: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-channel-directline-extension-net-bot?view=azure-bot-service-4.0.
When We publish the project from VS2022 on an Azure Windows App Service, it works correctly, but when we publish it on Linux, the route that finishes with "/.bot" returns 404 not found response.
We don't find anything about this problem on internet.
Do we need to configure anything else for it works on Linux App Service?
Linux App Services do not currently support extensions of any kind, so the Direct Line Extension is not currently supported on a Linux App Service. You can run the bot and use standard Direct Line on Linux, but if you require the network isolation offered by the extension, you will need to use the Windows App Service.
Is it possible use have a web-browser control inside a UWP app that connects to a local web server?
I can have the app connect to a live service, but some users need to be able to get access to web pages while working off-line.
Ideally, I'd like to replicate the feature on a local service, but I can't find anything to support this sort of feature. My guess is, it breaks the sandbox rule for UWP apps, but I thought there may be somebody that has been able to make this happen.
We are trying to host the BOT on the Enterprise server IIS server which is an internet server visible to Microsoft and other outside public domains.
So, after hosting the BOT on the enterprise cloud server we would get an endpoint ex: https://myenterpriseserver.com/api/messages.
Can I use the above endpoint to register the bot in the microsoft's dev.botframework.com?
Please help, as we are planning for a large scale implementation of the BOT.
Thanks,
Mahesh
As long as the server has a SSL Certificate it should work assuming you deploy the bot correctly. Test it out first by using the Bot Emulator to see if you can send a receive messages from a computer in your system's network. Next try registering the bot on Microsoft's Bot Framework and seeing whether Microsoft's Bot Connector service can connect to the bot successfully.
Your system/intranet may block outside messages from Microsoft in which case you will have to change some settings, etc. with your firewall. This GitHub Issue follows an issue with white-listing Microsoft's Bot Connector service.
I'm trying to test the Microsoft Azure's Mobile Services. I've created a Mobile Service on the Azure portal and downloaded the "getting started" project with the Todo demo application.
I was able to deploy the service on the cloud and to run the app with the simulator but when a I try to host the service on my local IIS and run the mobile app, I've got the following exception on the client side:
System.ArgumentException: 'us-ascii' is not a supported encoding name.
Parameter name: name
at System.Globalization.EncodingTable.internalGetCodePageFromName(String name)
at System.Globalization.EncodingTable.GetCodePageFromName(String name)
at System.Text.Encoding.GetEncoding(String name)
at System.Net.Http.HttpContent.<>c__DisplayClass1.<ReadAsStringAsync>b__0(Task task)
My Windows's language is English and my keyboard's language is French. I tried to configure the encoding of the HTTP requests on both client side and service side but nothing worked.
Any help would be greatly appreciated :)
Thanks.
This is a side effect of now allowing your WP8.X Emulator (VM) to connect to your local Service that runs under IIS.
When you create a WCF web service in Visual Studio, by default the service is hosted in IIS Express and only accepts connections at localhost
The Windows Phone 8 Emulator, however, configures itself as a separate device on the network. As a result, an app running on the Windows Phone 8 Emulator can’t connect to the development computer as localhost.
Before you can connect successfully from the emulator to the local web service, you have to follow these steps
In short :
Go to %USERPROFILE%\Documents\IISExpress\config\
Open applicationhost.config
Add a new Binding with the IP of your WPEmulator VM
Restart VS as Admin
I have a two web application in Visual Studio 2012 running in the Windows Azure Compute Emulator (using IIS Web Service, not Express). Additionally I have a Windows 8 App in another Visual Studio instance which uses both azure web applications. This combination works fine on the same machine.
For presentation purposes I'd like to run the app on a Windows RT Tablet. Therefore I use the remote debugging tool to run the app on the tablet. Running the app is not the problem. But I didn't found a possibility to connect to the web applications from the tablet. The azure Emulator generates URLs like 127.0.0.X:81 but the tablet cannot resolve this address.
Is there a workaround to solve my problem? A way to run the azure application with the IP address of my dev machine? Or is it possible to create a kind of a proxy running on the dev machine which forwards requests from the tablet to the azure application?
I've seen a possible solution running fiddler as a reverse proxy. This does not work for me because fiddler seems to listen only on one port. But I need two.
Another possibility would be to configure the Azure Emulator endpoint.
Take a look at this SO answer for more information.