Open the Web.config file of the ToDoListDataAPI project. Open the project in Visual Studio by double clicking ToDoList.sln, if it is not already open from Part 1.
Now we need to link up all the pieces to ensure data is gathered and stored correctly. Your SQL database should look something like this now.Ĭonnecting Visual Studio and SQL Database ? Go back to SQL Server Management Studio and hit refresh. Click OK.ĭon’t edit any other values on this modal and just hit Publish. Make sure the Database Name is ToDoListDb, but that should be filled in for you. Right click on the ToDoListDb project and choose Publish.įor Server name, take the Notepad value you saved for ComputerName\ServerName and enter it here. Open the folder that we downloaded earlier by double clicking ToDoList.sln. Save your ComputerName\ServerName in a Notepad, we will need this again later. This name most likely will be in the format ComputerName\ServerName.Ĭhoose Windows Authentication. Open SQL Server Management Studio (SSMS) and click the dropdown on Server Name and choose Browse for more.Ĭhoose the Server name of your instance. Download a copy here and extract it to a folder on your hard drive. Then connect your frontend Angular project to the API project. You need to connect the API project to your SQL Server. You will then open the solution in Visual Studio. The local setup will start with setting up your database.
You can get Visual Studio 2017 Community for free here.ĭon't Forget SQL Server Management Studio You get $200 USD credit a month, these are free credits on a trial account and cost you nothing.Īs a note, the instructions will be using Visual Studio 2017.
The Azure account asks you for a credit card number, but will not charge you at all or “roll into a paid version,” it simply expires when your trial month is up.
You will need a basic understanding of coding and software installation. The tutorial can be completed for free, but will require a Azure account. Please download the required software listed below. You will push the code to Azure DevOps and create a CI/CD (Continuous Integration/Continuous Delivery) process in order to deploy to Azure.
In Visual Studio, you will start out with a working version of the TODO application. The process for the app is described below. You're welcome to follow along with the tutorial or simply read and get a better idea of how you can apply the same patterns to your app. The app is a basic To-Do application - we'll call it TODO - created with Visual Studio, VSTS (now Azure DevOps), C#, Angular, and SQL.
But it does provide an end-to-end example of how to string different products together from within the Azure ecosystem and make your software delivery more continuous.Ĭrystal Tenn and Michael Crump from Azure Tips and Tricks teamed up to feature an Azure App Service site that communicates with an API project and an Azure SQL backend. This example doesn't necessarily cover the exact stack you're using. (And I was pretty skeptical when I started using it.) It's incredibly powerful and has a truly enjoyable user experience. If you haven't had a chance to dig into Azure DevOps yet, I think you're missing out. We've selected our favorite tips and tricks created by Michael Crump and are delivering fresh technical content on Azure all April! Miss a day (or more)? Catch up with the series.ĭon't have Azure? Grab a free subscription.