> Yes, it looks like the same problem as before. I shall look into this > simultaneously too. I did check in a fix yesterday for this bug. Basically we had two code blobcs that are remarkably similar, but in two different places that got out of sync (SimpleName.SimpleNameResolve and MemberLookup.DoResolve). miguel