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.

Sign up for GitHub

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

Jump to bottom

ServiceBus should use INameResolver, not ConfigurationManager #1347

Closed
MikeStall opened this issue Sep 20, 2017 · 3 comments
Closed

ServiceBus should use INameResolver, not ConfigurationManager #1347

MikeStall opened this issue Sep 20, 2017 · 3 comments
Assignees
@alrod
Labels
bug netcore
Milestone
Backlog

Comments

@MikeStall
Copy link
Contributor

ServiceBus should use INameResolver for getting appsettings - not ConfigurationManager.
This came up here: https://stackoverflow.com/questions/46272395/override-net-connection-string-resolution
@paulbatum paulbatum added this to the Triaged milestone Oct 11, 2017
@paulbatum
Copy link
Member

Lets make sure the service bus extension for v2 uses INameResolver as part of the porting work.

@paulbatum paulbatum modified the milestones: Triaged, Sprint 11 Nov 1, 2017
@alrod alrod modified the milestones: Sprint 11, Next Nov 17, 2017
@RyanONeill1970
Copy link

Should this be closed now? INameResolver works for me. https://stackoverflow.com/questions/46272395/override-net-connection-string-resolution

@alrod
Copy link
Member

alrod commented May 8, 2019

yes, INameResolver already works

@alrod alrod closed this as completed May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alrod alrod

Labels
bug netcore
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@paulbatum @MikeStall @RyanONeill1970 @alrod