Publish Duplicate Client Side Page Changes To Original Page Within Same SPO Site Pages Library

 

Problem Statement

 

This article is a continuation of my previous article, Duplicate the Client Side Pages into same Modern SharePoint Online Library Folder where I explained how to duplicate the client side page with all existing controls.

 

In this article, I would like to explain this: If the user makes any changes to duplicate page, how to publish the duplicate client side pages to the original page into same site pages library within the same site collection.

 

As a developer, we have a couple of options to duplicate the page into another modern site collection library or different folder structure, but there is no way to copy the pages within the same modern site collection sites library within the same folder structure.

 

Prerequisite Steps

 

Let's create a page and add existing below control, or user can add any other available controls. This is just for demo purposes.

• SharePoint Online PnP PowerShell Overview here
• Browse the existing pages

Home Page looks like this,

Duplicate Page looks like this with changes,

• Add new control
• Modify the pages control layout

Approach Overview

 

Key steps to publish duplicate client side page with changes to original Modern Site Collection Site Pages into Same Library Folder.

1. Use PnP Online to connect to SharePoint Online Modern Site
2. Export PnP Client Side Pages Command export pages with PnP Provisioning Template
3. Store it locally.
4. Apply PnP Provisioning Template store it with different name. 

1. try   
2.    {  
3.   
4.          $srcUrl = "https://mittal1201.sharepoint.com/sites/commsitehub"   
5.          Connect-PnPOnline -Url $srcUrl  
6.   
7.          $SourcePageName = "home_duplicate"  
8.          $TargetPageName = "home"  
9.       
10.          $tempFile = 'C:\CsharpCorner\'+ $SourcePageName +'.xml'  
11.          Export-PnPClientSidePage -Force -Identity $SourcePageName -Out $tempFile  
12.   
13.          $con = Get-Content $tempFile  
14.          $sourcepage=$SourcePageName +".aspx"  
15.          $targetpage=$TargetPageName +".aspx"  
16.        
17.          $con | % { $_.Replace($sourcepage,$targetpage) } | Set-Content $tempFile  
18.          Apply-PnPProvisioningTemplate -Path  $tempFile  
19.          write-host -ForegroundColor Magenta "Page reverted with name of  " $targetpage      
20.        
21.      
22. }   
23. catch {  
24.     Write-Host - ForegroundColor Red 'Error ', ':'  
25.     $Error[0].ToString();  
26.      
27. }  

Save and run this script.

 

OutPut Steps

 

Applying template to client side pages

 

Export-PnPClientSidePage Cmdlets applying the PnP Provisioning template and export ".xml" file into shared locaiton. Cmdlets referece can be find here 

Creation of client side pages

 

Apply-PnPProvisioningTemplate cmdlets will create a new page within the same library from download or exported ".xml" file with provided name i.e. pagename _ duplicate

Cmdlets referece can be find here

Final Duplicate Page Outcome

 

Browse the url; i.e., original page. New Client Side Page will be available with all configuration and controls.

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article.

Duplicate Client Side Pages Into Same Modern SharePoint Online SitePages Lib

 

Problem Statement 

 

In this article, I would like to explain how to duplicate client side pages which have OOTB webparts and custom SPFx webparts into the same site pages library within the same site collection.

 

As a developer, we have a couple of options to duplicate the page into another modern site collection library or different folder structure, but  there is no way to copy the pages within the same modern site collection site library within the same folder structure.

 

Prerequisites Steps  

 

Let's create a page and add the exisitng below controls,  or the user can add any other available controls. This is just for demo purposes. 

• SharePoint Online PnP PowerShell Overview here
• Add and Configure  Custom SPFx Control
• Add and Configure  Image Control
• Add and Configure  News Control

Approach Overview

 

We need to follow the below key steps to perform duplication of Modern Site Collection Site Pages into the Same Library Folder. 

1. Use PnP Online to connect to SharePoint Online Modern Site
2. Export PnP Client Side Pages Command  export pages with PnP Provisioning Template
3. Store it locally.
4. Apply PnP Provisioning Template store it with different name. 

