fix: update framework and package version in template botproject

[VanyLaw]

Description

Cause: The original version package reference was remove from repo, and caused sample bot project build failed.
Solution:

• update package reference in template botproject
• update schema to match the new version sdk
• change the script to throw error sothat the process can catch it.
• update netcoreapp form 2.1 to 3.1

And @alanlong9278 will help to fix the UI to match schema change(number to expression).

FYI. those sdk main changes:

1. New recognizers set:

• Microsoft.AdaptiveCardRecognizer
• Microsoft.QnAMakerRecognizer
• Microsoft.CrossTrainedRecognizerSet
• Microsoft.RecognizerSet
• Microsoft.OnChooseIntent (trigger)
• Microsoft.OnQnAMatch (trigger)

2. FormDialog related triggers and actions

• Microsoft.Ask
• Microsoft.OnAssignEntity
• Microsoft.OnChooseEntity
• Microsoft.OnChooseProperty
• Microsoft.OnClearProperty

3. Other new actions and triggers

• Microsoft.GotoAction
• Microsoft.ContinueLoop
• Microsoft.BreakLoop
• Microsoft.UpdateActivity
• Microsoft.DeleteActivity
• Microsoft.GetActivityMembers
• Microsoft.GetConversationMembers
• Microsoft.SignOutUser
• Microsoft.OnEndOfActions

4. minor updates

• Add disabled property on actions
• Change includeActivity to activityProcessed (only this one have a breaking change, but we don't enabled it in Composer UX yet, so this is fine.)

There is only one breaking change in the schema, others are all additions.

Task Item

fixes #1927

Screenshots

[github-actions]

Coverage remained the same at 42.425% when pulling 972202c on wenyluo/test into 983b29e on master.

[InDieTasten]

I've tried this on my local environment, and it did not resolve the issue.

I find it strange, that this is still running on target framework netcoreapp2.1. Wouldn't it make sense, to update to netcoreapp2.2 ?

EDIT: This resolves the issue, but I was getting build errors from a configured nuget source that failed. It's kind of annoying though, that the build errors can only be validated from running the build manually, and that composer wouldn't log the build errors to console. Makes reproducing and fixing a bit difficult.

[aalmada]

The documentation does specify .NET Core SDK 2.2 as prerequisite and not 2.1.

[VanyLaw]

I've tried this on my local environment, and it did not resolve the issue.

I find it strange, that this is still running on target framework netcoreapp2.1. Wouldn't it make sense, to update to netcoreapp2.2 ?

EDIT: This resolves the issue, but I was getting build errors from a configured nuget source that failed. It's kind of annoying though, that the build errors can only be validated from running the build manually, and that composer wouldn't log the build errors to console. Makes reproducing and fixing a bit difficult.

If you want to update to netcoreapp2.2, you need to change the package references and add some extra reference, like this:

I am not sure will it cause other compatible issues. Need to investigate it. But .net core sdk 2.2 should compatible with netcoreapp2.1.

And I modify the script to get more build error message.

[aalmada]

I applied the changes from this PR to my local version and I confirm that it fixes the 'Start Bot' issue.

[boydc2014]

@VanyLaw Can we take this chance to upgrade to 3.1 if possible, 3.1 is a LTS version, and i hope that could save us efforts a lot of time.

[luhan2017]

@VanyLaw, could you also update the sdk.schema in the template and Composer folder, and test whether the template bots work correctly?

[VanyLaw]

@VanyLaw, could you also update the sdk.schema in the template and Composer folder, and test whether the template bots work correctly?

Some sample bots will throw "must be an expression" error. Seems like number need to be changed to expression after schema updated. According to @alanlong9278 , It will cause hige UI change. Maybe we need a discussion about it.