System.Speech on Windows Azure Error - c#

I am trying to call some methods from System.Speech via a WCF Service hosted on Windows Azure. When i try this locally on the development fabric, it is working perfectly fine. I can consume the methods from this Speech API via WCF service in my client.
But when I up this service in real cloud on Azure, i get the following exception error message on the client:
No voice installed on the system or none available with the current security setting.
I have tried to set Copy Local property to True of System.Speech dlls but it is still throwing this exception to me.
Is there any workaround for this?

It looks like Windows Azure does not have actual voice engines installed. Unless it is possible to easily deploy them via the XCopy (which I doubt), then at the moment there is no way to use Speech on Windows Azure.

Related

Is it possible to make HTTP calls to applications outside of Azure from a web API running in Azure?

Is it possible to make HTTP calls to applications outside of Azure from a web API running in Azure?
I'm trying to connect a ASP.NET web API in Azure to a wpf application that runs on a PC at my company. Both the applications request data from each other using HTTP calls with JSON. This works fine locally because i can use localhost but
when running the web API in Azure the web API can't reach the wpf application
I have looked into Azure Point-to-Site and Site-to-Site connections but most examples that i found show connection with a VM in Azure and nothing about web API's.
Thanks in advance!
I still don't get your scenario even after reading all the comments, however here's a shot in the dark.
First of all, no, there are no restrictions as to what destination you may call from Azure, yes that includes the dark web, although not necessarily a recommended destination for both traffic and tourism alike.
For the second part, if what you're calling is behind a firewall and your API runs in Azure App Service, take a look at Hybrid Connections, it's built as a solution to that exact scenario, no IPsec or firewall rules are in play. The connectivity from on-prem will be outbound.

Connecting Azure Mobile Services to UWP

I have created a Mobile service in Azure, and connected an SQL database in it.
I installed the required Nuget Package Microsoft.Azure.Mobile.Client, and i tried Microsoft.WindowsAzure.MobileServices , and inserted this code in my App.xaml.cs:
public static MobileServiceClient MobileService = new MobileServiceClient("https://sqlbackend.azurewebsites.net");
The Problem is: When i come to connect an azure mobile service to the project, they say it is not supported.
Is there any way to connect my project to an azure mobile service?
What kind of project the client is?
If it's Azure Mobile Service or Azure Mobile App itself, no need to add a connected service, just right-click the project,select Publish,import the web app publish settings file and publish to Azure.
If it's Windows Phone WebView App or others supported by tooling gesture, the configure button will be enabled and the code in App.xaml.cs should be:
public static MobileServiceClient MobileService = new MobileServiceClient
("https://sqlbackend.azurewebsites.net", "XXXX-APPLICATION-KEY-XXXXX");
The second parameter is application key which is generated here:
PS: The code above and adding connected service(Azure Mobile Service) reach the same result and no need to use both at the same time.
You are using the old Azure Mobile Services client.
Links for you:
HOWTO:
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-dotnet-how-to-use-client-library/
SDK Docs:
https://msdn.microsoft.com/en-us/library/azure/mt419521(v=azure.10).aspx
When you convert to using Microsoft.WindowsAzure.MobileServices, it will inject the right header and you will not get the Unsupported message.
After reviewing your question again, you need to match up the type in the server with the type in the client. If you have created an Azure Mobile Service, then your client should be Microsoft.Azure.Mobile.Client. If you have created an Azure App Service Mobile App, then your client should be Microsoft.WindowsAzure.Mobile.Client - the links I provided were for Azure Mobile Apps (not Services in the client). I recommend Azure Mobile Apps (which can be considered the latest generation of such). Tutorials are available on azure.com

Consuming WCF service using NetTcpBinding in a UWP app

