GUI's are limiting, but there's no need to throw the baby out with the bath water. If developers want to add more functionality via a CLI, that's great. But to simultaneously REMOVE functionality from a GUI isn't my idea of progress.
IIS 7 let's you configure IP restrictions at the site level via the GUI. Why not at lower levels, as was possible with prior versions of IIS? I just don't see how removing functionality can be considered an improvement. John -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Wednesday, August 17, 2011 2:14 PM To: NT System Admin Issues Subject: Re: Using IP address restrictions in IIS 7 On Wed, Aug 17, 2011 at 08:13, John Hornbuckle <[email protected]> wrote: > Good heavens. That’s progress? Yes, absolutely. > The IIS team must’ve taken tips from the Exchange team on removing > previous GUI features and making users work more with config files and > command prompts. That's a good thing. GUIs are terribly limiting, and don't usually allow automation, revision control, etc. <snip> Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
