The implicit declarative binding syntax (phew, that's a mouthfull) meta:resourcekey can be used to localize ASP.NET Controls in a much more tidy manner than using it's explicit counterpart. Basically, instead of doing stuff like:

<asp:Button
    ID="_submitBtn"
    runaT="server"
    Text='<%$ resources: Buttons, SubmitButton.Text %>'
    ToolTip='<%$ resources: Buttons, SubmitButton.Tooltip %>'
    OnClick="Submit" />

you can get away with the much more elegant:

<asp:Button
    ID="_submitBtn"
    runaT="server"
    meta:resourcekey='SubmitButton' />

which then will automatically look for SubmitButton.Text and SubmitButton.ToolTip (and any other resource-able properties) in local resource files.

However, the neat trick is that with Visual Studio 2005, you can just forget all about localization when you're writing the markup. Yep, just go ahead and hard-code those literals right in there. Afterwards, simply hit 'Generate Local Resource' on the Tools menu, and VS will do just that, moving all your hard-coded literals into a resource file.

The only downside is that the 'Generate' function is only available in Design Mode. Which, if you're like me and like to hand-type your markup, will probably find a bit annoying. Hopefully this should get sorted in Orcas however :)