Opensourced .NET Core and Google App Engine

[Neil Rao]

With .NET Core being opensourced along with cross-platform runtimes for Linux, Windows, and Mac (and all the source code on GitHub), I think it'd be absolutely amazing to see .NET support for App Engine. It would be a smart move for Google for a few reasons:

1. There are a lot of people using .NET.

2. .NET Core is released for under the MIT License (see here).

3. Some competitors support .NET out-of-the-box.

Personally, we rely on the .NET stack, and thus we're forced to use Compute Engine over App Engine. I'd love to see support for the new .NET on Google App Engine. What do you all think?

[PK]

I would not expect Google to do this but you or the .NET community could do it.

Read this on the GAE direction regarding multiple platform support: https://www.linkedin.com/pulse/20141118192324-332875-program-the-cloud-in-any-language

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3e2a5c95-96c9-4ccd-99ad-caf0fd80c758%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

PK

p...@gae123.com

[Nick (Cloud Platform Support)]

I'll echo what PK has said - Custom Runtimes (part of Managed VMs) is how you can already do this, today. It's based on Docker, and I'm sure you can find .NET images out there. 

I'd recommend you look into this solution, as it appears to be the future of cloud application deployment, rather than waiting for us to implement a custom .NET version of GAE. 

At any rate, such a possibility can be discussed here with no problem, but the place to actually make a post like yours would be the Public Issue Tracker for App Engine, where feature requests should be directed. Keeping in mind what I've said about Custom Runtimes and Managed VMs, you may choose to just skip on that, but feel free if you want to wait rather than get going today ;)

[Neil Rao]

That's cool. Is there a client library for the App Engine Search service? I can't find any, so I thought I'd write one, but I couldn't find any publicly accessible interfaces for it (REST etc).

[Nick (Cloud Platform Support)]

Hi Neil,

The App Engine Search API service is accessible via the "API" of the libraries provided to the App Engine runtime in the given language. External access to the Search service for an app should be done through sending requests to handlers on your app (even an Endpoints API) which can access the Search API. Therefore, writing a "client library" for a custom runtime would involve writing a "wrapper" or "middle-ware" application in Java, Python, or Go which could access the Search API.

I hope this helps you move forward with your development, and specifically in reference to custom runtimes, I'm sure development will proceed with making these services accessible via a REST API (don't quote me, though), rather than simply being embedded in the runtime for the main supported languages of traditional GAE.

If you'd like, there is a public issue tracker for App Engine, and I encourage you to create a feature request asking for a REST API for Search API (and any other App Engine services which don't expose a REST API).

Sincerely,

Nick

[Neil Rao]

Hi Nick,

Thanks, I'll experiment with the Endpoints API. I created a new feature request here (#12008): https://code.google.com/p/googleappengine/issues/detail?id=12008

Best,

Neil