<p>How does the new Microsoft asp.net mvc implementation handle partitioning your application - for example:</p>

<pre><code>--index.aspx
--about.aspx
--contact.aspx
--/feature1
--/feature1/subfeature/action
--/feature2/subfeature/action
</code></pre>

<p>I guess what I am trying to say is that it seems everything has to go into the root of the views/controllers folders which could get unwieldy when working on a project that if built with web forms might have lots and lots of folders and sub-folders to partition the application.</p>

<p>I think I get the MVC model and I like the look of it compared to web forms but still getting my head round how you would build a large project in practice.</p>

There isn't any issues with organizing your controllers.  You just need to setup the routes to take the organization into consideration.  The problem you will run into is finding the view for the controller, since you changed the convention.  There isn't any built in functionality for it yet, but it is easy to create a work around yourself with a ActionFilterAttribute and a custom view locator that inherits off ViewLocator.  Then when creating your controller, you just specify what ViewLocator to use, so the controller knows how to find the view.  I can post some code if needed.
This method kind of goes along with some advice I gave another person for separating their views out for a portal using ASP.NET MVC.  Here is the
link to the question
as a reference.