This question is locked. New answers and comments are not allowed.
Upgraded ORM to use the latest version 2011.3.1129.2 from 2011.1.316.10 that I had been using for a while with hopes of some minor fixes. This upgrade seems to have broken a very simple LINQ query with a join:
from c in context.Ac_Categories
join cp in context.Ac_CategoryParents on c.CategoryId equals cp.CategoryId
where c.VisibilityId == 0 && c.Name == name
&& cp.ParentNumber == 0 && cp.ParentLevel == 1
orderby c.Name
select c
The error was that the engine wanted to know why 'ParentNumber' was not a part of 'Ac_Categories' and as such, wanted me to make that field in the class. After fighting with it for a little, I decided to go back to my working version from March2011 and just deal with that for now and of course this simple query works fine with that version. I thought you should know about this problem and see if anyone had any insight in the meantime. Thanks!
2011.3.1129.2 from 2011.1.316.10