SharePoint Online PnP PowerShell Script

1. try   
2.    {  
3.       
4.         $srcUrl = "https://mittal1201.sharepoint.com/sites/commsitehub"   
5.         Connect-PnPOnline -Url $srcUrl  
6.         $pageName  = [System.Web.HttpUtility]::UrlDecode("Home")  
7.         write-host $pageName  
8.         $tempFile = 'C:\CsharpCorner\'+ $pageName +'.xml'  
9.         Export-PnPClientSidePage -Force -Identity $pageName -Out $tempFile  
10.   
11.         $con = Get-Content $tempFile  
12.         $sourcepage=$pageName +".aspx"  
13.         $targetpage=$pageName +"_Duplicate.aspx"  
14.        
15.         $con | % { $_.Replace($sourcepage, $targetpage) } | Set-Content $tempFile  
16.         Apply-PnPProvisioningTemplate -Path  $tempFile  
17.         write-host -ForegroundColor Magenta "Page Created with name of  " $targetpage    
18.      
19. }   
20. catch {  
21.     Write-Host - ForegroundColor Red 'Error ', ':'  
22.     $Error[0].ToString(); 

Save and run this script.

OutPut Steps 

 

Applying template to client side pages

 

Export-PnPClientSidePage Cmdlets applying the PnP Provisioning template and export ".xml" file into shared locaiton. Cmdlets referece can be found here 

Creation of client side pages 

 

Apply-PnPProvisioningTemplate cmdlets will create a new page within same library from download or exported ".xml" file with provided name i.e. pagename _ duplicate

Cmdlets referece can be found here

 

 Final Duplicate Page outcome

 

Browse the url with suffix as _duplicate in the url. New Client Side Page will be available with all configuration and controls.

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article.

SPFX with DevOps using SharePoint ALM & Blob Storage

Implement SPFx (SharePoint Framework) deployment with DevOps using SharePoint ALM Commands & Blob Storage

Azure DevOps (Visual Studio Team Services / Team Foundation Server) consists of a set of tools and services that help developers implement DevOps, Continuous Integration, and Continuous Deployment processes for their development projects.

This article explains the steps involved in setting up your Azure DevOps environment with Continuous Integration and Continuous Deployment to automate your SharePoint Framework builds, unit tests, and deployment.

SharePoint ALM (Application Life Cycle Management) APIs provide simple APIs to manage deployment of your SharePoint Framework solutions and add-ins across your tenant or Site Collection level.

ALM APIs can be used to perform exactly the same operations that are available from a UI perspective

Continuous Integration

Continuous Integration (CI) helps developers integrate code into a shared repository by automatically build  and packaging the solution each time new code changes are submitted.

Setting up Azure DevOps for Continuous Integration with a SharePoint Framework solution requires the following steps:

Office Azure & SharePoint ALM - Build Pipeline

• Node 10.x
• Gulp Clean
• Gulp Build
• Gulp Bundle --ship
• Gulp Package-Solution --ship
• Publish Build Artifacts  (Task Version 1)
• "Display Name" -> Publish Artifact: CDN
• "Path to Publish" -> temp/deploy
• "Artifact Name" -> CDN
• "Artifact Publish Location" -> Azure Pipeline
• Publish Build  Artifact
• "Display Name" -> Publish Artifact: App
• "Path to Publish" -> sharepoint/solution
• "Artifact Name" -> App
• "Artifact Publish Location" -> Azure Pipeline

Continuous Deployment

Continuous Deployment (CD) takes validated code packages from build process and deploys them into a staging or production environment. Developers can track which deployments were successful or not and narrow down issues to specific package versions.

Setting up Azure DevOps for Continuous Deployments with a SharePoint Framework solution requires the following steps:

• Office Azure & SharePoint ALM - Build Pipeline
• Azure file copy (Task Version 2)
• "Display name"-> AzureBlobFileCopy
• "Source"->  $(System.DefaultWorkingDirectory)/_AzureDevOpsCI/CDN
• "AzureConnectionType"-> Azure Resource Manager
• "Azure Subscription"
• "Destination Type"-> Azure Blob
• "RM Storage Account"- > 
• "Container Name"->
• SharePoint ALM: Catalog Scoped Actions
• "Display name"->SharePoint ALM: Add Solution Package
• "Connection to SharePoint" -> commsite01
• "Action"-> Add Solution  Package
• "Path to SharePoint Solution Package"-> $(System.DefaultWorkingDirectory)/_AzureDevOpsCI/App/devops-01.sppkg
• "
• "PackageId output variable"-> AppPackageId
• SharePoint ALM: Catalog Scoped Actions
• "Display name"->SharePoint ALM: Deploy Solution Package
• "Connection to SharePoint" -> commsite01
• "Action"-> Deploy Solution Package
• "Id of the package in the SharePoint App Catalog"  -> $(AppPackageId)

End to End implementation SPFx deployment using Azure DevOps with SharePoint (Application Life Cycle Management) & Blob Storage for Static files.

Join me at Microsoft 365 Virtual Marathon, 36 hour event happening May 27-28 2020

Power Platform Evolution with AI Builder Model

Speedup digital transformation through the Power Platform and AI Builder. AI Builder provides AI templates (Binary Classification, Text Classification, Object Detection, Form Scanning) that you can tailor to easily add intelligence to your apps and processes in Power Apps and/or Microsoft Flow

Join me at Microsoft 365 Virtual Marathon, 36 hour event happening May 27-28 2020 

I will be speaking about Power Platform evolution with AI Builder 

Register here: https://lnkd.in/dA8vQS3 and hope to see you there! 

Virtual event page: https://lnkd.in/dqZ6Ks5 

🗓 Thursday, May, 28th 📺Room Mile 14 ⏱️06:30PM IST / 06:00PM PDT / 03:00 PM CEST

Next Generation | Document Search Bot using Bot Framework SDK V4

Azure Bot Service provides an integrated environment that is purpose-built for bot development, enabling you to build, connect, test, deploy, and manage intelligent bots.

Overview 

In this article, I am going to discuss how to leverage document search using Azure bot framework SDK V4.

SharePoint Online search engine is quite robust at the enterprise level and allows the developer to define custom managed properties and leverage that into search.

Here I am going to leverage SharePoint online search api to find the document based on keywords.

1. Azure Bot Framework used to build chatbot interface.
2. Luis cognitive services used to defined the intent and it will help to define the score and identified keywords.
3. QnAMaker cognitive service used to define the FAQ based questions and answers
4. Azure App API used to build search api and return data based on defined keywords.
5. SharePoint Online is used as content repositorty.
6. Adaptive Card used to design the card based on api results.  

Let's get started with implementation

Step 1

Lanuch VS2019 and create echo bot project.

Bot Project Structure look like this,

Step 2

Login to Luis.ai and create an app with intent, entity and utterances.

Luis is known as language understanding and used to defined intent; i.e. intention around the phrases, and Entity is used to define multple phrases with custom and build in entities.

In short, Luis has inbuilt machine learning capability and help to understand the intention around phases as well as defined keywords which will help to search documents.

Select and define intent name: "DocumentSearch" 

Select Entities and add some phrase 

Once you finish with Intent and Entities, train and publish the app.

Luis Key and End Point

Step 3

Browse the appsetting.json file in the solution and add Luis and QnA Maker keys and endpoint url:-

1. {  
2.   "MicrosoftAppId": "",  
3.   "MicrosoftAppPassword": "",  
4.   "ScmType": "",  
5.   
6.   "LuisAppId": "XXXXXXXX-3b11-4ae7-89fb-9c169d78e0ff",  
7.   "LuisAPIKey": "XXXXXX63f5ed4881a152c055309ac809",  
8.   "LuisAPIHostName": "westus.api.cognitive.microsoft.com/",  
9.   
10.   "QnAKnowledgebaseId": "XXXXXX7b-e0d4-4b32-b9c3-27634d078778",  
11.   "QnAAuthKey": "XXXXXXX-17a9-4772-aaed-fb2ba3f8775e",  
12.   "QnAEndpointHostName": "https://docsearchqna.azurewebsites.net/qnamaker"  
13. }  

Step 4

Add Luis recognizer class; i.e. create a connection with Luis based on defined Luis ID, Luis Key and Luis end point.

Create a folder name; i.e. Cognitive Services.

Add new file; i.e. SearchLuisRecognizer.cs and add the below code as-is. 

1. public class SearchLuisRecognizer : IRecognizer  
2.    {  
3.        private readonly LuisRecognizer _recognizer;  
4.        public SearchLuisRecognizer(IConfiguration configuration)  
5.        {  
6.            var luisIsConfigured = !string.IsNullOrEmpty(configuration["LuisAppId"]) && !string.IsNullOrEmpty(configuration["LuisAPIKey"]) && !string.IsNullOrEmpty(configuration["LuisAPIHostName"]);  
7.            if (luisIsConfigured)  
8.            {  
9.                var luisApplication = new LuisApplication(  
10.                    configuration["LuisAppId"],  
11.                    configuration["LuisAPIKey"],  
12.                    "https://" + configuration["LuisAPIHostName"]);  
13.   
14.                var recognizerOptions = new LuisRecognizerOptionsV3(luisApplication)  
15.                {  
16.                    PredictionOptions = new Microsoft.Bot.Builder.AI.LuisV3.LuisPredictionOptions  
17.                    {  
18.                        IncludeInstanceData = true,  
19.                    }  
20.                };  
21.   
22.                _recognizer = new LuisRecognizer(recognizerOptions);  
23.            }  
24.        }  
25.   
26.        public virtual bool IsConfigured => _recognizer != null;  
27.   
28.        public virtual async Task<RecognizerResult> RecognizeAsync(ITurnContext turnContext, CancellationToken cancellationToken)  
29.            => await _recognizer.RecognizeAsync(turnContext, cancellationToken);  
30.   
31.        public virtual async Task<T> RecognizeAsync<T>(ITurnContext turnContext, CancellationToken cancellationToken)  
32.            where T : IRecognizerConvert, new()  
33.            => await _recognizer.RecognizeAsync<T>(turnContext, cancellationToken);  
34.    }  

Step 5

Add Main Dialog and define water fall model to call Luis and QnA Maker.

MainDialog will recognize the intention in the phrases.

1. Create folder name i.e. Dialogs
2. Add new file i.e. MainDialogs.cs  

1. private readonly SearchLuisRecognizer _luisRecognizer;  
2.        public QnAMaker SearchBotQnA { get; private set; }  
3.   
4.        //string messageText = "What can I help you with today?";  
5.        // Dependency injection uses this constructor to instantiate MainDialog  
6.        public MainDialogs(SearchLuisRecognizer luisRecognizer, QnAMakerEndpoint endpoint)  
7.            : base(nameof(MainDialogs))  
8.        {  
9.            _luisRecognizer = luisRecognizer;  
10.            SearchBotQnA = new QnAMaker(endpoint);  
11.   
12.            AddDialog(new TextPrompt(nameof(TextPrompt)));  
13.            AddDialog(new WaterfallDialog(nameof(WaterfallDialog), new WaterfallStep[]  
14.            {  
15.                IntroStepAsync,  
16.                ActStepAsync,  
17.                FinalStepAsync,  
18.            }));  
19.   
20.            // The initial child Dialog to run.  
21.            InitialDialogId = nameof(WaterfallDialog);  
22.        }  

Main Dialog is used to define the Luis Connection, QnAMaker Connection and Waterfall Dialog Model used for implementing sequencial conversation flow.

1. IntroStepAsync ->  It's used to check Luis connection and move forward. 

1. private async Task<DialogTurnResult> IntroStepAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)  
2.        {  
3.            if (!_luisRecognizer.IsConfigured)  
4.            {  
5.                return await stepContext.NextAsync(null, cancellationToken);  
6.            }  
7.   
8.            return await stepContext.PromptAsync(nameof(TextPrompt), new PromptOptions { }, cancellationToken);  
9.        }   

2. ActStepAsync -> Used to define the intent against phrase. Based on intention, calls respective method to execute.

1. private async Task<DialogTurnResult> ActStepAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)    
2.         {    
3.     
4.             var luisResult = await _luisRecognizer.RecognizeAsync<ContentSearchLuisRecognizer>(stepContext.Context, cancellationToken);    
5.             APICaller aPICaller = new APICaller();    
6.             switch (luisResult.TopIntent().intent)    
7.             {    
8.                    
9.     
10.                 case ContentSearchLuisRecognizer.Intent.DocumentSearch:    
11.                     string documentName = luisResult.DocumentNameEntities != null ? luisResult.DocumentNameEntities : "";    
12.                     string documents = aPICaller.GetDocument(documentName);    
13.                     var docAttachments = DocumentCard.GetDocumentCard(documents);    
14.                     await stepContext.Context.SendActivityAsync(MessageFactory.Carousel(docAttachments), cancellationToken);    
15.                     break;    
16.     
17.                 default:    
18.     
19.                     var results = await SearchBotQnA.GetAnswersAsync(stepContext.Context);    
20.                     if (results.Length > 0)    
21.                     {    
22.                         var answer = results.First().Answer;    
23.                         await stepContext.Context.SendActivityAsync(MessageFactory.Text(answer), cancellationToken);    
24.                     }    
25.                     else    
26.                     {    
27.                         string documentNames = aPICaller.GetDocument(stepContext.Context.Activity.Text);    
28.                         if (!String.IsNullOrEmpty(documentNames) && documentNames != "[]")    
29.                         {    
30.                             var documentAttachments = DocumentCard.GetDocumentCard(documentNames);    
31.                             await stepContext.Context.SendActivityAsync(MessageFactory.Carousel(documentAttachments), cancellationToken);    
32.                         }    
33.                         else    
34.                         {    
35.                             Activity reply = ((Activity)stepContext.Context.Activity).CreateReply();    
36.                             reply.Text = $"😢 **Sorry!!! I found nothing** \n\n Please try to rephrase your query.";    
37.                             await stepContext.Context.SendActivityAsync(reply);    
38.                         }    
39.                     }    
40.                     break;    
41.             }    
42.     
43.             return await stepContext.NextAsync(null, cancellationToken);    
44.         }   

3. FinalStepAsync ->  Used to initiate the conversation flow again.

1. private async Task<DialogTurnResult> FinalStepAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)  
2. {  
3.   
4. return await stepContext.ReplaceDialogAsync(InitialDialogId, null, cancellationToken);  
5. }  

Step 6 - Call Custom API 

API will return data from SharePoint Online into Json Format. As of now I used anonymous api so it didn't generate access token. It's always a best practice to use user token and access token to make api and connection secure.

• Create a folder name Services
• Create a file "APICaller.cs"

1. public string GetDocument(string qry)  
2.        {  
3.            HttpClient httpClient = new HttpClient();  
4.            var baseUrl = "http://botapi.azurewebsites.net/";  
5.            var route = "api/document?query=" + qry;  
6.            httpClient.BaseAddress = new Uri(baseUrl);  
7.            httpClient.DefaultRequestHeaders.Accept.Clear();  
8.            httpClient.DefaultRequestHeaders.Accept.Add(  
9.            new MediaTypeWithQualityHeaderValue("application/json"));  
10.   
11.            string responseString = string.Empty;  
12.            var response = httpClient.GetAsync(route).Result;  
13.            if (response.IsSuccessStatusCode)  
14.            {  
15.                responseString = response.Content.ReadAsStringAsync().Result;  
16.            }  
17.            return responseString;  
18.        }  

