This has involved lots of hand-coding in my experience, and i've done a bit of work to automate the process.
SQL Metal Stored Procedure Names
Firstly i found that SqlMetal no longer removes the underscore characters with Orcas Beta 1, which typically leaves hundreds of compile errors that are time consuming to fix by hand. Visual Studio can replace these using regular expressions with a little preparation, depending on your naming conventions. All my stored procedures are of the form
TableName_SELECT_Xyz, or
TableName_UPDATE_Xyz etc. I found i could fix all the compile errors by scanning for
{[a-zA-Z]}SELECT and replacing with
\1_SELECT to cover the left hand side underscore, and similarly you can do the reverse to insert a right hand side underscore if there is an a-z character immediately after the SELECT (if there are brackets or punctuation then you probably don't want to insert an underscore). I ran this for SELECT INSERT UPDATE and DELETE, 2 times each. takes a minute but saved me a lot of time.
More info on
using regular expressions within Visual Studio.
Adding Namespaces when upgrading from a 'web site' project.
The Orcas 'convert to web application' facility is very good i must say. it actually works. no more half baked designer.cs files or unsynchronised control members in code behind etc. But it doesn't add namespaces to your aspx or code-behind files, which is a real pain if you have 50+ aspx pages in your site, and several projects to convert. I wrote a simple winform app to attempt to relieve the hand-coding required. it also takes out a few of the retired namespaces from MayCTP and adds in the Beta 1 / Linq replacements. You can customise the namespaces to add/remove, and specify the new namespace to add to the web site aspx + code behind files. it comes with no warranty and may screw up your files so always take a backup before running!
the idea is that you run the tool on your web site project directory, then create a blank WAP project in Orcas and copy in the files. Then run the Orcas 'convert to WAP' command on the project root. if it is successful you will see each aspx page expanded in the project tree. some pages don't convert because of compile errors with custom controls etc. i usually found it took a bit of working through the compile errors first before some of the pages would successfully convert to the WAP format. here's a screenshot and the code if anyone wants to run it:
Source code + executable (zip 36 Kb)