Hello guys, welcome to the 26th session or the SP dotnet Web API. In this session, we will learn how towards an end our API using the UI. The first question arises that what is worsening when our API probably is many client are going to use it. If we need to make the changes in iOS 10, it will reflect to the all of the inclined to solve this, we are creating the various version of the API. There are several way to creating the versioning in our API, we can create our signing using the UI accept header words on hitter media type as well as the query string. In this lesson, we are going to use the versioning using the Ura.

Let's switch to the Visual Studio. I'm created a new VBA project in which add a new model off name employee v1 The ShareFile version one and within these, I'm going to create a public integer ID property that public string name. Yeah Then set and now going to create a new controller, new controller or to VBA to empty off name, employee we won. Within that we need to create a static list of employee version One add the namespace all employees equal to new list of employees. Within that we are going to create a new instance of the employee version one with the dummy data is equal to one name equal to new ly employee ID equal to name equal to Ravi. One more child equal to three and named Makoto.

So come and see me semicolon After that creating a get method public enumerable of employee words and one get within that window just written the all employees and another method for receiving the insurance or the employee or someone within that we are providing the ID and we need to return all employees door pushed or before an employee such that employee.id will require them don't hide in a parameter Let's see how we are going to route menus of idpa slash v1 slash employee then we need to return the list of the all the employees. And when he was a fire the APS last we went to last employee slash ID, then we need to return the employee with Diego ID. When the user use the v2 instead of the v1, then we need to perform the all of those operations on the v2 insurance. There are two way for providing the versioning.

Using the UI, we can use the conditional based routing as well as attribute routing. Let's do the attribute routing. For that we need to use the route prefix attribute at the controller level. And specify that prefix API slash v1 slash employee and specify route for the our method that will be empty string when we are retrieving all of the employee. And when we are returning the employee with a given ID then we pass the ID within double quote. Let's try it.

Let's open the our API page that is slash API slash v1 slash less. employee. We can see that we are assuming the employer do worse than one. And let's specify the ID we are also able to recruit the editor or the employer with a given ID. Now our requirement is a change and along with the name we are going to pass the HR department name for the employee. For that we are going to create a version two which will be accessible from the changing the we do in the URL.

Now we are receiving the 404 error because we are not developed it that let's switch to Visual Studio. Stop the execution. I'm going to create a new model add a new class of meme employee version two which can then go to property. Along with this, it also contained the public shaming department name and also create a controller. Let's copy the existing one and change its name and change the route prefix to I have already a copy the list of the employee as per the employer words into a state instead of returning the employee offers on one we are going to return the words and two in both method and let's preview the our solution. Forget the semicolon.

Let's send request to the our version two. You can see that it's written the employee v2, and also contain the department name. And now we are going to retrieve the employee ID from the URL or the EPA and you can see that it does not return the department name. We are creating versioning of the our API on Ura based on the attribute routing, however, we can also provide versioning based on the conditional based routing. For this first of all, we need to stop the our solution and the comment in the comment do all of the attribute you know was in one Well, it's only to comment India wasn't too open the VBA config file. Copy the map attribute out tiara and comment is one, two Paste it change the anyone do a route, let us do was on one and it seems the routing template to the ones less.

Now we need to pass the controller name, controller equal to employee version one and I can copy and change your one to two. Let's build our solution. I'm going to reload the previous page you can see that the From the version one was received successfully, now we're going to chain to the version two. It was working same as the attribute routing, or attribute routing we need to use the route prefix or the route attribute at the controller or the action level. For conventional base routing, we need to modify the VPN config.cs file like that. Thanks for watching.

If you have any doubt, feel free to contact me