Package as Azure.Core and provide an extensibility mechanism for packages outside the core

[markcowl]

Package SDKs in a Core package including

• Authentication
• Resource Management
• KeyVault
• Storage
• Network
• Compute
• AppService

including all supported API versions and profiles. This means profile clients would have all these operations by default.

Include an extensibility mechanism for packages outside the core adding themselves to the client. A sample of this kind of mechanism using Extension methods is shown here: https://github.com/Azure/azure-sdk-for-net/pull/2472/files

[devigned]

Would this mean someone would need to add a using statement for a given set of profile operations if they added a package from outside of core?

For example, I'm currently using the core package at profile 2017_01_31. I add CosmosDB functionality by referencing that package and then adding

using Microsoft.Azure.Management.CosmosDB.Profile._2017_01_31

or something similar?