Sascha Kiefer esskar

esskar commented on issue esskar/Serialize.Linq#45
Sascha Kiefer

can you configure the serialization? If they use Json.NET for example, you could set TypeNameHandling = TypeNameHandling.Objects, and solve the pro…

esskar commented on issue esskar/Serialize.Linq#46
Sascha Kiefer

glad, it is so simple ;)

Sascha Kiefer
  • Sascha Kiefer 2ff4a17
    fix bug introduced in last commit: passing null is incorrect (address…
esskar commented on issue esskar/Serialize.Linq#46
Sascha Kiefer

is adding ExpressionContext enough? or am I missing something?

Sascha Kiefer
  • Sascha Kiefer c19de31
    allow to pass an ExpressionContext (addresses #46)
Sascha Kiefer
Sascha Kiefer
  • Sascha Kiefer 38a6f52
    narrow serializers to serialize nodes only
Sascha Kiefer
  • Sascha Kiefer f8fe07e
    add factory settings and use type.FullName only when UseRelaxedTypeNa…
Sascha Kiefer
  • Sascha Kiefer 311119b
    remove MemberType as it is not needed for serialization
esskar created repository esskar/Serialize.Linq.Json
esskar commented on issue esskar/Serialize.Linq#45
Sascha Kiefer

Fun to see that Serialize.Linq is used in various projects!

esskar commented on issue esskar/Serialize.Linq#44
Sascha Kiefer

idea: when the type to serialize is from an anonymous class, we use the full qualified name, otherwise we stick to type.Fullname how does that sound?

esskar commented on issue esskar/Serialize.Linq#43
Sascha Kiefer

Thanks for that. Yet i thought about a new NodeFactoy implementation, but i was to busy to actually do it. Maybe on the weekend.

esskar commented on issue esskar/Serialize.Linq#44
Sascha Kiefer

hi. not that i am aware of. due you have the stack trace? i will try to analyse.

Sascha Kiefer
esskar commented on issue esskar/Serialize.Linq#43
Sascha Kiefer

idea: special collections that where the values get serialized when used in expressions!?

esskar commented on issue esskar/Serialize.Linq#43
Sascha Kiefer

not sure if i want to support this. i am build the expression tree using recursion, to change it, i would need to build my own stack; i have to eva…

esskar commented on issue esskar/Serialize.Linq#43
Sascha Kiefer

as @vsoldatkin stated: we need the original expression that causes that error. But it looks like you should rethink your expression x.Account >= 79…

esskar commented on issue esskar/Serialize.Linq#41
Sascha Kiefer

I just published version 1.2.2. I owe you a beer!

esskar commented on issue esskar/Serialize.Linq#39
Sascha Kiefer

I just published version 1.2.2.

Sascha Kiefer
Sascha Kiefer
Processing Linq expressions may cause exceptions
esskar commented on issue esskar/Serialize.Linq#41
Sascha Kiefer

I think i fixed it with this c18f903 commit. Can you have a look and retest your stuff please?

Sascha Kiefer
  • Sascha Kiefer 1d5d3ef
    Issue 40 is actually Issue #41