Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Technical Support

lambda expressions autocomplete madness

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
clintp	Posted - Feb 05 2010 : 09:32:41 AM Using VS 2008, Visual Assist X 10.5.1738.0 When constructing a lambda expression in C#, the input variable to the expression triggers keyword expansion -- and is starting to drive me crazy. If I attempt to type: fields.Keys.Where( k => k == "test) Before I can finish I wind up with: fields.Keys.Where(KeyNotFoundException= It's not just "k", it's almost any single letter input variable. Workarounds include typing the => first, backing up with the arrow keys and typing the input variable again. Or use a two-letter input variable with unlikely combinations (xk, qp, hj). But having to make a style change to suit Visual Assist is stupid. Is there a fix for this in the works?
2 L A T E S T R E P L I E S (Newest First)
clintp	Posted - Feb 05 2010 : 2:57:07 PM quote: Originally posted by feline Do you have either of the options: VA Options -> Advanced -> Listboxes -> Selections committed with: Any character not valid in a symbol IDE tools menu -> Options -> Text Editor -> C# -> IntelliSense -> Committed by pressing the space bar turned on? It sounds like the listbox is being accepted when you type the space after "k", but this should not happen by default. Strangely enough I had both of them checked, for optimal annoyance. Thanks for the quick reply.
feline	Posted - Feb 05 2010 : 1:23:04 PM Do you have either of the options: VA Options -> Advanced -> Listboxes -> Selections committed with: Any character not valid in a symbol IDE tools menu -> Options -> Text Editor -> C# -> IntelliSense -> Committed by pressing the space bar turned on? It sounds like the listbox is being accepted when you type the space after "k", but this should not happen by default.

Snitz Forums 2000