Step 7

Define Adaptive; i.e. Document Card, based on api response.

Adaptive; i.e. Document card, will be designed to return api response into card format and the same is going to attach to carousel.

Create Folder Name: Cards

Create file name : DocumentCards.cs 

1. public static List<Attachment> GetDocumentCard(string dataSet)  
2.         {  
3.             var attachments = new List<Attachment>();  
4.             List<DocumentDto> documentDtos = JsonConvert.DeserializeObject<List<DocumentDto>>(dataSet);  
5.             foreach (DocumentDto info in documentDtos)  
6.             {  
7.                 string summary = HtmlToPlainText(info.Summary);  
8.                 string documentIcon = GetFileIcon(info.DocumentPath);  
9.                 //Icon fileIcon=Icon.ExtractAssociatedIcon("<fullPath>");  
10.   
11.                 var card = new AdaptiveCard("1.2");  
12.                 List<AdaptiveElement> AdaptiveElements = new List<AdaptiveElement>  
13.                 {  
14.                      new AdaptiveColumnSet()  
15.                      {  
16.                         Columns =new List<AdaptiveColumn>()  
17.                         {  
18.                             new AdaptiveColumn()  
19.                                 {  
20.                                     Width="100px",  
21.                                     Items = new List<AdaptiveElement>()  
22.                                     {  
23.                                           
24.                                         new AdaptiveImage(documentIcon)  
25.                                         {  
26.                                            Id="documentIcon",  
27.                                            Size = AdaptiveImageSize.Medium,  
28.                                            Style = AdaptiveImageStyle.Default,  
29.                                         },  
30.                                     }  
31.                                 },  
32.                             new AdaptiveColumn()  
33.                             {  
34.                                     Width=AdaptiveColumnWidth.Stretch,  
35.                                     Items = new List<AdaptiveElement>()  
36.                                     {  
37.                                          new AdaptiveTextBlock()  
38.                                          {  
39.                                             Id="title",  
40.                                             Text = info.Title,  
41.                                             Size = AdaptiveTextSize.Medium,  
42.                                             Weight = AdaptiveTextWeight.Bolder,  
43.                                             HorizontalAlignment =AdaptiveHorizontalAlignment.Left,  
44.                                          },  
45.                                          new AdaptiveTextBlock()  
46.                                          {  
47.                                            Id="author",  
48.                                            Text ="✍ " +info.Author,  
49.                                            Weight = AdaptiveTextWeight.Lighter,  
50.                                            Size=AdaptiveTextSize.Small,  
51.                                            Color=AdaptiveTextColor.Dark,  
52.                                            Wrap=true,  
53.                                          },  
54.                                          new AdaptiveTextBlock()  
55.                                          {  
56.                                            Id="date",  
57.                                            Text = "🗓 "+info.CreatedDateTime,  
58.                                            Weight = AdaptiveTextWeight.Lighter,  
59.                                            Color=AdaptiveTextColor.Dark,  
60.                                            Size=AdaptiveTextSize.Small,  
61.                                            Wrap=true,  
62.                                          },  
63.                                     }  
64.                             }  
65.                         }  
66.                      },  
67.                      new AdaptiveColumnSet()  
68.                      {  
69.                             Columns =new List<AdaptiveColumn>()  
70.                             {  
71.                                 new AdaptiveColumn()  
72.                                 {  
73.                                      
74.                                     Items = new List<AdaptiveElement>()  
75.                                     {  
76.                                         new AdaptiveTextBlock()  
77.                                         {  
78.                                            Id="summary",  
79.                                            Text = summary,  
80.                                            Weight = AdaptiveTextWeight.Default,  
81.                                            Size=AdaptiveTextSize.Small,  
82.                                            Color=AdaptiveTextColor.Dark,  
83.                                            Wrap=true,  
84.                                         },  
85.   
86.                                     }  
87.   
88.                                 }  
89.                             }  
90.                      },  
91.                      new AdaptiveActionSet()  
92.                      {  
93.                         Actions = new List<AdaptiveAction>(){  
94.                            new AdaptiveOpenUrlAction()  
95.                            {  
96.                               Id="open_url_action",  
97.                               Title = "View",  
98.                               UrlString = info.DocumentPath  
99.                            }  
100.                         }  
101.                      }  
102.                 };  
103.                   
104.                 card.Body = AdaptiveElements;  
105.                 Attachment attachment = new Attachment()  
106.                 {  
107.                     ContentType = AdaptiveCard.ContentType,  
108.                     Content = card  
109.                 };  
110.                 attachments.Add(attachment);  
111.   
112.             }  
113.             return attachments;  
114.         }  

