Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Mobile service with a .NET backend produces error in service explorer #64

Closed
avranju opened this issue Dec 23, 2014 · 3 comments
Closed

Comments

@avranju
Copy link
Contributor

avranju commented Dec 23, 2014

If you have a mobile service which uses a .NET backend in your subscription then the service explorer produces the following error:

err

@avranju avranju added the Pri1 label Dec 23, 2014
@BeatriceOltean
Copy link
Contributor

We should disable this for .Net, It is unsupported. No child item should be added in the tree

@babumuralidharan
Copy link

This is working as expected. Currently the respective mobile service is shown in service explorer but nothing underneath. Also when you right click the respective mobile service we could see the warning in the service log. Still we can use this mobile service when we add an azure service activity but not sure if user can do any customization on the template generated code since we do not support .net backend. @avranju thoughts??

@avranju
Copy link
Contributor Author

avranju commented Feb 13, 2015

We don't support a .NET backend for the mobile service in service explorer but I'd imagine that Android apps should be able to make use of a .NET backend based mobile service.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants