Why this podcast? Dotnet Bees

Hey Everyone, Thank you for tuning in and you are listening to Prashant where I will talk about dotnet and related Technologies. Today I have taken up a very interesting topic called WEB API. We will try to understand what is web API? And why it’s been brought in to the web development? As per Wikipedia API is the Application Programming Interface for either a web server or web browser. Before we jump into what is web API let’s try to understand how the web applications used to work before web API.  Initial days of web application development both the presentation layer and server-side code has to have in the same project. Such tight coupling of server-side and client-side code did not allow developers to work separately. Until and unless the work of BE did not complete, the work of FE could not be started. This tight coupling also restricted the use of multiple tech stacks into the product. Deployment of such applications became pain since it was not possible to deploy presentation and server code into a different machine.  They had to have the same machine.  Which resulted in less utilization of server resources and increased the cost of deployment. The major problem with such an approach was after a certain time adding new and removing Any feature from the product became very difficult.  It was hard to understand the system for new developers. All such delays and costs resulted in a huge revenue decline for software companies. Then the concept of WEB API evolved. It promised to bring clear separation into the product code. If someone wants to develop server-side code in dotnet core then for the presentations layer the code can be developed in any language. It provided flexibility in choosing the tech stack and also  It can be reused in the different presentation layer. This means once the product functionality is written it can be consumed by any presentation layer. WEB API also solved the problem of deployment where both presentation and server code could be deployed in the different cloud servers. Web API also allowed developers of both UI and BE to work independently. Now next question comes how WEB API able to solve this problem? Server-side code will expose endpoint which could be consumed by the presentation layer using HTTP or SOAP Endpoints are nothing but a URI using which any interface can consume data or post data to the server. WEB API brought a drastic change in the way web applications used to look before.  I hope I have covered most of the things in the basics of WEB API. Stay tuned will bring some more interesting topics for you. Till then stay happy and keep sharing the knowledge.

Hey Everyone, Thank you for tuning in, you are listening to Prashant and here I will talk only about dotnet and sometimes other technologies as well Today we are going to talk about what is MVC and I am not going to tell you the definition but I will try to convey it by some interesting story We will try to connect why we needed MVC as architecture? What was the problem which we were facing while developing code before MVC If you are someone who wrote code for windows forms and web forms then you can relate much but I will try to cover basics so that newbies can also understand. Let’s take real estate example to explain MVC, There was a rich guy he wanted to build a 60 floors building in between the city and he asked his architects to design the building structure. Architects came up with the design and they build a 60-floor building in the city.  the building became very popular in the state and people from different states started to come and visit the building. One day geology department broadcasted a warning for an earthquake. It created panic in builders and architects on how to safeguard the building, they tried to find many solutions but nothing was promising because of building size. They couldn't save the building in an earthquake. It was a huge loss for a builder and all those people who were living in that apartment. After that loss, they thought about the mistakes they made while designing and architecting the building. Next year they planned to rebuild the building, this time they decided to build three-building instead of one and implement different design internally to protect them in such calamities. The same year again earthquake came and one of their building affected little but the other two were safe.  One thing which we can draw from the story and implement in software is by keeping pieces apart relative to their use cases will save us if anything fails. So a bigger building is nothing but web forms and three smaller building are MVC MVC stands for the Model view controller Where Model consists of all the business-related logic adding manipulation data etc The view contains the presentation layer  The controller is the mediator between the model and view. In dotnet core, MVC pattern is been used heavily and this architecture has changed the way we thought about software architecture and deployment model. This is all about MVC, Thank you for tuning in. Will meet you in next episode till then keep sharing the knowledge

Hey Everyone, In this episode i have talked about what is difference between dotnet core and dotnet framework. Since dotnet framework and dotnet core has vast difference i have only talked about the differences which are very common: Dotnet core is open source  Dotnet core is lean  Dotnet core is cross platform Dotnet application can be developed in any IDE If you like the podcast please provide your feedback on instagram @techprashant. Thank you have a wonderful day ahead

Hey Everyone,  I hope each and everyone of you are doing good… In todays podcast we will be talking about how to become a dotnet developer If you haven't heard the Part 1 I would recommend to listen that first. Now after learning C# and OOPS you are very close to start working with dotnet Before you jump on dotnet let me tell you some background of dotnet and then you can start learning about it.First question which comes to mind is What is dotnet ? It is framework created by Microsoft to help developers to focus more on logic than to worrying about memory and other Resources. Job of framework is to provide an abstraction layer on top of the inner and complex implementation of memory allocation, de allocation, threading and many other such cases. In current market donet has two major versions Dotnet Framwork and Dotnet core. Let’s try to understand what are they. Dotnet framwork is the initial implementation of dotnet . It was launched on 13 Feb 2002 and after that many version of it came. Dotnet framework was not free. To develop dotnet framework applications we needed Visual Studio. Most of the big enterprises adopted framework and developed many big application. Dotnet framework was successful until most of the developer and big enterprises started moving toward open source frameworks. This change in mentality forced Microsoft to develop a framework which should be open source. In June 2016 they launch dotnet core which was open source and it did not required any specific IDE. Dotnet core support most of the things which were supported in dotnet framework. In current market dotnet core is very trendy because most of the big enterprise applications are now migrating from framework to core. In the next podcast I will talk about main difference between dotnet core and dotnet framework. If you like the podcast provide reviews. It will motivate me to bring and make changes to the content. Thank You for listening will meet you in next episode. Till then stay happy and keep learning

Hey Everyone, I hope each and everyone of you are doing good In todays podcast we will be talking about how to become a dotnet developer, I will divide this topic into multiple episode In this episode I will talk about the language and concept which you need to learn in order to work with dotnet Dotnet supports multiple language like F#, C# , Visual Basics etc… Among all these, most popular language is C# So your first job is to learn C#… There are N number of tutorials on YouTube and many other tutorial sites which you can refer. Once you are done with the basic of c# , you have to deep dive into Object Oriented Programming Concepts. Now most of you might be thinking how much time it will take to learn these two concepts.. So learning depends on how much time you are putting daily… As per my experience it will take 3 months max if you will read 6hr weekly and it will increase if you decrease weekly learning hours Once you are done with two concepts, note down basics of C#. This will help you to quickly look for term when you start developing an application. Let me wrap up the episode by concluding points Learn C# Learn OOPS Make note of basic concepts of C# and OOPS Thank You for listening will meet you in next episode. Till then stay happy and keep learning

Hey Everyone, My name is Prashant Maurya and I have started this podcast to help aspiring dotnet developers to achieve big into dot net development. As a listener you will be getting latest dotnet updates, tips and tricks and many more related to dotnet You will also be hearing experts talking about dotnet and interview questions. Please like and share podcast to other dotnet developers Let’s learn and grow together. Thank you for listening