Regenerate PolicyInsights based on latest spec for 2018-04-04 (GA version)

[bulentelmaci]

• Regenerate PolicyInsights based on latest spec for 2018-04-04
• Change client, assembly and file versions to 1.0.0; remove -preview
• Rerecord tests

Swagger spec PR: Azure/azure-rest-api-specs#2929

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
• 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]

Please create a generate.ps1 similar to this and regenerate the code

Please run
msbuild build.proj /t:build /p:Scope=SDKs\PolicyInsights

[dsgouda]

Please use Version instead of VersionPrefix

[dsgouda]

LGTM

[dsgouda]

Will merge on CIs passing

[bulentelmaci]

@dsgouda Thanks! How long after the merge should I expect the package to be available at nuget.org?

[dsgouda]

@bulentelmaci You will have to publish the nuget package yourself, instructions can be found here

[bulentelmaci]

@dsgouda Thanks! I assume I can just do the Publish job which will sign and publish (i.e. no need to run the sign job separately beforehand)?

[dsgouda]

Yes, that's correct. Please reach out to our alias in case you run into any publish issues.