'Windows' is not a member of 'Microsoft'
-
A productive system has crashed several times yesterday. The fastest way to limit this problem was to create a project group of the source code of the referenced components and debug them (remember: productive system => no test system available). When I "deeply relaxed" added the projects to a group, my IDE decided to comment this: 115 Errors: 'Windows' is not a member of 'Microsoft' After double-clicking the first message, the Visual Studio 2010 chose that it would probably be no more a member of Windows and crashed accordingly. I love days like this.
-
A productive system has crashed several times yesterday. The fastest way to limit this problem was to create a project group of the source code of the referenced components and debug them (remember: productive system => no test system available). When I "deeply relaxed" added the projects to a group, my IDE decided to comment this: 115 Errors: 'Windows' is not a member of 'Microsoft' After double-clicking the first message, the Visual Studio 2010 chose that it would probably be no more a member of Windows and crashed accordingly. I love days like this.
I've seen some strange errors from VS, but I have never seen this one. I think it was a reference mix up of some sort. But, who knows? Has VS become sentient? :~
public class SysAdmin : Employee
{public override void DoWork(IWorkItem workItem) { if (workItem.User.Type == UserType.NoLearn){ throw new NoIWillNotFixYourComputerException(new Luser(workItem.User)); }else{ base.DoWork(workItem); } }
}
-
I've seen some strange errors from VS, but I have never seen this one. I think it was a reference mix up of some sort. But, who knows? Has VS become sentient? :~
public class SysAdmin : Employee
{public override void DoWork(IWorkItem workItem) { if (workItem.User.Type == UserType.NoLearn){ throw new NoIWillNotFixYourComputerException(new Luser(workItem.User)); }else{ base.DoWork(workItem); } }
}
Yes, I think it was a reference mix up. I just started to remove the file references and include the corresponding source projects of the removed DLLs. I lost my overview as VS starts to gripe that source component A cannot call compiled component B. I clicked on recompile and the result was a list of 115 errors, where the first five or six (all I could see at once) messages where the mentioned one. Situation comedy, but that day I was not in the mood to laugh ;)