Recently, I had written a post on how I managed bring down build pipeline for entire organization. While I was at fault during that time, Team City should take the blame for this one. Background I had recently created a CI/CD pipeline for our new .NET Core project. As part of the build pipeline, I
December last year, last week before most of IT staff go on well-deserved vacation, when every team was trying to do one last deployment before code freeze, I brought down build-pipeline for almost every project in the company. Sounds scary? Here’s what happened. How it all started We are mostly a .NET shop and use
Sometime back, I had written about how to override appSettings during development in traditional ASP.NET application. Recently, we started development of a ASP.NET Core application and had a similar challenge. Our developers work on different operating systems (Windows and Mac). They have different local connection strings and application settings. We had a same problem as
Tools and tricks you can use along with Visual Studio to make your life easy as a developer:
Not too long ago, TFS and SVN were the only source control I had used. I had a very little experience of distributed source controls like Git. So when I got an opportunity to work on Git on a large scale project for the first time, I had my doubts. But, it did not take
In my workplace, our project is set up for Continuous Delivery. We do a production deployment almost daily and sometimes even more than once in a day. Ours is a fairly big solution built primarily on Microsoft technologies and Git as a Source Control. Setting up CI/ CD for your solution is easier said than