Was trying to create a new Azure Durable Function in Visual Studio 2017, but couldnt find the "Durable Functions Orchestration" listed in the below popup:
My visual studio is up to date, and not sure what I am missing!!
Ok, Found the problem. It seems like we need to select "Azure Functions v2 (.NET Core)" as the framework when creating the Project.
Note: After the project is created, do a build/rebuild of the project before trying to add a new function. For some reason, when I tried to add new Item, it still wasnt listed until I built the project
After the project is built successfully, you should now be able to see "Durable Functions Orchestration"
Related
I have a netcoreapp3.1 project with few functions.
I made changes to one function and deployed using VS 2022 but when I test in Azure, I can clearly see it is using the older code.
I tried removing then adding the function from the project.
Restarting the function app in azure and other refresh methods.
Will I only be able to get the new code if I delete and recreate the function app?
Is there another way to refresh the running code?
Once you have published your function to a FunctionApp throughout VisualStudio 2022 or VisualStudio Code, you can deploy updates to that function app. E.g. if you have added a new HttpTrigger, you can publish all the code including the added HttpTrigger from Visual Studio itself.
Visual Studio 2022, just a black Azure Function App for testing purposes:
Doubleclick on "Connected Services"
Then in the left pane, click "Publish"
Visual Studio Code (Azure Tools plugin):
I have an instance of visual studio 2017 in which azure functions are developing, strangely i stopped seeing, publish to azure option in the publish targets window and also in create new profile window.
If i open any of my other azure functions project in vs 2017, the window is seen correctly.
What could be different only for this case?
(Copying comment into an actual answer for the community to see)
well ,strangely my function app was missing functions sdk!! hence i was not seeing right publish outputs. after i installed Microsoft.Net.Sdk.Functions it all worked
I don't see the option to create an Azure function class library template in new projects under Visual Studio Mac. If I created one manually - what files do I need to include and what framework target should I use for the library? .net core or .net standard or something custom?
Alternatively - if I use a CSX script file instead, how would I debug that on a mac?
Azure Functions support for Visual Studio for Mac is available in the alpha channel, so you need to switch to that in order to use this functionality.
The tooling there is similar to what is available for Visual Studio 2015, supporting CSX based projects (as opposed to pre-compiled, class library projects) and giving you a local run/debug experience.
In Visual Studio Mac 7.2 this feature was moved into an extension. Just open the extension manager - search for "functions" and you can install that feature again.
I am using Visual Studio 2017 preview(2) to create Azure Function. The template generated for it is very different from what I get in Visual Studio 2015.
The Visual Studio 2017 template create a .cs file for function, and template structure looks like below :
All functions are created as individual .cs file and there are no run.csx, project.json or function.json files, due to which I am not able to specify function specific dependencies and settings
If we see the earlier template (see the image below) with Visual Studio 2015, it well represent the folders and files available on Azure Portal. It has functions in individual folder with all .json and .csx file. This folder structure helps in segregating files related to a particular function (which is not the case with VS 2017 template)
In VS 2017, I want to specify function specific dependencies and binding settings by adding project.json and function.json. Please let me know about the way to achieve this?
This is intended. Azure Functions team changed the way you develop and deploy Function Apps in Visual Studio 2017. Now, it's basically a compiled class library, with functions being static methods with proper attributes.
You should not be editing function.json manually anymore; instead use WebJob SDK attributes. Packages management is done the normal .NET way via NuGet packages.
The "old way" still works from within Azure portal for quick prototyping and experiments, but Visual Studio won't support it anymore.
I have developed an Azure Functions project in Visual Studio 2015 (a project with a .funproj file extension). Now I want to migrate it to Visual Studio 2017 but when I try, VS does not load the project.
Why is the migration failing and how can I complete it manually?
Azure Functions tooling for Visual Studio 2017 is still work in progress. They are expected to be announced during upcoming Build event.
Watch this github issue for status.
UPDATE: The Preview of Visual Studio 2017 Tools for Azure Functions are now available for download. The blog post explains the tools, requirements, and has a link to the download. Note that it only works in VS 15.3 Preview, not in earlier versions.
As far as I know, there's no migration tooling available per se, so you'd have to start from a blank project and then convert your script to static class and function.json to proper bindings.