Hi Pradeep,
No Problem. Looking over:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=python-v2%2Cin-process%2Cnodejs-v4%2Cextensionv5&pivots=programming-language-csharp
and
https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio%2Cblob-storage#running-azurite-from-an-azure-functions-project
I still cannot get this to work.
The built-in template in VS2022 uses the in-process model - (I saw that was being deprecated). However: I have all of the required packages installed by default and set up everything according to the template which attempts to install dependencies when the project is being built.
Please try to get the StorageConnection working in VS 2022 for local development using Azurite Emulator, Im sure you would feel the same pain I do. Maybe you will have better insight to a fix to help me understand what is missing?
-=-=-
In Example:
I set up a new AppFunction project, taking all defaults for BlobStorage, setting up the Azurite Emulator and connection and having the VS template install all dependencies. When the project was ready, the 'BlobTrigger' is banged out. I tried to install the lastest WebExtension.Storage - using intellisense -> find and install latest stable <- Followed all steps, and it did not work. I have to update all Nuget packages (in order) then install the latest WebStorage component.
The built-in project template for Blob Storage (and probably everything that needs WeStorage) is pretty broken out of the box, and takes hand-wringing to get it to build.
Once I get it building and the azurite emulator running, and everything looks good in the 'Connected Services'; the Function App fails with the error listed above. The Host (Azurite) has a bad reference to System.Memory.Data.
Currently, I have not found a clear way to test Storage FunctionApps locally before publishing. It does not give me confidence that this will work once published.
Is there a magic workaround to get this working to test WebStorage functions locally?
If not: where can I file a bug to the proper team to get this fixed? If there is a way to simply attach this thread to bring it to the attention of the proper team, that would be much appreciated.
Please advise.
Thanks much,
-Timothy