This is a real pain and it looks like a known issue.

See the link below for a explanation and work around. Not sure if the new service pack 1 for VS2008 will fix.

http://forums.asp.net/p/1002747/1324414.aspx

Se entry 06-19-2007 by Mimix at 6:27pm for the simplest work around.