本地运行的Azure移动服务（点网后端）引发未授权错误

Question

I've created a fresh new Dot Net backend based Azure Mobile service, downloaded it, published the service part to azure with publish settings. This all works fine.

(this is the default to do app that Azure Mobile service generates, no changes made it to it.)

Now for development & debugging purpose I need to connect with my local service. Following is what I've done

1. Updated "applicationhost.config" IIS express file to have a new binding type

where 192.168.2.6 is my local internal IP

2. Run VS 2013 in Admin mode.
3. Set both project as startup project from solution

4. Updated following code in App.Xaml.cs

   public static MobileServiceClient MobileService = new MobileServiceClient( "http:// 192.168.2.6:59984/" );

5. Run

6. Browser opens to show the service running & WP8 emulator starts loading the app.

This is what happens I can see the service up & live on localhost:59984, I can also see in IIS Express toolbar icon that http:// 192.168.2.6:59984 is also running the local service just fine. Click open it & it shows the default "Service Up & Running" page

The WP8 emulator starts, Application Loads & I get a "The request could not be completed. (unauthorized)" error.

Please check the image below

I've also run a ntash command to allow IIS express for remote connections. as mentioned in This Blog

can someone please help? I've been struggling with this for over 2 days now & what seems like a very simple thing, is driving me nuts now.

Thanks Supreet Tare

Answer 1

我需要的只是Visual Studio 2013 Update 2，一切正常。

Answer 2

Take a look at this article.

You need to specify the application key of the service in the Web.config file:

<add key="MS_ApplicationKey" value="Overriden by portal settings" />

If you run the service within Visual Studio, you don't need these values, and every request will pass. When you deploy the service on Azure, these values are overriden with the correct values. But, if you deploy the Mobile Service on your local IIS, you need to manually set them, and be sure that they match the values you enter in the client.

After changing the MS_ApplicationKey value in the web.config and also updating my phone client app to specify the application key in the MobileServiceClient constructor, I was able to hit the service from the phone!