Thanks for the article! Do you have any tips on developing bots with multiple developers? Especially in combination with authentication, it seems cumbersome to setup a bot channel registration and different manifest package (thus uploaded app) for every developer.
I thought the bot framework emulator would be one option but it won't give you Teams-specific context. Is there an easier solution? How do bigger developer teams do this?
Code, write, talk, and doodle about JavaScript & stuff. π±-as-a-Service: HTTP Status Cats, RasPi KittyCam, Git Purr π» I have more (older) writings about the web on girliemac.com.
Hi Nils, thank you for your comment and I am sorry about this late reply!
In this series of articles, I only focus on the features and nothing else, but yes, in the reality there are a lot more things involved, like security, access management, etc.
Bot development is all associated with Azure services, although the tool used in the article (App Studio) does some of the operations like configuration automatically so you don't need to manually do anything on your Azure portal.
But when you have more complex tasks and work with more people, you will need to set up manually on Azureβ
Azure DevOps: to manage everything(access, keys, auth etc.)
Azure AD: to help to access Test, Build and Release environments on Azure
Bot testing can be done on Bot Framework emulator that you mentioned. But yes, you are right, it only helps some of the functionality and not Teams-specific features like messaging extensions and adaptive card actions.
So your team may end up testing and debugging on own computers. This requires some sort of tunneling so calls from the Azure Bot Channel Service can reach your code. If we had a shared bot registration, there would only be one tunnel URL. If only one developer works at a time, that could work. (Yeah, I know this isn't the best!)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the article! Do you have any tips on developing bots with multiple developers? Especially in combination with authentication, it seems cumbersome to setup a bot channel registration and different manifest package (thus uploaded app) for every developer.
I thought the bot framework emulator would be one option but it won't give you Teams-specific context. Is there an easier solution? How do bigger developer teams do this?
Hi Nils, thank you for your comment and I am sorry about this late reply!
In this series of articles, I only focus on the features and nothing else, but yes, in the reality there are a lot more things involved, like security, access management, etc.
Bot development is all associated with Azure services, although the tool used in the article (App Studio) does some of the operations like configuration automatically so you don't need to manually do anything on your Azure portal.
But when you have more complex tasks and work with more people, you will need to set up manually on Azureβ
Azure DevOps: to manage everything(access, keys, auth etc.)
Azure AD: to help to access Test, Build and Release environments on Azure
docs.microsoft.com/en-us/azure/dev...
Bot testing can be done on Bot Framework emulator that you mentioned. But yes, you are right, it only helps some of the functionality and not Teams-specific features like messaging extensions and adaptive card actions.
So your team may end up testing and debugging on own computers. This requires some sort of tunneling so calls from the Azure Bot Channel Service can reach your code. If we had a shared bot registration, there would only be one tunnel URL. If only one developer works at a time, that could work. (Yeah, I know this isn't the best!)