I am having a hard time understand the current set of options and components currently available (January 2019) to us with respect to Azure Functions. Part of my issue could also be what is seemingly confusing terminology and/or versioning and what seems like very stale documentation (many of the pages listed here (https://docs.microsoft.com/en-us/azure/app-service/overview-diagnostics) are still dated from 2017.).
As I understand it
.NET Full Framework.NET Standard / Core. This was in beta (??), preview (??) last year and went GA around September / October 2018?Azure Webjobs SDK、Azure Functions Host、WebJobs Script、Azure Core Tools、とAzure Functions Runtime。Ultimately, I am looking to run Azure Functions on-premise and need to support both v1 and v2. While the vast majority of functions we are going to create will target the newer v2, we have two or three .NET libraries that have yet to be ported away from Full Framework and since they are 3rd party, we cannot control the time frame.)
Ideally we would like to provide a on-premise Portal for developers to upload the functions from Visual Studio or even create them via the browser.
Even better would be to containerize the functions and run them in an on-premise Azure Service Fabric. (I realize this is advanced and probably beyond the scope of this posting.)
Conclude your questions to 3 points
Runtime difference(The first three items)
Your understanding is totally right that V1 targeting Full NetFramework and V2 on .NET Core, which is announced to be GA since 9/24/2018. And yes, all new features will be only targeted at V2.
The relationship between those terms(The 5th item).
Azure Webjobs SDK is a framework that simplifies the task of writing background processing code that runs in Azure. In .NET functions, it(along with Webjobs extensions) is referenced by Microsoft.NET.Sdk.Functions.
WebJobs.Script = Azure Functions host = Azure Functions Runtime, where our functions work. It's built upon Azure WebJobs SDK and enables a light-weight scripting model for it, the scripting library does the work necessary to plug our function scripts into the Azure WebJobs SDK runtime.
Azure Functions Core Tools(CLI) is a command line tool integrated with Azure Functions Runtime. Our local development(e.g. running, debugging) depends on this tool.
Azure Functions Runtime preview 2(The 4th item)
It offers a UI similar to Azure Function portal and consumes very old Function runtime from obsolete docker hub image. As you have found in the thread, no plan to update, not sure whether it will be abandoned or not.
So far we are not able to get a working on-premises Portal and could only turn to CLI or container for local running. Note that there's No image for v1 function. Not familiar with Azure Service Fabric so no more suggestions.
この記事はインターネットから収集されたものであり、転載の際にはソースを示してください。
侵害の場合は、連絡してください[email protected]
コメントを追加