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

Microsoft.AspNetCore.DataProtection is v3 not compatible with azure functions anymore #16581

Closed
petrce opened this issue Jan 17, 2020 — with docs.microsoft.com · 5 comments · Fixed by #17037
Closed
Labels
Source - Docs.ms Docs Customer feedback via GitHub Issue

Comments

Copy link

petrce commented Jan 17, 2020

according to this: Azure/azure-functions-host#5447
DataProtection since version 3 is not compatible with Azure Functions anymore (v2 is fine), I think the documentation should mention it...


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@dotnet-bot dotnet-bot added ⌚ Not Triaged Source - Docs.ms Docs Customer feedback via GitHub Issue labels Jan 17, 2020
@Rick-Anderson
Copy link
Contributor

@Leon99
Copy link

Leon99 commented Jan 31, 2020

@Rick-Anderson could you clarify how your link is related to the issue @petrce referenced?

@Rick-Anderson
Copy link
Contributor

@Leon99 My link states what @petrce want's documented. It's already documented.

@Leon99
Copy link

Leon99 commented Jan 31, 2020

Hmm @Rick-Anderson I'm confused. Your link states that "DataProtection.AzureStorage uses new Azure Storage APIs" and nothing about Microsoft.AspNetCore.DataProtection being incompatible with AF v3.

@hiranamarasinghe
Copy link

hiranamarasinghe commented Feb 25, 2020

Hmm @Rick-Anderson I'm confused. Your link states that "DataProtection.AzureStorage uses new Azure Storage APIs" and nothing about Microsoft.AspNetCore.DataProtection being incompatible with AF v3.

according to this: Azure/azure-functions-host#5447
DataProtection since version 3 is not compatible with Azure Functions anymore (v2 is fine), I think the documentation should mention it...

I was able fix this issue while using IWebJobsStartup instead of FunctionsStartup. The issue seems to be IFunctionsHostBuilder in the DI container.

So this might work with this line of code in Startup.cs

public class Startup : IWebJobsStartup
{
public void Configure(IWebJobsBuilder builder) =>
builder.AddDependencyInjection(ConfigureServices);

    private void ConfigureServices(IServiceCollection services)
    {

// Your code
}

In order to resolve dependency injection you need to use third party DI resolver and I used Willezone.Azure.WebJobs.Extensio

devigo added a commit to devigo/AspNetCore.Docs that referenced this issue May 6, 2021
Rick-Anderson pushed a commit that referenced this issue May 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants