data-annotations

I'm laying out a view that compares two password strings. The two properties in one of my models are pretty straightforward: [Required] [RegularExpression(@"(\S)+", ErrorMessage = "White space is not allowed")] [StringLength(20, MinimumLength = 6)] [DataType(DataType.Password)] [Display(Name = "New Password")] public string NewPassword { get; set; } [Required] [DataType(DataType.Password)] [RegularExpression(@"(\S)+", ErrorMessage = "White space is not allowed")] [StringLength(20, MinimumLength = 6)] [Display(Name = "Confirm Password")] [Compare("NewPassword", ErrorMessage = "The new password

I didn't use jquery.ui's datepicker because I needed to select an entire week and multiple dates under different conditions, so I am using Keith Wood's datepicker in an EditorTemplate for my Date fields: @model Nullable<DateTime> @{ string name = ViewData.TemplateInfo.HtmlFieldPrefix; string id = name.Replace(".", "_"); string dt = Model.HasValue ? String.Format("{0:d}",(string)Model.Value.ToShortDateString()) : string.Empty; } @Html.TextBox("", dt, new { @class = "datefield", @type = "date", @id = id }) <script type="text/javascript"> $(document).ready(function () { $('#@id').datepick({

I have a small MVC2 app that displays in two cultures: en-US and es-MX. One portion contains a user input for a date that is pre-populated with the current date in the Model. When using en-US, the date field is displayed as MM/dd/yyyy and can be changed using the same format without causing any validation errors. When using es-MX, the date field is displayed as dd/MM/yyyy, but when the date is edited in this format, the server-side validation fails with the message: The value '17/05/1991' is not valid for The Date. One of the first things that jumps out at me about that message is that it is

Putting simple Data Annotations on properties is great, public class UnicornViewModel { [Required] public string Name { get; set; } But lets say I'm have something like this: public class SuperPower { public class Name { get; set; } } public class UnicornViewModel { [Required] public string Name { get; set; } public SuperPower PrimarySuperPower { get; set; } public SuperPower SecondarySuperPower { get; set; } How do I apply the Required attribute on PrimarySuperPower.Name while leaving it optional for SecondarySuperPower.Name? Preferably 1. something that ties into client side validation and 2

So I have a UserProfile model class as part of SimpleMembership. In it I need to store a legacy identifier that exists in another DB of type char(36) . I'd love to change this to something more sensible like a uniqueIdentifier but that's out of scope for today's activities. My current annotation creates a column nvarchar(36) [StringLength(36)] public string UserIdentifier{ get; set; } I'd like a column of char(36) instead. Is this possible? If you want to keep with Data Annotations, then just simply use: [StringLength( 36 )] [Column( TypeName = "char" )] public string UserIdentifier{ get; set;

Is it possible to define a many-to-many relationship in Entity Framework 4.1 (Code First approach) using Data Annotations only, without model builder? For example, something like: Product = { Id, Name, ... } Category = { Id, Name, ... } ProductCategory = { ProductId, CategoryId } You get the picture. I don't want to have an intermediate entity ProductCategory in the context with two many-to-ones since I don't have any additional data, just the two FKs. Also, I should be able to define table name for the intermediate table for use with an existing database. It is possible to define many-to-many