It looks like that may be a bug in VS that was never actually fixed in VS.NET 2003.

http://connect.microsoft.com/VisualS...dbackID=237556