This article lists the aliasses you can use in visual studio when searching with a regular expression.

http://msdn.microsoft.com/en-us/library/2k3te2cs(VS.80,ide).aspx

For example  if you want to find all guids in your solution

• CTRL-SHFT-F (find in files)
• Entire Solution
• check the Use Regular Expressions box
• type in the find box :h^8-:h^4-:h^4-:h^4-:h^12
• go

Article about how to add a "Get PublicKeyToken" menu item in Visual Studio

http://blogs.msdn.com/b/miah/archive/2008/02/19/visual-studio-tip-get-public-key-token-for-a-stong-named-assembly.aspx

Basic steps:

• Tools --> External tools..
• Title: Get PublicKeyToken
• Command: C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\SN.exe
• Arguments: -T $(TargetPath)
• Check Options: Use Output window

Make sure you build your project before using this new tool.
I love this, and think it should be added on every developers machine.

I've been using the beta an RC version of Visual Studio 2010 for a while.
Yesterday VS2010 was offically released.

Take a look if there is a launchparty near your location.

http://www.microsoft.com/visualstudio/en-us/visual-studio-events

Enjoy.

Together with 3 colleagues from QNH Business Integration I am currently finishing implementing a already NEN 2082 certified project based on SharePoint 2010.
When SharePoint 2010 hits RTM there will be another audit for this version of SharePoint, because currently the pre release version has been certified.

NEN 2082 is a Dutch standard which is similar the DoD5015 and MoReq standards.

This project was done for the Gemeente Nieuwegein, which is a Dutch local Government.

For this project we have also been nominated for the “Innovation of the year” award:

More information (Dutch)

My colleagues at QNH:

• Jeffrey Tummers - http://blog.thumnet.com
• Alexander Ketelaar – http://sharepoint2010.nl
• Robert Sep

Last week, I removed my VS2010 beta installation and installed VS2010 RC. The RC is much more stable, and as a bonus renaming a feature in a SP2010 project now works.
We have been building lots of features lately, and I was very pleasantly surprised to see this bug already fixed.