GetChangeFeedProcessorBuilder is inaccessible due to its protection level
See original GitHub issueWe are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.
Describe the bug The compiler complains that the method “GetChangeFeedProcessorBuilder” is inaccessible in Azure.Cosmos version 4 preview 3.
To Reproduce
dotnet add package Azure.Cosmos --version 4.0.0-preview3
CosmosClient cosmosClient = new CosmosClient(EndpointUrl, AuthorizationKey);
container.GetChangeFeedProcessorBuilder<object>(processorName: "changeFeedSample", onChangesDelegate: HandleChangesAsync)
.WithInstanceName("consoleHost")
.WithLeaseContainer(leaseContainer)
.Build();
Expected behavior Either the compiler should not complain or the docs should mention which method to use in the latest version.
Actual behavior The compiler doesn’t let the code be compiled.
Environment summary SDK Version: Azure.Cosmos 4.0.0-preview3 .Net Version: 6.0.101 OS Version: Windows 10 (Ubuntu 20.04 LTS using WSL)
Additional context N/A
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
C# - is inaccessible due to its protection level
This means that only Game and any classes which derive from it will have access to those protected members and no-one else to...
Read more >Access ChangeFeedProcessorBuilder from Unit Test Project
is inaccessible due to protection level [assembly: InternalsVisibleTo("Microsoft.Azure.Cosmos.Tests" + AssemblyKeys.ProductPublicKey)]
Read more >Container.GetChangeFeedProcessorBuilder Method
GetChangeFeedProcessorBuilder (String, Container+ChangeFeedStreamHandler). Initializes a ChangeFeedProcessorBuilder for change feed processing.
Read more >How to Fix .Net Error Inaccessible Due To Its Protection Level
Unlock the power of Microsoft .NET Core with my engaging Udemy courses! For all the details and limited-time $9.99 pricing, scroll down to ......
Read more >Error: It may be inaccessible due to its protection level
The issue is you have in_config as IN argument but you are not passing any value while calling the workflow.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe I expressed myself wrong. When I said “There is a reason why it is still in preview” I was admitting that @bartelink is right and that I understand that V4 wouldn’t work in some scenarios. When I rereaded it I realized I sounded like I was criticizing the fact that to this day it is still in preview, but that is NOT what I meant. Sorry for that.
I would put it differently - the V4 preview is/was a spike.
Far more useful to clarify whether the problem you cite exists on V3 (and/or what you are proposing; it’s not obvious to me from the OP) - the next V4 type thing will be based off master in this repo in order to take in all the features and fixes in the two years since then.