- [4165] Show multiple runtime matches for
targetFramework
when creating from Functions API - [4195] Enable end-to-end Azure tests and add more tests
- [4215] Update backup templates
- [4200] Upgrade
@azure/arm-appservice
to enable flex consumption SKU support
- [4182] Display a warning when attempting to deploy a containerized function app
- [4184] "+ Create new function app" command when deploying a containerized function app
- [4104] Flex Consumption SKU support for creation and deploying
- [4115] Added Azure Blob Storage Trigger (using Event Grid) templates for flex consumption apps
- [4138] Display a warning after deploying an Azure Blob Storage Trigger to a flex consumption app
- [4130]
Create new function app
from Deploy command - [4101] Add retry logic to getFunctionsForHostedProject on ECONNREFUSED
- [4127] Expanding in-proc .NET support
- [4125] Changed deploying by function app id to use
azureFunctions.deployByFunctionAppId
rather thanazureFunctions.deploy
- [4130] Various UX changes in local workspace view
Full Changelog: https://github.com/microsoft/vscode-azurefunctions/milestone/66?closed=1
- [4112] Fix listing functions on sovereign clouds
- [4096] Update initial launch.json for Python to use debugpy
- Minor text fixes
- [3943], [3964] Support for creating containerized function apps
- [3929] Support for creating containerized function projects
- [3984] Improved "Execute Function" flow for EventGrid functions
- [3967] Fixes functions not deploying for Linux Consumption apps
- [3969] Fixes deploy subpath setting being ignored
- [3881] Add workspace functions to extension API
- [3887] Automatically enable full monitoring for Java Elastic Premium
- [3916] Add EventGrid Cloud Event templates for .NET to verified list
- [3924], [3297] Improve creating new local app setting experience during new function template creation
- [3813] Fix Windows files not appearing under the Files node
- [3889] Fix .gitignore being ignored during deployment
- [3902] Remove Azure Account from extension dependencies
- [3831] Use Node 18.15
- [3832] Remove all .NET 5 (EOL) tests
- [3918] Update
eslint-config
to enforce import types
Full Changelog: https://github.com/microsoft/vscode-azurefunctions/compare/v1.13.1...v1.13.2
- Enable Python 3.11 for GA
- Remove preview label from Node v4 programming model and make it the default over v3
- Remove '-alpha.7' from v4 node projects
- Python V2 programming model GA by @nturinski in microsoft#3799
- Python V2 blueprint support by @nturinski in microsoft#3799
- .NET 8 SDK support @nturinski in microsoft#3841
- Fix Windows files node feature by @alexweininger in microsoft#3813
- Function app creation not setting
netFrameworkVersion
properly by @nturinski in microsoft#3847
Full Changelog: https://github.com/microsoft/vscode-azurefunctions/compare/v1.12.4...v1.13.0
- Minor improvements to deployment logic by @nturinski in microsoft#3760
(intermediate value).parsedBody.map is not a function
error when deploying Function App #3769- Fail to connect to log stream #3775
- Unexpected status code: 401 when executing remote function #3788
- Azure Functions icon not appearing in the workspace view when using a light theme #3783
- Azure Functions runtime V2 and V3 now show EOL warnings #3771
- Fixed an issue where deployment failed due to empty lines in the
.funcignore
file.
- Add Ballerina language support by @xlight05 in microsoft#3584
- Print a warning if the function project root can't be found on deploy by @mkfrey in microsoft#3764
- Fix executing service bus topic trigger by @alexweininger in microsoft#3763
- Add actions submenu to workspace view title by @alexweininger in #3719
- Allow user to create an Event Hub namespace and/or Event Hub when creating EventHubTrigger by @nturinski in #3713
- Support ZRS enabled storage accounts in advanced create by @alexweininger in #3737
- Fix view properties command for function apps by @alexweininger in #3714
- Fix SWA create function for node model v4 by @ejizba in #3721
- Hardcode default bundle version by @alexweininger in #3727
- Fix create function app when workspace items are selected by @alexweininger in #3732
- Fix view properties command on remote function by @alexweininger in #3736
- Update to utils v2 by @alexweininger in #3707
- Upgrade to TS 5.1.3 by @alexweininger in #3712
- Remove onCommand activation events by @alexweininger in #3741
- Resolve using list instead of get by @alexweininger in #3726
- Update dependencies to fix CG alerts by @bwateratmsft in #3720
- Bump semver from 5.7.1 to 7.5.2 by @dependabot in #3724
- Python V2 templates have left preview!
- Add support for the upcoming Azure Resources Focus feature
- Verify
AzureWebJobsFeatureFlags
setting hasEnableWorkerIndexing
and enable prior to deployment for Node Model v4 by @nturinski in microsoft#3653 - Add clean script to TypeScript projects by @ejizba in microsoft#3654
- Ensure that the app settings have propogated to production app before deploying by @nturinski in microsoft#3656
- Improve task comparison during project init by @alexweininger in microsoft#3671
- Change the name of the
windows-process-tree
module by @nturinski in microsoft#3669
- Update backup templates by @alexweininger in #3602
- Remove azureWebJobsStorage validation on deploy by @MicroFish91 in #3647
- Update .NET Isolated detection to check against the template ID by @MicroFish91 in #3644
- Fix parsing binding setting with missing help resource by @alexweininger in #3601
- Fix TypeScript project language detection by @alexweininger in #3604
- Don't throw error when missing 'requirements.txt' by @MicroFish91 in #3627
- Make skip for now message more clear when there are no resources available by @nturinski in #3611
- Change learn more label for programming model step by @nturinski in #3609
- Remove node.js programming model experimental flag by @nturinski in #3612
- Remove remote connection overwrite prompting by @MicroFish91 in #3593
- Add Dotnet Isolated runtime specific dependencies for Durable by @MicroFish91 in #3597
- Fix getting package references from csproj from multiple item groups by @alexweininger in #3603
- Fix when clause contexts for upcoming VS Code release (v1.77) by @MicroFish91 in #3621
- Azure Functions walkthrough by @esweet431 in #3573
- Detect new NodeJs model during "Init for VS Code" by @ejizba in #3586
- Minor fixes for durable in new NodeJs model by @ejizba in #3587
- Forward compatibility with Azure Resources API v2 by @alexweininger in #3548
- Deployment failure due to
Function Core Tools
not being installed #3556 - Missing event hub connection prompt #3554
- Enable support for Python 3.10 when creating projects #3486
- Support new Durable Functions backend options for the following languages: C#, JavaScript, TypeScript, Python #3273
- Support for new Node.js language model (Preview). Set feature flag
azureFunctions.showNodeProgrammingModel
to enable #3285 - Declared limited support for virtual workspaces #2793
- Added Azurite generated emulator files to .funcignore #3371
- Removed deprecated .NET runtime stacks for creating new projects and Function Apps #3474
- Remove Python 3.6 due to EOL #3526
- Add warning messages for Azure Functions Core Tools EOL and mismatched versions #3346 #2985
- Improve Core Tools install experience for Linux #2745
- Create Function button in Workspace view #3350
- Warning when a stack has an upcoming end of life #3353
- Updated host.json template to enable dynamic concurrency #3248
- Always on = on when creating an Azure Function App on an App Service plan #3037
- Automatically run
npm install
after initializing a TypeScript or JavaScript Project #3034
- Revert addition of PyStein "feature flag" setting. #3386
- Deployment failures initialized from "Deploy..." button on Workspace ribbon #3369
- Log Analytic workspace resource provider not being registered blocked creation #3352
- Support for new Python language model (set feature flag
azureFunctions.showPystienModel
to enable) #3235 - Support for Java 17 (Preview) #3245
- Use appropriate version of extension bundle in Python V2 projects #3304
- Update Python V2 naming #3305
- update FUNCTIONS-WORKER-RUNTIME setting with remote function app #3288
- Add net7 tests #3277
- Just use the 1st value for creating python projects #3276
- Push Framework argument for .net70 #3273
- Switch to latest VS Code test package #3275
- Replace fse with AzExtFsUtils where possible #3268
- Update net7 template #3262
- Update backup templates #3260
- Move workflow from root to workflows folder #3259
- Rename info-needed-closer #3257
- Bump terser from 5.9.0 to 5.14.2 #3253
- Use shared azure id parsing utils #3246
- Add post release version bumper #3244
- Update AppInsights key #3239
- Update
FUNCTIONS-WORKER-RUNTIME
setting when deployingdotnet-isolated
projects todotnet
remote #3288
- An error occurs for the setting "azureFunctions.projectLanguageModel" with the default value "0" #3315
- Do not open new documents if opened in new window #3307
- An error occurs if a Java/Python (New Model Preview) project opens in VS Code previously when creating a new Python project #3300
- [Suggestion] It would be better to change log to "Delete Slot 'xxx' Succeeded" in the ACTIVITYLOG window after deleting a slot #3148
- View properties doesn't display site config #3264
- Fix tests to use v4 Core Tools #3267
- App Insights APM 2.1 Enablement and Representation #2835
- [Suggestion] Don't show Logic Apps in Functions Extension #3165
- Fix
ServiceUnavailable
error that occurs in Files and Logs node #3188
- Updated minimum version of VS Code to 1.66.0 #3231
- Updated @vscode/extension-telemetry to 0.6.2 #3229
- Update @vscode/extension-telemetry to 0.5.2 #3206
- Error when picking Create new local app setting from local.settings.json when creating blob trigger #3191
- Deploy command is now accessible via the Workspace Deploy menu
We've made some large design changes to the Azure extensions for VS Code. View App Centric release notes
- Add Execute Step in createFunction API #3150
- Fix "Create Project" flow losing options #3116
- Zip deploy fails with ECONNRESET or 400 Bad Request on VS Code versions
>=1.66.0
#2844
createFunction
API handles multiple target frameworks- Microsoft Cloud Deutschland (Azure Germany) is no longer supported. Migration information
- Remove preview flag from Azure Functions v4
- Option to change Azure Functions runtime version when selecting runtime
- AzureFunctionsExtensionApi command
validateFuncCoreToolsInstalled
- AzureFunctionsExtensionApi command
validateFuncCoreToolsInstalled
proxies.json
are no longer created when callingCreate New Project...
- Proxy tree items are no longer displayed in local project tree view
- Preview support for .NET 6 on Azure Functions v4
- Added setting "azureFunctions.funcCliPath" to explicitly control the path of the "func" executable used for debug and deploy tasks
- Minimum version of VS Code is now 1.57.0
- Support Azure Functions on Kubernetes with Azure Arc (Preview)
- Minimum version of VS Code is now 1.53.0
- Icons updated to match VS Code's theme. Install new product icon themes here
- .NET 5 support for creating projects/functions, copying http trigger urls, and creating a Function App in Azure
- Now depends on the "Azure Resources" extension, which provides a "Resource Groups" and "Help and Feedback" view
- TypeScript projects default to TypeScript v4.0
- Extension may become unresponsive when deploying on WSL or Codespaces
- Debugging a C# project on Mac/Linux may take ~30 seconds longer than before v1.2.1 of the extension
- Fixed failure to debug on VS Code v1.53+ because extension did not activate
- Mitigated "ECONNRESET" errors by retrying the request
- Allow Python v3.9 when creating a virtual environment for a local project
- Remove "Preview" label for custom handler projects
- Python project fails to attach debugger with error "The operation has timed out."
- Support debugging .NET 5 projects
- Modified post-debug behavior so that "func host start" output remains viewable and to optimistically fix issue where VS Code becomes unresponsive #1401
- Added "Reload Templates" option when creating a function that will also clear the template cache (Use setting "azureFunctions.showReloadTemplates" to enable)
- "Report an Issue" button has been removed from errors. Instead, use the "Report Issue" command in the command palette
- Dynamically retrieve the runtime stacks available in Azure so that the extension supports them as soon as possible, including upcoming preview support for Node 14
- Preview support for creating custom handler projects and functions
- Preview support for generating functions from an OpenAPI specification
- Extended deployment slot support to Linux consumption apps
- Warn when attempting to deploy a 64-bit C# project to a 32-bit Function App (thanks @prabh-62)
- Allow comments in "local.settings.json"
- Deploy error when
AzureWebJobsStorage
app setting doesn't have EndpointSuffix - createFunction API call fails to create C# triggers
- Create, debug, and deploy PowerShell 7 and Java 11 projects
- Preview support to deploy custom handler projects
- Improved extension activation time (by switching to the azure-sdk-for-js)
- Minimum version of VS Code is now 1.48.0
- Support for PowerShell 6 projects has been deprecated
- Added "Execute Function Now" for all trigger types
- Support viewing remote files on Linux consumption plans
- To improve performance, "WEBSITE_RUN_FROM_PACKAGE" will automatically be added to all Windows plans when deploying. Set "WEBSITE_RUN_FROM_PACKAGE" to "0" to override this behavior
- Enhanced deployment logs to show more information and more accurately detect failures
- Added setting "azureFunctions.validateFuncCoreTools" to skip validating Azure Functions Core Tools before debugging
- Minimum version of VS Code is now 1.40.0
- Enable/disable a function
- Added setting "azureFunctions.postDeployTask" to run a task after every deploy. New JavaScript/TypeScript projects will run "npm install" by default
- Improved performance of loading templates
- Pre-deploy task notification becomes unresponsive and prevents deploy
- Updated C# recommended extension id to "ms-dotnettools.csharp"
- Java and C# support for the local project tree item
- Copy local http trigger urls
- Execute local timer triggers
- Allow Python 3.8 when creating local project or deploying to Azure (only supported in v3 of the Azure Functions runtime)
- Allow deploying Java projects to Linux Function Apps in Azure (only supported in v3 of the Azure Functions runtime)
- Added setting "azureFunctions.showDeployConfirmation" to turn off "Are you sure you want to deploy..." dialog
- Logging is enabled by default when creating a Function App in Azure
- Bindings are no longer displayed in the tree. View properties on the function instead
- "Add Binding..." was moved from the local "Bindings" tree item to the function tree item
- Prompt for runtime before OS when creating a Function App in Azure. OS will not be prompted if the runtime doesn't support it
- Inline button to view deployment logs was removed. Left or right click the tree item instead
- Reduced time to create the first Function App in Azure on some new subscriptions
- Prompt to select existing resource group instead of "403" error when subscription doesn't have permissions to create
- "Init project for VS Code" will detect projects using "extensions.csproj" and configure to use "func extensions install" instead of bundle
- Browse to website
- Added option to create a Node 12.x Function App, only supported in v3 of the Azure Functions runtime
- If the Azure Functions runtime version cannot be automatically detected, default to v3 instead of v2
- Removed ability to update app settings in Azure if language or runtime version don't match when deploying. Instead, create a new Function App in Azure
- Select Python version (3.6.x or 3.7.x) when creating a project
- Linux Premium Function App fails to run because it's missing CONTENT* app settings
- Select Node.js or Python runtime version when creating a Function App in Azure
- Added support for Azure Functions v3 Preview in the following existing features:
- Install func cli from the command palette (brew and npm only)
- Create new project/function from a version-specific template
- Validate local version matches remote version when deploying
- View Files and Logs for your Function App in Azure
- Removed support for "azureFunctions.projectRuntime" value of "beta". Use "~1", "~2", or "~3" instead
- Fix error "Expected value to be neither null nor undefined" when adding a binding
- Added support for deployment slots (feature flag no longer required)
- Deploy
- Stream logs
- Start/stop/restart
- Create/delete/swap
- Default new Python projects to remote build. See here for more info: https://aka.ms/AA5vsfd
- Function templates respect extension bundle specified in host.json
- Add option to use a Premium (preview) hosting plan when creating a Function App in Azure
- Fixed subfolders of a symbolically linked folder not included during deploy
- Fixed bundle dependency not added during "Add Binding"
- Reduced false positive deploy failures when listing triggers or logs
- Fix error "Expected value to be neither null nor undefined" when creating App Insights resource with existing resource group
- Fix error "r.map is not a function" if
Microsoft.Insights
is not a registered provider for your subscription
- Added Python project support for remote build. Follow these steps to enable: https://aka.ms/AA5vsfd
- Added Application Insights support when creating a Function App in Azure
- Added a local project tree item to the Azure Functions view (does not apply to Java or C#)
- Copy local http trigger urls
- Execute local timer triggers
- View and add bindings
- Removed "Preview" label from Python projects and Linux Function Apps
- Removed setting "azureFunctions.advancedCreation" in favor of a separate "Advanced" command to create Function Apps
- Renamed default Python virtual environment from ".env" to ".venv"
- Basic create mode will now prompt for a location when creating a Function App
- Fixed copying non-anonymous function urls for Linux consumption apps
- Reduced occurrence of error "Failed to detect running Functions host" for C# debugging
- Fixed creation of Linux Dedicated Function Apps
- Improve performance of loading Function Apps
- New projects will no longer have a dependency on .NET Core for non-.NET developers
- Preview support to create, debug, and deploy PowerShell projects
- Right click in a "function.json" file to add a binding from a template
- New JavaScript projects will include a package.json, with automatic logic to install any dependencies before debug or deploy
- Right click on a timer function to execute now
- If in advanced create mode, you may use a premium plan when creating a Function App in Azure
- Added templates to the "verified" category, including Event Hub and Durable functions
- Improved multi-prompt wizards (e.g. "Create function")
- Added support for back button
- All prompts will occur up front before any steps are executed
- Creating a project will automatically prompt for the first function
- Projects in sub-directory of a workspace will be recognized as function projects
- Prompt to upload local app settings after deploy
- View commit in GitHub for an applicable deployment
- Creating a Function App in Azure will only prompt for Function App name. Set
azureFunctions.advancedCreation
totrue
to be prompted for all other values.
- Create, debug, and deploy TypeScript projects
- Support for
.funcignore
file, which will exclude paths when deploying based on.gitignore
syntax. This file is also used by the func cli. - Added templates to the "verified" category, including Event Grid for most languages
- If using "zipGlobPattern" and "zipIgnorePattern" settings when deploying, you will be prompted to use
.funcignore
file instead
- Improved startup and installation performance
- Improved reliability of Python projects
- Leverages ptvsd module shipped with Python extension for VS Code instead of installing ptvsd in your virtual environment
- Removed terminal specific separators from debug config
- Allow deployment to dedicated App Service plans
- Added retry logic to handle momentary issues while deploying
- Added
azureFunctions.advancedCreation
setting. When set to true, this allows you to manually select several properties (i.e. OS and runtime) when creating a Function App - App setting values are hidden by default
- Java projects now leverage common settings for deploy. See our wiki for more info
- Projects will no longer run
mvn clean package
unlessazureFunctions.preDeployTask
is set - Projects will no longer deploy a subpath of the workspace unless
azureFunctions.deploySubpath
is set
- Projects will no longer run
- Provide option to "Deploy Anyway" if pre-deploy task fails
- If "azureFunctions.preDeployTask" is not set, do not run any task
- Deployments node for Function Apps that are connected to a GitHub or LocalGit repository
- View deployment logs
- Redeploy previous deployments
- Preview support for deployment slots (feature flag
azureFunctions.enableSlots
must be set totrue
)- Deploy
- Stream logs
- Start/stop/restart
- Create/delete/swap
- Feature flag no longer required for creating Python projects
- Bumped minimum version of "ps-tree" due to event-stream#116
- Improved debugging
- Functions host will be stopped after you detach
- Terminal (where Http Triggers are listed) will be the default view rather than Debug Console
- Improved Python projects
- Deploying will automatically sync triggers
- Users will be warned if deploying to Windows
- pylint will be added to the local virtual environment by default
- "pip install" will be run before debugging
- Added Cosmos DB trigger to "Verified" category for C#
- JavaScript and Python projects will hide 'obj' and 'bin' folder by default (used for Functions extensions). NOTE: extensions.csproj will not be hidden and should still be checked in to source control
- Local debugging for Python projects may fail with "python.exe -m ptvsd: error: the following arguments are required: --host.". Can be resolved by changing the
"languageWorkers__python__arguments"
setting in the.vscode/tasks.json
to"-m ptvsd --host 127.0.0.1 --port 9091"
- Preview support for creating and debugging Python projects. To enable, set
azureFunctions.enablePython
to true. IMPORTANT: Python support in Azure is still in private preview. - Added several more templates to the "verified" category, including Cosmos DB and Service Bus.
- Newly created Function Apps will default to "Run From Package". See here for more info.
- Deprecated projectRuntime of "beta" in favor of "~2".
- "azureFunctions.deploySubpath" setting takes precedence
- "Copy Function Url" for v2 non-anonymous functions will copy an invalid url #567
- Functions cannot be listed for Linux Consumption apps azure-functions-host#3502
- Debugging C# functions after fixing a build break fails with error "Failed to stop previous running Functions host..." #534
- Improved Java templates
- More templates are available
- Templates will be automatically updated going forward
- JavaScript projects run
func extensions install
before debug and deploy
- "Copy Function Url" for v2 non-anonymous functions will copy an invalid url (that returns a 401 Unauthorized error) due to recent breaking changes in the runtime #567
- Improved C# templates
- More templates are available
- Templates will be automatically updated going forward
- Templates are installed only with the scope of VS Code and no longer affect machine-wide .NET CLI templates
- Added support for deploying to App Service Environments
- Debug config for JavaScript functions has changed. See https://aka.ms/AA1vrxa for more info
- New C# projects will deploy the result of a 'dotnet publish' rather than deploying the build output
- Azure Function Apps created through VS Code will automatically match the runtime from your local machine rather than always using v1
- Users will not be prompted to install the latest version of the func cli if high priority issues are discovered
- For example, the latest version of the func cli (2.0.1-beta.26) breaks JavaScript debugging
- Improved warning when Azure Functions Core Tools is out of date
- In some cases, an 'Update' option is provided that will automatically run the necessary commmands
- Warning now displays for all users, regardless of how they installed the func cli
- Function templates are now versioned and can be controlled with the "azureFunctions.templateVersion" setting
- Select open behavior after creating a new project ("Add to workspace", "Open in current window", or "Open in new window")
- Moved Azure Functions Explorer to new Azure view container instead of file explorer
- Deployment fail when deploying to Function App with a custom domain
- Upload and download application settings
- Prompt to automatically install the Azure Functions Core Tools when possible
- "Report an issue" button on error dialogs that links to the GitHub repo
- Subscription filter button next to Subscription nodes in the explorer
- Deploy to Function App context menu action for Function Apps
- JavaScript projects will default to runtime "beta" instead of "~1" on Mac/Linux. See here for more information.
- Automatically detect projects created outside of VS Code and prompt to initialize
- View/Delete Proxies
- Remote Debug Java Function Apps (experimental)
- Add backup templates in case there is no internet or in case the functions portal api changes
- Stream logs from your Azure Function Apps
- Support projects in multi-root workspaces
- Link to deployment tutorial
- Show warning if your Azure Functions Core Tools version is out-of-date
- Update Microsoft.Net.Sdk.Functions version so that C# functions work on Mac/Linux
- C# local debugging
- Fixed "Cannot access the file because it is being used by another process." error by automatically restarting the functions host
- Fixed project being built twice for every F5
- Improved performance of 'azureFunctions.pickProcess' on Windows
- Create, Debug, and Deploy a C# class library project
- User settings for language/runtime/templateFilter now apply when creating a new project
- Set these once and never select a language, runtime, or filter again
- Set the language to something other than "JavaScript", "C#", or "Java" for preview support of other languages (for example, "C#Script")
- The Functions host must be stopped after making changes and before rebuilding to C# functions #185
- C# class library functions fail to run on Mac #164
- C# script functions fail to attach on Windows #180
- Copy HTTP Trigger Url
- Change Deployment Source (Zip Deploy vs. Local Git Deploy)
- Settings to control project language and runtime
- JavaScript 'Verified' templates not displayed
- Java templates not displayed
- Java support
- Create new project
- Create new function
- Deploy project
- Azure Functions Explorer
- View and delete functions
- View, add, edit, and delete Application Settings
- 'Load more' for large number of resources
- Improved 'Create new function'
- All JavaScript templates listed in the Azure portal are now supported
- The user will be prompted for function settings on creation
- Added
azureFunctions.templateFilter
setting to control which templates are displayed (Verified, Core, or All)
- Added 'Create' and 'Delete' commmands for Function Apps in Azure
- Updated icons to match the Azure portal
- Moved 'Deploy here as Zip' option from Function App nodes to the explorer menu bar
- Show warning message that zip deploy is a destructive action
- Leverage new app service zipdeploy
- Zip Deploy no longer runs 'npm install'. It expects a ready-to-run app
- Create new project
- Create new function from template
- Debug function projects locally
- View Azure Functions
- Deploy to Azure Functions
- Start, stop, and restart Azure Functions
- JSON Intellisense for
function.json
,host.json
, andproxies.json