Reporter | Ri Scott (Ri) |
---|---|
Created | Dec 16, 2011 12:20:47 AM |
Updated | Mar 16, 2012 12:53:09 AM |
Priority | Critical |
Type | Bug |
Fix versions | 7.0 |
State | Open |
Assignee | Sergey Shkredov (serjic.shkredov) |
Subsystem | Code Completion |
Affected versions | 6.1 |
Fixed in build | No Fixed in build |
Intellisense is performing badly in LINQ queries when I try and do joins. Take the following compiled linq query:
protected static Func<SpiderEditContainer, int, string, IEnumerable<ItemOptionQueryResult>> GetItemOptionsQuery =
CompiledQuery.Compile((SpiderEditContainer db, int productId, string groupCode) =>
(from i in db.Items
join io in db.
select new ItemOptionQueryResult()
{
}
));
There are a number of problems that crop up here:
1) On the line that starts CompiledQuery.Compile.... After I type "SpiderEditContainer" and I begin to type the local variable name "db", ReSharper's Intellisense pops up a symbol locator as if I were looking for a type/symbol rather than typing a variable name.
2) After typing the word "join", it does the same thing. It doesn't know that I'm typing in a local variable name - it starts looking for a symbol.
In general, this is a fairly annoying problem overall in LINQ queries. The intellisense needs to be tweaked overall to know when to expect local variables and not pop up the intellisense/symbol locator pop up. It really interferes with the flow of work.
protected static Func<SpiderEditContainer, int, string, IEnumerable<ItemOptionQueryResult>> GetItemOptionsQuery =
CompiledQuery.Compile((SpiderEditContainer db, int productId, string groupCode) =>
(from i in db.Items
join io in db.
select new ItemOptionQueryResult()
{
}
));
There are a number of problems that crop up here:
1) On the line that starts CompiledQuery.Compile.... After I type "SpiderEditContainer" and I begin to type the local variable name "db", ReSharper's Intellisense pops up a symbol locator as if I were looking for a type/symbol rather than typing a variable name.
2) After typing the word "join", it does the same thing. It doesn't know that I'm typing in a local variable name - it starts looking for a symbol.
In general, this is a fairly annoying problem overall in LINQ queries. The intellisense needs to be tweaked overall to know when to expect local variables and not pop up the intellisense/symbol locator pop up. It really interferes with the flow of work.