Looking for a JavaScript while deploying a C# application

[Jorriss]

I'm trying to test out deploying a C# application to Azure and running into this error:

ENOENT: no such file or directory, stat 'c:\\Code\LogLoader\LoadLogData\functions\run.js'

I'm pretty sure I'm missing something in my serverless.yml file

service: AFTKLogLoader

provider:
  name: azure
  location: West US

plugins:
  - serverless-azure-functions

package:
  exclude:
    - env.bat
    - .gitignore
    - package.json
    - .git/**
 
functions:
  LogLoader: 
     handler: functions/run.csx

Is there any documentation or examples that would assist creating a C# application in Azure?

[pragnagopa]

We did not add support for c# yet. We will track this issue as feature request.

[cmatskas]

+1 for adding support for C# and F# functions

[cmatskas]

@pragnagopa I would be keen to get this feature in. Is it more than just adding the necessary template files? Could we have a chat about this so that I can understand what's involved so that I can contribute to this? thanks

[joefiorini]

Since the question was never answered, asking again. I could not find an easy way to init & deploy function apps on macOS; I have serverless deploy working now, but the only reason I'm using azure is so I can write F#. @lostintangent @pragnagopa What is actually needed to start supporting other languages? Is it merely updating shared/utils.js to not automatically append .js to the handlerPath or is there something more to it?

[pragnagopa]

Generating functions.json from the yml file for the bindings and creating folder would be the same. We need to add functionality to handle .csx files.
@fiveisprime - Can you please follow up?

[joefiorini]

Would it be trivial to add functionality for handling fsx files at the same time? What about precompiled workflows? https://github.com/Azure/azure-webjobs-sdk-script/wiki/Precompiled-functions Given the proper details, I’m happy to implement it myself. What does “add functionality to handle .csx files” mean exactly?

…

On Jun 13, 2017, 1:08 PM -0400, Pragna Gopa ***@***.***>, wrote: Generating functions.json from the yml file for the bindings and creating folder would be the same. We need to add functionality to handle .csx files. @fiveisprime - Can you please follow up? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[pragnagopa]

I think adding support for Precompiled-functions should be straight forward . Plugin needs to be updated to:

• Figure out if the function is JavaScript or c#
• Add support in yml to parse for "scriptFile"
• Update code that generates function.json to include scriptFile element for c# functions
• Copy dll to the function folder

Plugin already takes care of generating the right folder structure and copying files to FunctionApp.

[joefiorini]

Thanks!

Figure out if the function is JavaScript or c#

Could we just look up the file matching the configured handler name and then check if it's extension is csx, js, or fsx?

Add support in yml to parse for "scriptFile"

So scriptFile would be a relative path to the dll file (ie. build/Debug/MyFunctions.dll)? Would this new key be sibling to functions.<function_name>.handler or under a vendor-specific key like x-azure-settings?

[pragnagopa]

There shouldn't be any difference in handling precompiled functions for C# and F#. Yes, please use handler property in yml for specifying "ScriptFile". This could be a relative or absolute path. Code here needs to be updated to handle both JavaScript and Pre-comipled assemblies.

For figuring out language, other providers are using 'runtime' element in yml file. As Azure functions supports writing functions in multiple languages, it might be worth it to add new 'language' element which can be specified for each function. This can default to JavaScript if not specified.

[taraspos]

scritFile was introduced in the PR #83, you could try again and see if it works with the latest version of the plugin.

[minusreality]

This is still an issue and I'm having a difficult time finding any examples of how to deploy a C# function to Azure using this plugin. I am able to successfully deploy using "func azure functionapp publish" entirely outside of Serverless Framework, but I'd like to use Serverless Framework if possible.

serverless deploy -v
Serverless: Load command config
Serverless: Load command config:credentials
Serverless: Load command create
Serverless: Load command install
Serverless: Load command package
Serverless: Load command deploy
Serverless: Load command deploy:function
Serverless: Load command deploy:list
Serverless: Load command deploy:list:functions
Serverless: Load command invoke
Serverless: Load command invoke:local
Serverless: Load command info
Serverless: Load command logs
Serverless: Load command metrics
Serverless: Load command print
Serverless: Load command remove
Serverless: Load command rollback
Serverless: Load command rollback:function
Serverless: Load command slstats
Serverless: Load command plugin
Serverless: Load command plugin
Serverless: Load command plugin:install
Serverless: Load command plugin
Serverless: Load command plugin:uninstall
Serverless: Load command plugin
Serverless: Load command plugin:list
Serverless: Load command plugin
Serverless: Load command plugin:search
Serverless: Load command config
Serverless: Load command config:credentials
Serverless: Invoke deploy
Serverless: Invoke package
Serverless: Building Azure Events Hooks
Serverless: Parsing Azure Functions Bindings.json...
Serverless: Building binding for function: hello event: httpTrigger
Serverless: Packaging service...
Serverless: Logging in to Azure
Serverless: Looking for deployed functions that are not part of the current deployment...
Serverless: Creating resource group: AgnosticHello-rg
Serverless: Creating function app: AgnosticHello
Serverless: Waiting for Kudu endpoint...
Serverless: Uploading function: hello
Error: ENOENT: no such file or directory, open ''

I have created a project that attempts to be an example of deploying a Serverless C# function to both AWS and Azure from the same project. It actually works, except I cannot use serverless framework for deployment due to this issue. I made a branch for this bug, and if you follow the README instructions it should allow you to reproduce the same issue:

https://github.com/minusreality/agnostic-serverless-hello-cs/tree/serverless-azure-functions-bug-45

[tbarlow12]

C# functions are on our roadmap. Closing in favor of #367