Welcome to my blog on .NET, cloud, and everything else
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
When you open VS, the first thing that you notice is the Start Page. In VS 2015 the Start Page provided a useful way to open recent projects, look into tech news. But this is where it stopped. VS 2017 has totally revamped the Start Page experience. It is visually more appealing and offers more options
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
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.
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
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.
In my current engagement, we have more than 80 projects in a solution (don’t ask me why :)). Recently, as per quality guidelines, we needed to make few changes to each project. For example: Treat warnings as errors, enable code analysis for each project, sign assembly etc.
Recently, I needed to scale out my web app hosted on Virtual Machine. After a few hiccups and learnings, I was finally able to Load Balance my web app hosted over multiple Virtual Machines. I have tried to document the steps in the form of a blog here. To scale out I used following configuration: Two
Recently, I worked on a ASP.NET 4.6 MVC 5 project which didn’t have anything MVC about it. 🙂 It was a Single Page Application built on TypeScript, Knockout JS, CSS. Now, since it we didn’t have any server side code, we decided to give Gulp a try to concatenate and minify the JS and CSS
This post is Part 2 of the series – Publish web app to Azure VM. In this post I will take the application, we created in Part 1 and publish it on Azure Virtual Machine through Visual Studio Team Services.