ASP.NET Core I have used ASP.NET core a lot. But I wonder how I would describe it to someone who has never used it before. So I decided to give it a shot at describing in simple words what it really is. What is it? ASP.NET Core is a cross-platform, open-source framework for building modern internet connected apps that can be deployed on premises or in the cloud. Cross-platform - an asp....
Back-end developers quite often find themselves thinking about making breaking changes to their API. A change that could break the client application consuming the API. We quite often forget how easy it is to cause havoc for our clients by breaking the contract we agreed between front-end and back-end. All sorts of unintentional consequences could arise from this. We recently had a similar conversation at my workplace about how we wanted to deal with the release of a feature we had been working on in the last sprint....
I realised recently that I have always taken application logging for granted. In my previous firm, which was a pretty large company, over a few thousand employees, we had a centralised logging platform and some lovely packages for each language and a team to configure the logging instance for our application and all that luxury. Developers, did just application development. For everything else, there was always somebody you could lean on....
In my previous post, we talked about interacting with related entities using entity framework. Introduction Time to look at some special cases where you would want entity framework to work with views, stored procedures and plain old SQL statements. There is a wide minconception that developers raise, “Oh it is a stored procedure, that can’t be good”. There is nothing inherently wrong with using stored procedures. It is nice to have all business logic in one place....
In my previous post, we talked about data access and updates in entity framework. Updating Related Data A naive way to update related data, especially when the context isn’t tracking your object, as in, you send data about an existing entity in the database, from the UI, and EF has to figure out what part of the updated record has changed and needs an update in the database. If you ever encounter a situation where you are to update only one related object of a primary entity, then you might be in for a surprise....