New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ASP.NET Core / EF7 / .NET Core Semantics #97

Closed
jiberan opened this Issue Feb 22, 2016 · 13 comments

Comments

Projects
None yet
7 participants
@jiberan

jiberan commented Feb 22, 2016

EntityDomainManager is expecting DbContext from EF6. There should be also version for Entity Framework Core.

@adrianhall

This comment has been minimized.

adrianhall commented Mar 25, 2016

Hi @jiberan - we do not support ASP.NET Core at this time. Feel free to file a UserVoice at http://feedback.azure.com - I'm sure others are waiting on it as well.

@DibranMulder

This comment has been minimized.

DibranMulder commented Aug 2, 2016

He @adrianhall do you have any plans for supporting ASP.NET Core? Since it has already been released for a month. I'm figuring out if I should be my mobile backend with ASP.net core or with the regular ASP.net framework. OfflineSync is a must have for me...

@adrianhall

This comment has been minimized.

adrianhall commented Aug 2, 2016

You should use the regular ASP.NET framework for right now.

This was referenced Nov 26, 2016

@pvbchak pvbchak added this to the .net core milestone Jan 11, 2017

@jraadt

This comment has been minimized.

jraadt commented Jan 27, 2017

It's been a few months and I see there's a .net core milestone now. Has this moved from backlog to active development? Just curious if there's an update.

@adrianhall

This comment has been minimized.

adrianhall commented Jan 27, 2017

We are still waiting for a couple of features within EF7 and a release of the OData provider before we can begin work. We've done some light investigation, but waiting for these libraries is holding us back.

@adrianhall adrianhall changed the title from EntityDomainManager and Entity Framework Core to Support ASP.NET Core / EF7 / .NET Core Semantics Feb 23, 2017

@adrianhall

This comment has been minimized.

adrianhall commented Feb 23, 2017

Check out my blog on https://shellmonger.com - I'm starting a series where I discuss running things in .NET Core, which will include EF7 and Azure Mobile Apps. This project will NOT be going to .NET Core - the differences are significant enough that we will be starting a new project to support .NET Core going forward. Look for this in the future - it isn't going to be quick.

@adrianhall adrianhall closed this Feb 23, 2017

@Ponant

This comment has been minimized.

Ponant commented May 5, 2017

Hi @adrianhall , I asked this question (compatibility between Azure Mobile Apps and .Net Core) and after your response we worked on the ASP.NET Core web app, hoping that the Azure Mobile App will get updated in the meanwhile to support .Net Core. Could you give us a rough indication of the timeline such that we know how to proceed? Are we talking about 3 months, 6 months, a year or more? Approximately.

@adrianhall

This comment has been minimized.

adrianhall commented May 5, 2017

I am no longer with Microsoft, so I can't answer this. Personally, I'd look for an alternate solution to this.

@chadiswar

This comment has been minimized.

chadiswar commented May 5, 2017

Adrian was this move based on a product shift in the Azure app service or was this a personal decision?

@Ponant

This comment has been minimized.

Ponant commented May 5, 2017

Hi @adrianhall , I am sorry to hear this as I know your contributions to Azure. Which alternate solution would you have in mind? It is not clear to us what altenatives we have, identity server? We need to keep our .Net Core app but be able to communicate with Azure from a mobile app (UWP and then Xamarin). cheers

@adrianhall

This comment has been minimized.

adrianhall commented May 5, 2017

AUthentication and configuration are already taken care of (I've done the work for handling the [Authorize] token and it is released on NuGet - check out my blog at https://shellmonger.com and my NuGet libraries). After that, just create a regular REST API and use that.

@Ponant

This comment has been minimized.

Ponant commented May 5, 2017

If that is what you mean, http://www.nuget.org/packages/AzureAppService/, it would be great to point to an explicit post in your blog where you use this library. The closest I got was this one, https://shellmonger.com/2017/03/02/azure-app-service-authentication-in-an-asp-net-core-application/, but it does not seem to use your lib.

@adrianhall

This comment has been minimized.

adrianhall commented May 5, 2017

Yep - that is the one. The code is the same - I just encapsulated the library code in an actual library.

tofutim pushed a commit to loqu8/azure-mobile-apps-net-server that referenced this issue Jan 9, 2018

Merge pull request Azure#97 from gb92/xamarinandroid
Adding name attribute to xamarin android login activity
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment