Cannot use semantic search bindings in .NET 8 about azure-functions-openai-extension HOT 4 CLOSED

Your sample project targets .NET in-proc, so this is mostly expected. For the benefit of anyone else who lands here, per the .NET 8 announcement, Azure Functions doesn't yet support .NET 8 using the in-proc model.

Support for .NET 8 does not currently extend to applications using the in-process model. See the August 2023 roadmap update for more information regarding support timelines.

In the meantime, we need to create a .NET isolated version of these bindings so that we can support .NET 8 users on the .NET Isolated worker.

/cc @aishwaryabh

from azure-functions-openai-extension.

Oh thank you @cgillum - you're right I had not connected the dots. Is there any possibility of getting a better error message for this case, maybe pointing to the article/roadmap?

When Open.AI.Kusto is ready in isolated, I'll try .NET 8 again.

Once we have taken action on any doc clarifications or error messages please feel free to close this.

from azure-functions-openai-extension.

As an extension vendor, I'm not sure if there's much we can do to control the error experience, but I wonder if @fabiocav or @mattchenderson have thoughts on how the "graceful error message" can be solved in general for customers that try to run in-process functions on .NET 8?

from azure-functions-openai-extension.

@paulyuk , @cgillum - We have added samples for dotnet-isolated using dotnet 8.
PR #50

Are we good to close this issue now?

from azure-functions-openai-extension.