We are currently in the process of updating this sample template. If you are encountering any issues with the sample, please open an issue at github.com/twilio-labs/code-exchange/issues and we'll try to help you.
This application example demonstrates how to do Simple phone verification with C# ASP.NET Core MVC, and Twilio Verify.
Implementations in other languages:
Python | Java | Ruby | PHP | Node |
---|---|---|---|---|
Done | Done | Done | Done | Done |
This application should give you a ready-made starting point for writing your own application. Before we begin, we need to collect all the config values we need to run the application:
Config Value | Description |
---|---|
Account Sid | Your primary Twilio account identifier - find this in the Console. |
Auth Token | Used to authenticate - just like the above, you'll find this here. |
Verification Sid | For Verification Service SID. You can generate one here |
After the above requirements have been met:
- Clone this repository and
cd
into it
git clone git@github.com:TwilioDevEd/verify-v2-quickstart-csharp.git
cd verify-v2-quickstart-csharp/VerifyV2Quickstart/
- Build to install the dependencies
dotnet build
- Set your environment variables
cp VerifyV2Quickstart/twilio.json.example VerifyV2Quickstart/twilio.json
See Twilio Account Settings to locate the necessary environment variables.
- Install EF Core CLI if it's not already installed.
dotnet tool install --global dotnet-ef --version 3.0.0
- Create the local DB. This also should be executed in
VerifyV2Quickstart
directory.
dotnet ef database update
- Run the application
dotnet run
- Navigate to http://localhost:5000
That's it!
If you have Docker already installed on your machine, you can use our docker-compose.yml
to setup your project.
- Make sure you have the project cloned.
- Setup the
twilio.json
file as outlined in the Local Development steps. - Run
docker-compose up
.
You can run the tests locally by typing:
dotnet test
- The CodeExchange repository can be found here.
This template is open source and welcomes contributions. All contributions are subject to our Code of Conduct.
No warranty expressed or implied. Software is as is.