-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Can we create topic subscription problematically using .net core 2 #3
Comments
@lilanmadusankasilva We have a net standard client 6.1 client located on our nightly nuget feed on myget (https://www.myget.org/gallery/exceptionless) See this for more info (#2) If you specify your azure ad credentials it will create topic subscription you define in the passed in options for you. But we don't expose any management api's directly to do any management other than delete the queue. We are not going to be releasing this other than a nightly feed until Microsoft brings back the connection string based management features as requiring AD credentials to even create a topic is insane. Does this help? @shahbarkha Am I missing anything? |
@lilanmadusankasilva @niemyjski - Thats correct. We don't expose separate API to manage any entities like creating/deleting topic subscriptions . Although we ensure they get created as soon as the user tries to send or recv the message to and from the topic through PublishAsync and SubscribeAsync. |
@shahbarkha - I used code to read subscription message (I create topic manually using azure portal but I want to create subscription programmatically, so I used below code, but that code didn't create subscription with given name) So, Can I create topic subscriptions programmatically? Can you give me sample code for that? |
@lilanmadusankasilva Which code are you accessing? I don't see that we are using IAzureSubscriptionReceiver anywhere. You should use IMessage interface to access the functionality. Something like this: |
If you can please provide me working sample code? |
is that possible ?
The text was updated successfully, but these errors were encountered: