Skip to content
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

Add c# .net core support #40

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

Marak
Copy link
Collaborator

@Marak Marak commented Aug 30, 2017

@janaka

This looks awesome! I've opened a PR to begin to review the changes for .net support.

I've been planning on doing a new release soon, so let me know if there was anything else you wanted to add or change.

@janaka
Copy link

janaka commented Aug 30, 2017

Awesome thanks.

I'd like to add some user documentation around how to create .NET Core services as a minimum.

Since I've realised that requiring the service to be a full console app project may be is unnecessary and somewhat un-FaaS like. This could be improved to only require a *.cs containing a class, templating the rest out. However, I need to think through how a user would add dependencies would work without direct access to the csproj file.

TODO

  • Check if C# .NET Core is supporting all required/expected functionality
  • Regression test to make sure nothing broke during adding .NET Core support
  • Refactor language specific logic that's scattered around into the plugin architecture (general improvement)
  • check performance - noticed some lag spitting out responses on the page in the hello world example.

The first two are probably sensible to tackle. Without the last one, it may need to go out with a beta label.

Let me know your thoughts.

@Marak
Copy link
Collaborator Author

Marak commented Aug 30, 2017

That all makes sense. I've been working on a few changes to some internals in another branch, but I don't think they will affect anything I've seen in this PR.

I don't do much work with dotnet, but I'd like to see this added. Not sure what qualifies as a dotnet console app, but I'd like to see this supported for http server applications.

Please make sure to try and encapsulate the dotnet logic as much as possible. I see we've added originalCodeFilePath. Not sure if that's something dotnet specific or that we should add to the API.

Please let me know if have any questions. I'm okay with Beta support to start. Thank you again for your contributions.

@janaka
Copy link

janaka commented Sep 1, 2017 via email

@Marak Marak mentioned this pull request Jan 3, 2018
@janaka
Copy link

janaka commented Feb 18, 2018

Hi, I'm sorry I did not get to this as promised. Obviously wasn't able to make time as I was away.

I'll have to ramp up on it again, hopefully far less time consuming for me than last time.

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

Successfully merging this pull request may close these issues.

None yet

2 participants