Port File Staging to VS17

[matthchr]

Description

---

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

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

[darylmsft]

ya I used the name and datetime stuff for a purpose... not just to provide uniqueness. and the sleep probably made "uniqueLetsHope" provably "unique". If there is a way of keeping this I'd appreciate it... yes your code is simpler but its harder to use.

[matthchr]

I updated this to use a time (for ordering) and a GUID for uniqueness at the end. Plus added some max length truncation where we will truncate the container name if it's too long.

That saves us the Thread (which we can't use) but I think maintains the original behavior.

[darylmsft]

probably no longer linked... the "link" referred to the vs feature.

[matthchr]

@shahabhijeet - This can be merged now (if CI passes)

[shahabhijeet]

@matthchr can you resolve the conflicts and push.

[matthchr]

@shahabhijeet Done