![]() ![]() ![]() IMessageActivity currentCard = adc.GetCurentFeedback(feedback) ĬurrentCard.Id = Īwait turnContext.UpdateActivityAsync(currentCard) ![]() IMessageActivity deativatedCard = adc.GetDeactivatedFeedback(feedback) ĭeativatedCard.Id = Īwait turnContext.UpdateActivityAsync(deativatedCard) If (())ĪdaptiveCardsController adc = new AdaptiveCardsController(_hosturl) Additionally, the current userID ( AadObjectId) needs to be added to the userIDs of the card so the user is not able to vote again. Corresponding on the number of the vote (the scale 1-5) correct vote needs to be increased by one. If a vote is requested two things need to happen. Having that done based on the verb, it’s possible to detect if it’s another vote or a simple refresh from a user that are already voted. Compared to the NodeJS version it’s a bit complex to convert that to a JSon object. Here all necessary information are contained inside turnContext or directly invokeValue. In Code on bot side this arrives in OnAdaptiveCardInvokeAsync. This can be caught inside the code while returning to the bot on giving feedback. This is realized by an ActionSet where only the first one is shown for brevity and represented by Action.Execute with a verb once again. What is more important here is the option to vote. It’s represented by the “refresh” part which is shortened here and explained later. Request feedback (once)įirst important thing here is to use at least version 1.4 to have a chance for using the Adaptive Cards Universal Action Model at a later point of time. The webApplicationInfo is to establish permissions to the meeting’s chat “get control over the chat” to catch the lifecycle events. As a member of the chat the bot can then also post/update (it’s own) posts cause added to the chat as member. Nevertheless, it still enables the bot “get control over the chat” with Read access which enables to catch the lifecycle events. This looks a bit different than in my “old” NodeJS based post but this is due to a change beginning with teams manifest schema 1.12. In the manifest the following settings are necessary: "validDomains": [ Some things like “Hello World Card” stuff can be get rid of and then for attending a Teams meeting some requirements need to be done. A Setup for a new bot solution and that’s it. ContentĪt the time of writing this post there’s no clear documentation nor a learning path for setting up a bot solution with Teams Toolkit for Visual Studio 2022. Net Meeting lifecycle bot catching or mentioning several lifecycle events of a Teams meeting. This will illustrate a Teams Toolkit for Visual Studio and. Net versions on behalf of the new Teams Toolkit. I also, a while ago, started to transform some of my Teams app samples to Visual Studio and. In the past, I already created a Teams meeting app collecting feedback at the end of a meeting with a bot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |