An open API service indexing awesome lists of open source software.

https://github.com/ajsaulsberry/blipphone

Demonstration project for using libphonenumber-csharp to validate phone numbers in an ASP.NET Core 2.1 MVC application.
https://github.com/ajsaulsberry/blipphone

aspnet-core aspnet-core-mvc telephony

Last synced: 5 months ago
JSON representation

Demonstration project for using libphonenumber-csharp to validate phone numbers in an ASP.NET Core 2.1 MVC application.

Awesome Lists containing this project

README

          

# BlipProjects

**_BlipPhone_** is an ASP.NET Core 2.1 MVC case study solution demonstrating implementation of the [libphonenumber-csharp](https://github.com/twcclegg/libphonenumber-csharp) library for server-side validation of phone numbers.

## Solution Projects

| Project | Application Layer |
| :--- | :--- |
| BlipPhone.Web | all |

## Technologies

| Dependency | Version*
| :--- | ---:
| Bootstrap | 3.3.7
| C# | 7
| jQuery | 3.3.1
| libphonenumber-csharp | 8.9.9
| Microsoft.AspNetCore.App | 2.1.1

* As of the latest commit.

## Getting Started

1. Download or clone this repository.
1. Open the solution in Visual Studio 2017 or higher.
1. Run the BlipPhone.Web application.

## Configuration

No special configuration environment configuration is required to run the project with IIS Express.

## License

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

## Contributing

See the accompanying instructions on [How to contribute](CONTRIBUTING.md).

## Disclaimer of Warranties and Limitation of Liability

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.