View Complete Thread
  • Re: Application pools

    Jul 08, 2008 03:55 AM|sergeia|LINK

    Well, we have more than hundred schematized collections in configuration. We could create enough specific cmdlets to cover all various kinds of data, but it will be at least three hundred commands with different parameters for get/set/new operations, then unknown number of commands for more specific operations like setting app to app pool. I doubt users will be happy with this amount of commands. Therefore we decided to be conservative for now and limit number of helper commands to the bare minimum, as we understand it. We are looking for users feedback to decide, is it right set of commands, or it should be extended/changed.

    We expect that little by little customers will start using standard commands from provider. As soon as you are familiar with namespace path, you could easily figure out the path to any object you want, you could navigate to this location and do various things without passing path to commands, or passing dot, just like in file system provider, or in the registry provider. You also using the same commands: get-item, set-item, get-itemproperty, etc. This is whole idea of providers in PowerShell: limit number of commands you have to memorize.