Generating LUIS SDK for updated specification file

[mohabghanem]

Description

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• Please add REST spec PR link to the SDK PR
  Changing Entity Index to integer azure-rest-api-specs#3456
  [Cognitive Services] Update endpoint URL template for LUIS. azure-rest-api-specs#3492

• I have read the contribution guidelines.

• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[dsgouda]

@mohabghanem please link the related REST spec PR

[dsgouda]

This is a breaking change. Please bump the major version number here Also, update the PackageReleaseNotes accordingly

[dsgouda]

Please update the AssemblyInfo here based on these version updates.

[mohabghanem]

@dsgouda where to update the PackageReleaseNotes?

[dsgouda]

Please update the AssemblyFileVersion too

[dsgouda]

Please update the PackageReleaseNotes here

[mohabghanem]

@dsgouda what should be in the PackageReleaseNotes ?

[dsgouda]

What changes you are planning to release in this version. Please check the
"Changes in this release:" section

[mohabghanem]

@dsgouda please review

[dsgouda]

Looks great apart from a minor comment.

[dsgouda]

PackageReleaseNotes must be updated

[mohabghanem]

@dsgouda I edited the package release notes. But I do not know what else to add, because the only change in this PR is customizing the endpoint

[dsgouda]

LGTM

[dsgouda]

Will merge on CIs passing

[yangyuan]

Suggest to use below description: (The reason is we may not change Azure Portal quickly, so better in here (as well as documents) we emphasize that the Endpoint should only contains protocol and hostname)

1. Supported customizing service endpoints by assigning the endpoint string to LUISRuntimeClient.Endpoint. The endpoint string can be found on Azure Portal, it should contain only protocol and hostname, for example: https://westus.api.cognitive.microsoft.com.
   2....

[mohabghanem]

@dsgouda @yangyuan I get the build error 'Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure' from the automated build. However builds and tests ran successfully on my local machine before pushing. Any clues on what may be causing this problem it?

[yangyuan]

TTypo :)

[yangyuan]

For Authoring. The client name should be LUISAuthoringClient

[yangyuan]

@mohabghanem I have no clue about that build error.
Can you try rebase to latest Azure:psSdkJson6? If CI do merge before build, then the error might be cause by recent psSdkJson6 changes.

[mohabghanem]

@yangyuan @dsgouda The tests are now passing. Please review.

[dsgouda]

LGTM