mystical reference problem

I am not sure whether this is the best forum to ask this question, but here goes:

In a solution I have a project that references Microsoft.ApplicationsBlocks.Data and Microsoft.ApplicationBlocks.ExceptionMangement. The dlls are lying in a local directory at the same place where I have my projects. The dlls are also checked into Sourcesafe because I am working with others and we want to be sure that we reference the same versions.

Everything has worked fine for weeks. But today I suddenly got the error "Error 90 The type or namespace name 'ApplicationBlocks' does not exist in the namespace 'Microsoft' (are you missing an assembly reference ) C:\VSS\V2Light.root\V2Light\GUI\SqlHelper.cs 11 17 V2Light". In the file SqlHelper I have the directive "using Microsoft.ApplicationBlocks.Data;".

As you all probably know, this ordinarily means that my references are not up to date, but checking them everything seems fine. They point to det same dlls they always have done, and the dlls still exist. I tried removing the references and adding them again, but that did not help. Then I noticed something strange. The dlls in sourcesafe are the same versions as the ones I have and they have only been checked in once. The versions correspond with the versions stated in my project file (after removing and adding the references again), but they do not correspond with the versions stated in earlier versions of the project file. This seems to me very strange. How could it have worked before when the references seemingly were wrong, but it does not work now when they are correct

Frankly, I am very confused and I am not able to resolve the problem. I have tried rebooting. I have also tried removing the whole project causing the trouble from my disk and getting it fresh from SourceSafe, but the problem won't go away. I am sure there is an easy explanation and that there is something I am overlooking. Does anybody have a clue about how I should resolve this

Answer this question

mystical reference problem

dhooger
Well, I found the solution to this problem. What happened was that the file that caused the problem somehow had been included in another project in the solution. Since I "knew" which project the file was in, I did not notice that and checked the references for this project which of course were OK. So it had a natural explanation, however, I am unable to explain how the file came to be included in the other project, as I am 100% sure that I did not include it there myself...
mystical reference problem

Answer this question