BlipValidate is an ASP.NET Core MVC case study solution to accompany an ASP.NET Core article on codeArbor and three guides in the PluralSight Guides collection for Microsoft .NET technologies.

Building robust numeric fields for HTML forms with ASP.NET Core MVC - Building robust numeric data fields for data entry on the web should include validation of client data on both the client, in the browser, and on the server. ASP.NET Core MVC provides excellent resources for these tasks.

ASP.NET Core MVC Client Data Validation - Part 1: ViewModels and Data Annotations - This guide, the first of three parts, presents the foundational level of client-side data validation using the MVVM design pattern: viewmodels and data annotations.

ASP.NET Core MVC Client Data Validation - Part 2: jQuery validation - The second installment builds on the foundation created in Part 1 by explaining how widely-used jQuery libraries can provide responsive client-side data validation by working in conjunction with the HTML created by ASP.NET Core MVC.

ASP.NET Core MVC Client Data Validation - Part 3: Controller validation - Part 3 shows how the view model, data annotations, and the ModelState object come together with MVC model binding to provide server-side validation of client data, an essential part of the client data validation process.

Notice: codeArbor, PluralSight, and the author(s) disclaim any liability for errors or omissions in this code. See the Disclaimer of Warranties and Limitation of Liability for complete information.

* As of the latest commit.

1. Download or clone this repository.
2. Open the solution in Visual Studio 2017 or higher.
3. Open a Package Manager Console window.
4. Change Default Project to BlipValidate.Data.
5. Run update-database to create the database.

• Note that the database is not required to run code associated with any of the Guides listed above.

• The following files contain configuration strings which may require modification for the developer's specific environment:

  Project	File
  Blip.Web	config.json

• The configuration strings specify the instance of SQL Server Express installed with Visual Studio 2017 as the target database server: Data Source=(localdb)\ProjectsV13. Developers using a different target database will have to change the connection strings in both projects.

This project is licensed under the terms of the MIT license.

See the accompanying instructions on How to contribute.

The contents of this repository are offered on an as-is and as-available basis and the authors make no representations or warranties of any kind concerning the contents, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable.

To the extent possible, in no event will the authors be liable on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of the use of the contents, even if the the authors have been advised of the possibility of such losses, costs, expenses, or damages.

The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.