MVC :: DataAnnotations And Model MetaData Caching?
Nov 1, 2010
My case:I am developing an application that will run for multiple clients, each client has the ability to customize field displays and error messages.My issue:I created some custom attributes which inherit from DisplayNameAttribute, RequiredAttribute etc... and in them I am pulling out the resource needed.However it is only executed the once, so if my context changes it will be pulling the incorrectly cached value instead of pulling the new value need.Has anybody attempted to try something like this with the data annotations? Or any advice such as just don't use them for this scenario?
In my project I use Strong Types Views. Because I find it nice structured.
public abstract class AbstractViewData: View Page ( ICollection Foo; ) public class HTML Component View Data: AbstractViewData ( string Foo2; )
I have the same structure in my code, as in the corresponding pages.And here starts the problems. I would like to use HTML.Display (o => o.Foo) could be a customer for that matter.But my Strong Types Views have not posted Metadata Model into my classes.Like: Return View ( "FooView", customer); would.Is there a way to write some code that can solve this problem for me?
I'm working on an ASP.NET MVC 2 project with some business entities that have metadata dataannotations attributes applied to them (Validation attributes, Display attributes, etc.).
Something like:
[Code]....
Using the metadata from different views is no problem, as long as I am using my business entities as viewmodels or as part of a viewmodel like this:
[Code]....
However, sometimes I need to code a view for editing some, but not all fields of an entity. For those fields I want to reuse the metadata already specified in my user entity. The other fields should be ignored. I'm talking about custom view models like this:
[Code]....
That's where I am running into problems. The custom view model above leads to an exception when the view is generated, because it has no password property.
The associated metadata type for type 'Zeiterfassung.Models.ViewModels.Users.UserNameViewModel+UserModel' contains the following unknown properties or fields: Password. make sure that the names of these members match the names of the properties on the main type.
Also, even if this exception did not occur, I expect to get into even more trouble with model validation on form submit because Password is marked as required in my business entity.
I can think of several workarounds, but none seem really ideal. In any case I can't change the database layout so that the password field would be in a separate entity in my example above.
i am working an asp.net mvc 2 web app using model metadata and some of the model metadata don't seem to work when using the default Html.EditorForModel().For example, when applying the DefaultValue(1) and the ReadOnly(true) attributes on a model field, the field displayed on edit view has zero for its default value and it is not read only.
I would like to separate my attribute decoration(3-4 per field) by having them someplace else so that my code looks readable.Also the arguments passed to some attributes should come from a resource file.EG:[Required("Cannot proceed without entering *field_Name*")]
I need just [Required] Possible duplicate of this question(on which i couldn't resist offering a bounty) : Default resource for data annotations.
I was wondering if anyone can point me in the right direction? I have a POCO model and I am using Code First CTP. In my application, I set the database to be recreated whenever the model changes.
I would like to write custom functionality to access the model (POCO) metadata same way as EF sees it and use that to generate some source files (using T4). I would like to access the processed model not having to worry about finding properties that hold primary keys or any other conventions (implicit or not). What is the way to go about it?
I would like to extend the HtmlHelper by using metadata (similar to DataAnnotaions metadata). Specifically I want to be able to add a 'Title' attribute to html controls that will then appear as a tooltip on the control. I would like to keep the tooltip text with my model, for example by adding 'Tiltle' metadata to the model as follows:
[DisplayName("User Id")] [Title("Enter your 10 digit user id")] property UserId { get; set; }
So the questions are:
1. How do I add metadata (such as 'Title') to my model?
2. How do I access this metadata in my HtmlHelper extension method?
I have a page with a number of user controls, In one of my user controls I have a button event. I turn on output cache for the user control that has the button and vary by control using the ID property of a hidden field control in the user control. whenever I turn on the output cache my button event doesn't fire.
I'm building an MVC 2 application with a MySQL database behind it. I've imported the model by adding an ADO.NET Entety Datamodel. Now I want to use DataAnnotations to validate the user input. So I have added the line
[Code]....
[code]....
However, It just doesn't do anything. The Model.IsValid() returns true no matter how long a string I submit.
I am using business objects that are accessed via webservices. These objects can be loaded via the webservice and serialized to my mvc app. The mvc app can get a web reference to the objects and they can be utilized in the mvc app. However, the business objects are where the classes are defined, and where the annotations are applied.
The mvc validation seems to have no idea that there are System.ComponentModel.DataAnnotations attributes applied to this business object class.
1) Are DataAnnotations lost when objects are serialized / deserialized?
2) If in mvc I use a view model approach, and have nested objects (which themselves have public properties - decorated with DataAnnotations) can/will the mvc validation system traverse the entire object model, the model being used for my view? (so it can see DataAnnotations attributes of the nested object)?
I am using Entity Framework with partial classes added on so I can use DataAnnotation attributes. Does anyone know how to add a data annotatin which will verify that a field is a whole number (or a DataType of int or long)? I'm surprised there is no [DataType(DataType.Integer)] attribute. I tried to create a custom attribute, but it doesn't work because the value it receives is always null:
[code]....
Obviously I'm missing the point, but I don't know enough to know what I'm missing.
I have a DateTime property in my model and I would like to validate it using DataAnnotations.In my view I want to get that DateTime as a number of days (e.g. "3"), instead of a DateTime (e.g. "7/14/2010"). If user enters "3" in the view, then DataAnnotation finds it invalid -and that is the issue.What are my options in this scenario?
Using data annotations for asp.net MVC, I can enforce range, regular expressions, required, stringlength, etc.. However, I have boolean property "SignedDocument" that I want to enforce its set to true? Is this possible in data annotation?Example:
I want DefaultModelBinder not to perform any validation based on DataAnnotations metadata. I'm already using DataAnnotations with DynamicData for the admin area of my site, and I need a different set of validation rules for the MVC based front-end. I'm decorating my classes with the MetadataType attribute. If I could have different MetadataType classes for the same model but used on different scenarios that would be great.If not I'm fine with just disabling the validation on the DefaultModelBinder, either by setting some property or by creating a specialized version of it.
I have a few field in my entity that i wish to be non-editable. Looking in the docs it seems like "EditableAttribute" would do the trick. However this is only 4.0Just wondering if there are other attributes that would have the desire effect. So be clear, i have a field called "DateRegistered" i wish to display this as string not text field using "Html.EditorFor"
I have a problem with server-side validation in xVal. I'm using the RequiredAttribute from DataAnnotations.
I would like to change error message from:
The field is required.
to:
Polje je obvezno.
My current solution is this: [Required(ErrorMessage = "Polje je obvezno.")]
But I was wondering if it's possible just to write [Required] and to override error message in one place? (like there is a localization file for client-side validation in xVal)
Is it possible to add a CSS class from DataAnnotations (metadata) when I use Html.EditorForModel() - without a custom template...
Something like this [DataType(CssClass = "DateTime")]
public class TestInput { [Required(ErrorMessage = "Name is required.")] public string Name { get; set; } [Required, StringLength(500)] [DataType(DataType.MultilineText)] public string Description { get; set; } [Required] [DataType(CssClass = "DateTime")] public DateTime Date { get; set; } [HiddenInput(DisplayValue = false)] public int Id { get; set; } }
My problem is that when i do a tryupdatemodel it validate the ParentCategory aswell, is it really suppose to do that? How could i avoid this, I tried [Bind(Excluede = "ParentCategory)] in the ActionResult but with no luck. I have looked all over the place with no luck everybody just got the Id problem.
I'm having problems with getting my custom dataannotations to work, I'm trying to add a validation-attribute that validates that the UsergroupName for a Customer (CustomerID) is unique.
[Code]....
the IsValid should return false if the "count >0". How do I fix this one so it works. GetUsergroups() returns IQueryable<Usergroup>.
I have tried everything to get client-side validation to work in MVC2 RC, but have been completely unsuccessful. Server-side validation works just fine, but client-side never fires. I have grabbed
[Code]....
from the futures source, since it wasn't included in RC. Unfortunately, that's the only script that people agree is necessary for everything to work. Besides that, nobody seems to know which other specific js scripts are needed. The candidates are (jquery-1.3.2.js, jquery.validate.js, MicrosoftMvcAjax.js, MicrosoftMvcJQueryValidation.js). I've tried every permutation of these and other scripts to no avail.
Html.EnableClientValidation() has been included before BeginForm, and the JSON validation data appears to be correctly written into the source of the page. But, again, client-side validation never fires.
So, is this the way it's supposed to work? Shouldn't enabling client-side validation highlight non-validating elements by default, without an needing to create an associated Html.ValidationMessageFor(), if it has a DataAnnotation validation attribute?
[Required(ErrorMessageResourceName = "ValidationError_Required", ErrorMessageResourceType = typeof(Resources.Resources))] public string Title { get; set; } public class LRequiredAttribute : System.ComponentModel.DataAnnotations.RequiredAttribute [code]...
I'm building an application using MVC 3 and Entity Framework 4. I've created my Entity Data Model and generated a database from it. Now I know the validation attributes such as [Required] or [StringLength(5)] can be used on the model properties to provide validation both clientside and serverside.
I would like to know if these attributes can also be generated dynamically instead of having to add them to the model explicitly? I saw that in EF 4.1 RC you can make use of the Fluent API to further configure your model in the OnModelCreating method by using the DbModelBuilder class. As shown here I'm working with a framework however that still uses ObjectContext instead of DbContext so I would like to know if the above solution can be used in combination with ObjectContext?
As a final note, since I've been trying to figure out how to generate and use data annotations it seems using view models would increase the complexity of validation. From what I read here it seems that just passing the models directly to the view would remove the need to add annotations to the models as well as the view models. However that means that you can no longer use strongly typed views when you do joins on the models and pass those to the view directly?
