Welcome to my blog

Background: Software quality is not limited to testing for strong validations, security and vulnerabilities but also depends upon its architecture, coding standards, and defined business logics. Quality assurance (QA) generally does by separate quality team in software industries and qualifies it after validations, security, vulnerabilities and performance testing. Testers do not have any idea about coding standards and business structures used behind the scene. Now the question arises, if coding guidelines and business structure are not defined properly then does the software will be really a quality product? Object oriented (OO) concepts are not a piece of cake. Understanding, coding and managing software program in object oriented paradigm (OOPs) is really a big challenge in software development. Consider you are the lead of a project and numbers of programmers are programming. Your assigned project is really big, then how you will assure about its quality in terms

ASP.Net MVC ERROR: The type or namespace name 'Ajax' does not exist in the namespace 'System.Web.Mvc' (are you missing an assembly reference?) Solution: Right click on respective referenced .dll, go to 'Properties', set property Copy Local = True, and then rebuild.

Entity Framework ERROR: Cannot convert from 'System.Data.Objects.ObjectParameter' to 'System.Data.Entity.Core.Objects.ObjectParameter[]' entity framework 6 This is one of most frequent compile time error you may face in Entity Framework. This is because either of: 1. Version conflict or 2. Namespace used. By default, while compiling project, framework includes namespace using System . Data . Objects ; Solution: To fix this issue: If version conflicts, install package for respective version of EF. If version is same, change the above namespace to  System . Data . Entity . Core . Objects