Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example for DotNet6 isolated process HTTP trigger Azure Function #3806

Open
wonboyn opened this issue Aug 4, 2022 · 0 comments
Open

Example for DotNet6 isolated process HTTP trigger Azure Function #3806

wonboyn opened this issue Aug 4, 2022 · 0 comments
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Issue is created by anyone that is not a collaborator in the repository. feature-request A request for new functionality or an enhancement to an existing one. needs-triage The issue has just been created and it has not been reviewed by the team.

Comments

@wonboyn
Copy link

wonboyn commented Aug 4, 2022

Is your feature request related to a problem? Please describe.
I'm trying to implement a simple bot as an HTTP trigger Azure Function using DotNet v6 isolated process.

The problem I'm facing is that the Function uses Microsoft.Azure.Functions.Worker.Http.HttpRequestData for the request object & Microsoft.Azure.Functions.Worker.Http.HttpResponseData for the response. Whereas the BotBuilder adapter expects Microsoft.AspNetCore.Http.HttpRequest & HttpResponse for the ProcessAsync() call

How would you recommend resolving this?

Describe the solution you'd like
An example of a simple bot in DotNet using isolated processing that is designed to be wholly deployed in an Azure Function.

@wonboyn wonboyn added feature-request A request for new functionality or an enhancement to an existing one. needs-triage The issue has just been created and it has not been reviewed by the team. labels Aug 4, 2022
@wonboyn wonboyn changed the title DotNet6 isolated process Azure Function example Example for DotNet6 isolated process HTTP trigger Azure Function Aug 4, 2022
@stevkan stevkan added customer-reported Issue is created by anyone that is not a collaborator in the repository. Bot Services Required for internal Azure reporting. Do not delete. Do not change color. labels Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Issue is created by anyone that is not a collaborator in the repository. feature-request A request for new functionality or an enhancement to an existing one. needs-triage The issue has just been created and it has not been reviewed by the team.
Projects
None yet
Development

No branches or pull requests

2 participants