Step 8

Create search bot file and call MainDialog file

Add new file searchbot.cs into bot folder. It has two main functions.

OnMemberAddedAsync

1. protected override async Task OnMembersAddedAsync(IList<ChannelAccount> membersAdded, ITurnContext<IConversationUpdateActivity> turnContext, CancellationToken cancellationToken)  
2.        {  
3.            foreach (var member in membersAdded ?? Array.Empty<ChannelAccount>())  
4.            {  
5.                if (member.Id != turnContext.Activity.Recipient.Id)  
6.                {  
7.                    //if (turnContext.Activity.MembersAdded[0].Name == "USER_NAME")  
8.                    //{  
9.                    Activity reply = ((Activity)turnContext.Activity).CreateReply();  
10.                    reply.Text = $" 😀 **Hi, I am Virtual Assistant!!** \n\n I am here to assist you.";  
11.                    await turnContext.SendActivityAsync(reply, cancellationToken);  
12.                    //}  
13.                }  
14.            }  
15.            await Dialog.RunAsync(turnContext, ConversationState.CreateProperty<DialogState>(nameof(DialogState)), cancellationToken);  
16.        }  

 OnTeamMemberAddedAsync

1. protected override async Task OnTeamsMembersAddedAsync(IList<TeamsChannelAccount> membersAdded, TeamInfo teamInfo, ITurnContext<IConversationUpdateActivity> turnContext, CancellationToken cancellationToken)  
2.        {  
3.            foreach (var teamMember in membersAdded)  
4.            {  
5.                Activity reply = ((Activity)turnContext.Activity).CreateReply();  
6.                reply.Text = $" 😀 **Hi, I am Virtual Assistant!!** \n\n I am here to assist you.";  
7.                await turnContext.SendActivityAsync(reply, cancellationToken);  
8.            }  
9.        }  

