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
Based on #1102, CSLA 5 will now allow arbitrary method names for data portal operations, with the operation identified via attribute instead of a hard coded DP_XYZ name (though those remain fallbacks for legacy support).
The idea of this analyzer is to guide people to use the new attribute-based model by providing a warning that they are still using the DP_XYZ and Child_XYZ naming convention.
The text was updated successfully, but these errors were encountered:
Based on #1102, CSLA 5 will now allow arbitrary method names for data portal operations, with the operation identified via attribute instead of a hard coded DP_XYZ name (though those remain fallbacks for legacy support).
The idea of this analyzer is to guide people to use the new attribute-based model by providing a warning that they are still using the DP_XYZ and Child_XYZ naming convention.
The text was updated successfully, but these errors were encountered: