asp.net - Is ModelState.IsValid really necessary?

Question

So I have an AccountVM.

public class AccountVM
    {
        [Key]
        public int Id { get; set; }
        [Required]
        [MaxLength(30)]
        public string Name { get; set; }
        [Required]
        public double Value { get; set; }
        [Required]
        [EnumDataType(typeof(AccountType))]
        [Display(Name = "Account Type")]
        public AccountType AccountType { get; set; }
    }

And then I created CreateAccountVM

public class CreateAccountVM
    {
        public AccountVM Account { get; set; }
        public List<AccountType> AccountTypes { get; set; }
    }

I used AccountVM to have cleaner code and I can use Automapper then as well. But I cant use ModelState.IsValid when I return CreateAccountVM. So do I really need it, since after mapping the Account model will be checked again when entered in the database, right?

Or perhaps there is another way for me to use ModelState or do a check?

question from:https://stackoverflow.com/questions/65872962/is-modelstate-isvalid-really-necessary

Answer 1

Waitting for answers