Tag: .NET
-
One year of Motherhood
Originally posted on Deepika Vijay Blog: “A woman is a soul who carries a soul within her” Motherhood, a special feeling coupled with divine emotions, sharing the strongest bond with your child. But being a mother is not an easy job. It is probably one of the toughest jobs, which comes with new responsibility. Unlike…
-
Testing in Modern App Development
I’m back to writing blogs after a small break. Things have changed for me personally since, I have made a career move recently. I hope to be more regular going forward. In my new team, we follow Kanban flow. Our application is customer facing and due to nature of our project we need to do a…
-
Visual Studio Team Services = Git/TFS + JIRA + Team City + Octopus
Warning: The content of this post is highly opinionated. Please exercise caution. 🙂 A bit of Background Back in 2012-13, the term Dev-Ops was unheard of in my team. We were still living in dark ages where a developer would developed the code, then write unit test cases more to get the code coverage look good…
-
Visual Studio 2017 – The best IDE ever
Visual Studio 2017 was launched with much fan fare yesterday (March 7, 2017). I started exploring Visual Studio 2017 from RC and I must say, after using VS 2017 I felt I was earlier leaving in stone age. It is so much better. In short the Visual Studio 2017 is equivalent to following: VS 2017…
-
async await best practices
aysnc await is probably one of the most important features of C#. It has made the life of developers easy. It helps developers to write clean code without any callbacks which are messy and difficult to understand.
-
Clean Visual Studio Solution
Today, every project we work on big or small, easy or complex, small team or large team is probably on Source Control. The source control of course can be git, VSTS, SVN etc. Still, there are times where you need to share your code as zip in an email, or shared link. It could be because…
-
Dispose HttpClient or have a static instance?
Recently, I came across this blog post from ASP.NET Monsters which talks about correct using HttpClient. The post talks about issues of related to disposing HttpClient object for each request. As per the post calling HttpClient as below can lead to issues.