Step 9

Call Search Bot.cs file into startup.cs file,

1. public void ConfigureServices(IServiceCollection services)  
2.        {  
3.            services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);  
4.   
5.            // Create the Bot Framework Adapter with error handling enabled.  
6.            services.AddSingleton<IBotFrameworkHttpAdapter, AdapterWithErrorHandler>();  
7.   
8.            // Create the storage we'll be using for User and Conversation state. (Memory is great for testing purposes.)  
9.            services.AddSingleton<IStorage, MemoryStorage>();  
10.   
11.            // Create the User state. (Used in this bot's Dialog implementation.)  
12.            services.AddSingleton<UserState>();  
13.   
14.            // Create the Conversation state. (Used by the Dialog system itself.)  
15.            services.AddSingleton<ConversationState>();  
16.   
17.            services.AddSingleton<SearchLuisRecognizer>();  
18.   
19.   
20.            // the dialog that will be run by the bot.  
21.            services.AddSingleton<MainDialogs>();  
22.   
23.            services.AddSingleton(new QnAMakerEndpoint  
24.            {  
25.                KnowledgeBaseId = Configuration.GetValue<string>($"QnAKnowledgebaseId"),  
26.                EndpointKey = Configuration.GetValue<string>($"QnAAuthKey"),  
27.                Host = Configuration.GetValue<string>($"QnAEndpointHostName")  
28.            });  
29.   
30.            // Create the bot as a transient. In this case the ASP Controller is expecting an IBot.  
31.            services.AddTransient<IBot, SearchBot>();  
32.        }  

Step 10

Test, Build and Run the solution to test into bot emulator

Press F5 to test locally; i.e. using Bot Emulator,

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article.