wireless configuration: Incorrect MFC DLL version installed

several hours came and went banging my head against the wall after getting this error msg.
all started when i decided to finally uninstall vs 2003 and i guess it removed some dlls that i shouldn't have to...
i'm fairly pissed off right now so lets skip to the solution:
after deciding not reinstall windows because of this, at least i decided to put xp sp3, although i didn't really needed to...anyway this didn't help =/
after absurdly many hours of google search i came to this page - http://www.techsupportforum.com/microsoft-support/windows-xp-support/169616-incorrect-mfc-dll-version-installed-system.html
and this hint led me to open my services tab, kill the fukking 'tray service' and write this blog, quite sardonically if i may add...
damn software :)

on the market

ok, so first interview came and went - what conclusions can be made?
the interviewer asked me about App domains
I was never really interested in those, said one of the benefits is the version control, gotta check this.
On multithreading...should i read more about some test cases? i spoke of some of my experience with it, its funny that when you have to talk about it its sometimes hard to elaborate on the subject...
WCF, now thats a weak point - i have experience with .Net remoting, but so many years ago I could hardly say any details, but it felt bad when the guy asked me had I had even read about WCF and I said "err...no" - gotta take care of this too, i guess
he also asked me if i had any experience with MS SQL Server, but when i started talking and mentioned the two certifications i have in this he seemed satisfied enough.
hmm...what else was there...

oh but of course - Web services - the last positions had me implementing solutions reading/writing from Web services, and this was good as when he asked me about securing web services i was stuck until i remembered how one of the service providers worked - by supplying a cookie to be used in each request after the initial login/pwd shakeup

Class member Entity.Id is unmapped.

ok, the problem come from the fact that we have a number of tables (linq entities), but only a few of them have the Id column, and only on those few i need to run a certain method.
so how to do this?

i created the generic method

MMethod(int id) where T : Entity, IEntity
{
var r = from s in source.GetEntity()
where s.Id == id
select s;
}

and here i started getting the errors...
first of course i could not use s.Id because the general T doesn't have Id member defined.
so i started looking where to define it - and first defined it in the interface.
now, the interface would have the property Id and some of the linq entities would also have it, but on evaluation of the var r i would get

The mapping of interface member [...] is not supported


nice...
some reading on google and i started looking for another place to add this member.
the other obvious choice - the entity class.
this seemed to be my last chance, after i tried coming up with an extension method or whatever desperate solution i could think of.

so, member added, all compiled nicely, but while in debug i decided to see what the var r evaluates to and saw a sweet message:

Class member Id is unmapped


so...WTF? Id is now nicely defined and visible everywhere, so how come this error? and what does it mean??

some browsing in google, and i come to this page

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2446465&SiteID=1

at first quick look i couldn't find any solution, but, ooo how nice that i didn't close the page immediately, because after some time i went back to it, as something stuck as a neat idea - the guy was talking about a possible bug in linq implementation, but gave a few examples of when a statement worked and when it didn't, so i decided to give a try to one of the statements that he claimed to have worked and....voila!
problem resolved.
while waiting for the build i came upon another page that confirmed this solution here: http://stuff.hornbostel.com/?cat=10

neat
thanks guys