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

Support for Azure Functions development #779

Open
filipw opened this issue Feb 21, 2017 · 1 comment
Open

Support for Azure Functions development #779

filipw opened this issue Feb 21, 2017 · 1 comment
Assignees
Labels

Comments

@filipw
Copy link
Member

filipw commented Feb 21, 2017

Based on dotnet/vscode-csharp#1241

This can be spun off from the existing CSX support with some extra features, specific to Azure Functions:

  • predefined set of implicit namespaces
  • predefined set of DLLs available as if they were GACed (even though they aren't)
  • support for project.json for external references (this is already there, however for .NET Core only, but functions are net46 only)

The biggest challenge would be to decide when a CSX is a "standard" one and when it is an Azure Function one.
At the very worst, if we can't infer it, we could have a mode switch in omnisharp.json.

@filipw filipw added the csx label Feb 21, 2017
@filipw
Copy link
Member Author

filipw commented Mar 1, 2017

Long story short, the key would be to incorporate https://github.com/Azure/azure-webjobs-sdk-script/blob/master/src/WebJobs.Script/Description/DotNet/FunctionMetadataResolver.cs and most other things should just fall in place.

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

No branches or pull requests

1 participant