I am currently in the process of migrating all of our applications over to the Windows 10 UWP platform. We were coming from the Windows 8.1 platform and we were using a WCF service to send both data as well as files to and from a server running our service.
This worked great in Windows 8.1 since it fully supported the uploading of files to a WCF service that had a nettcpbinding. However, according to numerous posts on here as well as the MSDN forums, nettcpbinding is not currently supported on UWP. Whenever I try to run our app and upload a file to our server I get PlatformNotSupportedException when it tries to upload.
The issue here is that while I could roll my own socket classes to upload this file, I find it hard to believe that Microsoft would've released UWP without basic support for nettcpbindings. On top of this it appears that the .NET library that is included in UWP apps does not have support for native FTP so I cannot do that either.
Has anyone had any experience in getting nettcpbindings to work with UWP? If I try to circumvent my proxy classes that I have made manually with "Add Service Reference" it ends up generating the upload method with an incorrect signature. The signature is supposed to be UploadFileAsync(RemoteFileInfo info) but is turned into UploadFileInfo(byte[] info when using "Add Service Reference".
Any ideas?

OWIN OAuth invalid grant error in Windows Service vs. Console App

I have a Web API using OWIN for OAuth, running in Katana/TopShelf.
When I install the Web API as a Windows Service, everything responds correctly, except a POST via resource owner flow (grant_type=password, username=x, password=y) returns 400 Bad Request (invalid_grant).
The exact same Web API, running in the same folder, except this time running in Command Line mode, using the exact same request from the same remote address, is successful.
The only delta is whether I run the .exe file directly in Console mode or I install and start it as a Windows Service.
I have to think this is a conflict at the network level but Windows Service is just acting as a thin host around the same HttpListener based host.
Whenever we see an issue like this with Topshelf it is almost always permission related. There's some resource that you have rights to but the service user doesn't. Are there resources on disk the service accesses or something similar?

Service Bus for Windows Server - The API Version is not Supported

I'm considering developing an app to run on-premise and off-premise and was hoping to use the Service Bus to communicate between services.
I have 2 problems:
My corporate network is blocking access to my Azure endpoint so I can't use my genuine Azure Service Bus.
I can't use WindowsAzure.ServiceBus version 2.2.7.0 against my Windows Server Service bus.
I get the following whenever I try using the Windows Server Service Bus (e.g. NamespaceManager.QueueExists):
System.ArgumentException : The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of 2012-03,2012-08,2013-04,2013-07...
I suspect I need to add api-version to NamespaceManager.CreateFromConnectionString but I just can't seem to find how :(
My current connection string is:
Endpoint=sb://[my machine]/ServiceBusDefaultNamespace;StsEndpoint=https://[my machine]:9355/ServiceBusDefaultNamespace;RuntimePort=9354;ManagementPort=9355
No matter where I stuff api-version=2013-07 it doesn't like it.
MTIA
Andy
Ended up here because I was getting this issue using Service Bus Explorer with Service Bus 1.1 installed locally on my machine.
The issue was due to using the latest version of Service Bus Explorer (currently 2.4.1.1).
The issue was fixed by using Service Bus Explorer 2.1 which is also included in the Service Bus Explorer download.
Using the 2.1.3.0 version the issue went away.
Get it here. http://code.msdn.microsoft.com/windowsazure/Service-Bus-Explorer-f2abca5a
Edited:
Above link is broken.Use this instead.
https://code.msdn.microsoft.com/windowsapps/Service-Bus-Explorer-f2abca5a
You probably ran into some other issues others were having like in the link below,
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/c23a7c1f-742d-4d7f-ad4f-3bf149964762/service-bus-for-windows-server-the-api-version-is-not-supported?forum=servbus
however if you notice there is very little help except in the following post
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/3aa6c2b8-65ac-4f8b-a36c-674698bb2f41/setting-development-environment-for-service-bus-11-on-windows-7-and-vs-2013?forum=servbus
The quick answer reading between the lines is not to use the Microsoft.ServiceBus v2.2.0.0 that comes with Windows Azure SDK 2.2. Instead, grab the nuget package "Service Bus 1.1 for Windows Server" and everything should work fine using SB 1.1 for Windows Server.
Install Service bus 1.0 CU on the server where Workflow Manager is installed. Refer to: http://support.microsoft.com/kb/2799752 and download it from: https://www.microsoft.com/en-us/download/details.aspx?id=36794
For anyone still having this issue, as the above posts say the resolution to this problem came from a conflict between Microsoft.ServiceBus assemblies. My project had a reference to the ServiceBus DLL that comes with the Azure SDK version 2.7. I replaced the reference with the DLL installed with Service Bus 1.1 and that corrected the issue.
Make sure your assemblies you are referencing correspond with the right version.

Categories