SP Permissions Under SQL Server 2005

I am just migrating to SQL Server 2005 and I am having difficulty
figuring out how to do some tasks that were easy under SQL Server 2000.
Specifically, I am not sure about object permissions.

(This is
what I did for SQL Server 2000) For database access by my web
application, I added a SQL login for the IIS_WPG group. I then added a
database user (name ASPNET) associated with this database login and
give it only datareader and datawriter privileges. I would then
'double-click' the user, which would bring up the list of securable
objects. I would then click the 'execute' permission for all of the
user-created stored procedures. [done]

For SQL Server 2005, I am
not quite sure what to do. It seems to me (based on what I see after
importing the tables), that a schema should be used, but I do not see
any explicit permissions in the schema. On the other hand, if I select
each stored procedure and look at its properties, I can see that the
ASPNET user has execute permission.

It seems inconceivable that
the only way to configure permissions is to modify each SP by hand.
This would take more than 10 times as long as the SQL Server 2000
method of assigning permissions.

So, my question is this:
How
can permissions be assigned 'wholesale'? (i.e., some method akin to the
SQL Server 2000 method that does not require setting permissions on
each individual object individually.)

Of course, if you care to suggest a better way to do this, I'd love to hear it!

Thank you.