SQLiteDemo | Source code for blog post http : //blog | Blog library

Well, the problem is not related to StartsWith. If you check the exception DbSet .Where(m => x.TopLevelString != null && "A" != null && x.TopLevelString.StartsWith("A") starts with m => but inside uses x this is caused by ParameterExpression entityParameter = Expression.Parameter(typeof(TEntity), stringSelector.Parameters.First().Name); line. You use that parameter name to generate another parameter but they are not the same.

There are 2 solutions for that.

1. Is to use parameter directly and extend your expression on it
2. Rewrite your member expression with the newly created parameter which is redundant.

So basically this will solve your issue :

Since basic XML is just string data, we can solve this problem using simple string replacement. It isn't particularly elegant, but I think it answers the question:

1 - You have a typo as you have already determined :)

1B - "SQL logic error no such column: Extent2.CardHolder_CardHolderId"

EF isn't finding your FK. You could add it to your AccessCard model:

You passing the parameter right what left is just to get it after the navigation.

Add this function to the Editar.xaml.cs

Use Newtonsoft.JsonConvert.DeserializeObject(content);

IntIrestService is the interface, you can't instantiate the interface.
You need to instantiate the concrete class that implements the interface.

If you're targeting explicitly Mono then use the Mono version of the SQLite connector (never knew why they decided to break the namespace compatibility, but that's how they did it).

Just replace the references and usings from System.Data.SQLite to Mono.Data.SQLite