[QUERY] EventHubsConnectionStringBuilder in Azure.Messaging.EventHubs?
See original GitHub issueLibrary name and version
latest
Query/Question
I have an old codebase (Microsoft.Azure.EventHubs-based) that uses EventHubsConnectionStringBuilder like this:
var connectionStringBuilder = new EventHubsConnectionStringBuilder(configConnectionString);
connectionStringBuilder.OperationTimeout = TimeSpan.FromSeconds(configOpTimeoutSeconds);
First off, there is no EventHubsConnectionStringBuilder or replacement (at least I didn’t see one). Secondly, I don’t see a replacement for OperationTimeout. How would I correctly translate this code to A.M.EH? Thanks.
Environment
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
EventHubsConnectionStringBuil...
EventHubsConnectionStringBuilder can be used to construct a connection string which can establish communication with Event Hubs entities.
Read more >EventHubsConnectionStringBuil...
EventHubsConnectionStringBuilder Constructors. Reference. Feedback ... Event Hubs ConnectionString ... Fully qualified domain name for Event Hubs.
Read more >Samples for the Azure.Messaging.EventHubs client library
A discussion of the metadata available for an Event Hub instance and demonstration of how to query and inspect the information. Publishing ...
Read more >The connection string used for an Event Hub client must ...
I am getting below error:- Azure.Messaging.EventHubs: The connection string used for an Event Hub client must specify the Event Hubs namespace host, ...
Read more >Send or receive events using .NET - Azure Event Hubs
In this quickstart, you learn how to send events to an event hub and then receive those events from the event hub using...
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
Ok, TryTimeout is the new OperationTimeout (maybe add that bit of info to the migration document?). That should be enough to migrate the existing code to its equivalent new shape.
Hi @christophwille, since you haven’t asked that we “
/unresolve
” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve
” to reopen the issue.