Rockford Lhotka

Sadly it isn't a bug, it is a limitation. If T is a child type you'll find the same result. It T is a system type we can resolve the...

I haven't looked at your PR yet. Hopefully it is a good solution. The issue is this: if we allow types _from your assembly_ to be resolved with different version...

JSON has a much easier job that we do, because JSON isn't a full fidelity serializer. The output from deserializing a JSON stream is not guaranteed to be identical to...

I'm not sure 3 is necessary. The instance creation code in `MobileFormatter` should be (I think) the only place where a change is required. I don't recall if this code...

I understand what you are saying, but there's a philosophical core to CSLA, which is that all rules are centralized in the business layer. I'm thinking forward to the ProjectTracker...

I think we're on the same page - we've both been authorized 😄 I'm not trying to force the idea that every page uses CSLA authorization. But it needs to...

I appreciate your input @kellyethridge. I agree that the multiple parameters is very important. I am torn on the DI, and am leaning toward doing _both_. As you note, we...

I'd be thrilled to have another language as a resource. But if you just roll your own rule classes you get to provide your own output strings.

Thank you @rxelizondo - most of the text is very technical with developer jargon, that is very true. I suspect a native Polish speaker, who is also a developer, would...

The DataAnnotations attributes have a solution too - where you can provide a resource moniker they use to find the string. If I remember right, you provide the assembly containing...