Is objects a Linq-To-SQL database context? In which case, you can only use simple expressions to the right of the => operator. The reason is, these expressions are not executed, but are converted to SQL to be executed against the database. Try this Arr[] myArray = objects.Select(o => new Obj() { Var1 = o.someVar, Var2 … Read more
You need to turn it on its head in terms of the way you’re thinking about it. Instead of doing “in” to find the current item’s user rights in a predefined set of applicable user rights, you’re asking a predefined set of user rights if it contains the current item’s applicable value. This is exactly … Read more
You should supply the SqlParameter instances in the following way: context.Database.SqlQuery<myEntityType>( “mySpName @param1, @param2, @param3”, new SqlParameter(“param1”, param1), new SqlParameter(“param2”, param2), new SqlParameter(“param3”, param3) );
.Where(oh => oh.Hierarchy.Contains(“/12/”)) You can also use .StartsWith() or .EndsWith().
First off, if you’re starting a new project, go with Entity Framework (“EF”) – it now generates much better SQL (more like Linq to SQL does) and is easier to maintain and more powerful than Linq to SQL (“L2S”). As of the release of .NET 4.0, I consider Linq to SQL to be an obsolete … Read more