Let's say we have a well-established solution in Visual Studio 2008, using WSPBuilder to bundle it up into a package. It has a handful of features and a whole whack of assets to deploy (.webpart, .xsl, .js, images, site columns, content types, etc.) to both site collection libraries and the 12 hive.
What would you suggest the approach should be for going to 2010?
I have an odd feeling that SPI folders (as lovely as they are for managing Module Elements) are going to get pretty busy and hard to manage in a VS2010 solution with several features in the one project. So, would you still use WSPBuilder, and have your 14/TEMPLATE/FEATURES/etc folder hierarchy in the project?
Also, I horrendously dislike the "Solution" and "Feature" design surfaces, especially so when you have a VS2010 Solution with several projects, each with a handful of features.
Anyone else have experience with medium-sized-and-up VS2010 solutions yet?
Also: the assumption is that the 2010 solution will be deployed to the Farm.