Error in SmartFilterAdapter, ExpressionPropertyAnalyzer

Aug 26, 2008 at 1:33 PM
I am getting a dictionary key missing. error in the SmartFilterAdapter's constructor. It is throwing on a missing type key. The ExpressionPropertyAnalyzer is missing my info. There is a switch:

switch (expression.NodeType)
            {
                case ExpressionType.MemberAccess:
                    MemberExpression memberExpression = (MemberExpression)expression;

                    PropertyInfo property = memberExpression.Member as PropertyInfo;
                   
                    if (property != null)
                    {
                        HashSet<string> propertyNames;
                        if (!properties.TryGetValue(property.DeclaringType, out propertyNames))
                        {
                            propertyNames = new HashSet<string>();
                            properties[property.DeclaringType] = propertyNames;
                        }

                        propertyNames.Add(property.Name);
                    }
                    break;

                case ExpressionType.Parameter:
                    break;

                default:
                    break;
            }

My member is type of int32 so it is not getting into the list of properties. Is it supposed to? Here is my linq query:

            View.Bids = from b in buy
                        where b.Security.Id == View.Security.Id
                        orderby b.Price, b.Quantity ascending
                        select b;

The security.id is where it is falling off and missing the type in the smartfilteradapter. If i remove the where clause, it works fine.

Any thoughts?

-Chris

Coordinator
Aug 27, 2008 at 12:16 PM
Chris,
  Thanks for posting this. While we'll certainly look into it, keep in mind that all of the 2.0 stuff for CLINQ is highly experimental right now. None of this stuff is ready for prime time so there are bound to be bugs in it.
Coordinator
Aug 27, 2008 at 6:51 PM
Sit tight on this particular one, we've got some refactors going on that aren't checked in that are likely to fix this problem.
Aug 28, 2008 at 6:19 PM
Thanx. So what does the current tip of dev have vs 1.0 release? perhaps i am better off on 1.0.
Coordinator
Sep 16, 2008 at 9:00 PM
The latest in 2.0 branch now has better support for deep property notification.

To get the binaries, grab the 1.1 release from the front of the site.