You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
When using VSCode to create a v3 Azure Function, I needed to add
a using Microsoft.Azure.Cosmos.Table
statement (and may have had to do a dotnet add package, but cannot remember for sure).
It seems all the changes with extension bundles for functions, there has been much change for what to reference....and if you even can reference the old OR newer packages.
E.g. in Tip#98 I could NOT find a way to get a package that was .NET Core based for Microsoft.Azure.ConfigurationManager or Microsoft.WindowsAzure.ConfigurationManager. Thankfully the tip said I could hardcode the storageAccount connection string...but that's less than ideal for production.
Thank you for these tips&tricks, they are really helping compared to most of the official docs for Azure Functions (and all the now outdated chaff on Stackoverflow and other forums).
The text was updated successfully, but these errors were encountered:
When using VSCode to create a v3 Azure Function, I needed to add
a
using Microsoft.Azure.Cosmos.Table
statement (and may have had to do a dotnet add package, but cannot remember for sure).
It seems all the changes with extension bundles for functions, there has been much change for what to reference....and if you even can reference the old OR newer packages.
E.g. in Tip#98 I could NOT find a way to get a package that was .NET Core based for Microsoft.Azure.ConfigurationManager or Microsoft.WindowsAzure.ConfigurationManager. Thankfully the tip said I could hardcode the storageAccount connection string...but that's less than ideal for production.
Thank you for these tips&tricks, they are really helping compared to most of the official docs for Azure Functions (and all the now outdated chaff on Stackoverflow and other forums).
The text was updated successfully, but these errors were encountered: