Software Related Blogs

Scenario 1(New Application/Module):- Lets us assume below two classes which are exposed by a windows application:-        public   class   Multiplication     {          public   int  Multiply( int  x,  int  y)         {              return  x * y;         }     }      public   class   CalculatePower     {          public   int  RaiseTo( int  number,  int  power)         {              if  (power < 0)             {  throw   new   ArgumentException ( "Power cannot be negative" ); }              int  result=1;              Multiplication  multiply= new   Multiplication ();              for  ( int  i = 1; i <= power; i++)             {                 result = multiply.Multiply(result, number);             }              return  result;         }     } Now developer will have to wait till UI is ready for him to test his code " Hence Unit Test Is Needed In This Scenario " which will test his code without any interfa

C# since its inception has gone through many changes and new feature gets added every now and then, here is list of what every developer should try to get hands on. Most of it will be applicable for any OOP language. Principal of OOP (Inheritance/Encapsulation/Abstraction/Polymorphism). Abstract class and Interface. Generic classes and functions. SOLID principles. delegate and its use. Fun<>. Implement functional programming using C#. (Will help you understand how all this .where().select() works) Reflection. (Try to mimic ORM using reflection) var,dynamic,Tupple,ValuedTupple Most common design patterns.

What is Azure Cloud:- Microsoft has been building highly scalable applications in datacenters around the world—applications that have global reach and high availability, and offer great functionality to users. Azure allows you to take advantage of the same infrastructure to deploy your own applications, with the corresponding capabilities to reduce your maintenance requirements, maximize performance and minimize costs. Though we know that cloud adds lot of value but that only happens when it is done right and hence we need have thought of  below before taking a call:- 1. Always plan for the long-term . It’s easy to be tempted by solutions that promise immediate benefit and what looks like the quickest route to the cloud.  While the PaaS (platform as a service) approach may appear more complex, the long-term benefits such as built-in elasticity, service healing, patch management, and so forth, make it a worthwhile investment that will pay dividends both on the technology and busi