Showing related tags and posts across the entire site.
-
This sounds like a question you might need to ask in an ASP.NET forum on MSDN or something. I've never explored this part of the DataAnnotations infrastructure.
-
Does anyone know which DataAnnotations presently work with CSLA in a Windows Forms application. I have personally had success using Required, StringLength, Range and CustomValidation. I have attempted to use the ConcurrencyCheck DataAnnotation without any luck. Is there a list of working ones I can reference...
-
We are using partial classes for our generated CSLA code. We are also using data annotations. Our generated code contains data annotations based upon the database (e.g. InvoiceAmount which gets a generated data annotation of Required since the column is not nullable). We do not modify our generated code...
-
I have a non-CSLA Property with a [Required] data annotation that is causing CLSA to freak out. [ DataObjectField ( true , false )] [ Required ] public string DateString { get { return InternalDate . Text ; } set { InternalDate = new SmartDate ( value ); } } It's a runtime issue, that happens in...
-
Unfortunately that isn't the case. I am not overriding and it isn't working. I'm pulling about 30 property values for the four EditableChild document objects that are pulled out of a database from various related tables by the query in my EditableRootList parent object. I'm marking ALL...
-
If I understand you correctly, as long as I am not overriding AddBussinessRules, this should be working, right? I don't have a single line of code in that method. Should I be calling the base explicitly? ( I wasn't doing that when this was briefly working.) If it had NEVER worked, it wouldn't...
-
I've been having uneven (and now, none at all) success with these. I've got all my properties decorated with the Required attribute and I call CheckRules at the end of my Child_Fetch routine. I haven't added any Validation Rules because my understanding is that they are unnecessary for this...
-
I've put a little more thought into this. I'm not entirely sure it is a good idea. There's a short-term pain issue - it is another breaking change from 3.x to 4 - but I could live with doing that. The bigger problem is that it forces a dependency on System.ComponentModel.DataAnnotations for...
-
[quote user="cdkisa"] Is there still going to be support for DataAnnotation attributes? [/quote] Yes, absolutely. That is in the current preview and works just like it does in 3.8.
-
The attributes normalize in .NET 4. There are some substantial implementation differences in the base class between SL3 and .NET 3.5 too, so there's no functional equality either - the SL behavior is much more powerful. But .NET 4 brings .NET into line with SL - so you should assume what you are...
-
Requiring the DataAnnotations display name attribute is one option - which does solve the localization issue. Another option is to leave the friendly name in PropretyInfo<T>, but to have PropertyInto<T> maintain a reference to the underlying System.Reflection.PropertyInfo, making it easy...