You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.
We can name server side Dataportal methods any valid identifiers as long as they have appropriate attributes?
The Client side dataportal methods' names remain the same as in Csla 4.xx and earlier versions? we can't arbitrarily name them?
In Csla 5.XX do the same rules apply to overloading Data Access operations? we have to define multiple criteria? (In our case sometimes we get a 'companyInfo' by EIN, in other cases it's by legal name. )
warm regards
Version and Platform
CSLA version: 5.xx
OS: Windows, Linux, iOS, Android, etc.
Platform: WinForms, WPF, ASP.NET Core, MVC, Xamarin, etc.
The text was updated successfully, but these errors were encountered:
I'm not sure what you mean? All logical server-side methods (better described as data portal operation methods) are now identified by attribute, regardless of whether you use the local or remote data portal configuration. The methods on the actual DataPortal and DataPortal<T> types are fixed of course, because they are part of the framework, not your code.
Your data portal operation methods (decorated with Fetch, Update, and other attributes) can now accept multiple parameters as long as the parameter types are (a) serializable, or (b) injected using the Inject attribute.
@rockfordlhotka , Thank you Sir, that explains all of it.
2) I think some of the terms I use for Csla are 'dated' hehe , As I type this, and I am not making this up, your C# 2008 book is lying on the left side of my chair 😄 . I had to look something up a few days ago.
Kind regards
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Question
A few quick questions
warm regards
Version and Platform
CSLA version: 5.xx
OS: Windows, Linux, iOS, Android, etc.
Platform: WinForms, WPF, ASP.NET Core, MVC, Xamarin, etc.
The text was updated successfully, but these errors were encountered: