Design experience for installing cmdlets as CurrentUser

[markcowl]

Description

Need to decide what the experience should be for installing as CurrentUser and how this mixes with installing for the machine scope.

We need to avoid conflicts between machine-scope cmdlets and current user scope cmdlets.

We could

• Always install as CurrentUser
• Always install in the machien scope
• Allow users to choose, but enforce the choice once made
• Allow users to choose and find a way for the default profile to make sense in these situations

[viananth]

This issue was moved to Azure#3301