.NET Planet

  Interviewer : What is .NET framework ? You :  It is collection of many small technologies integrated as a single large technology such that very powerful applications can be developed. Interviewer : What are the .NET components and explain in detail ? You : CLR: Common Language Runtime, CLR plays a main role in the .NET framework, It is a runtime environment in the .NET framework When .NET program is compiled , the output of the compiler is not executable file but a file that contains a special type of code called MSIL ( Microsoft Intermediate Language) also called as Common Intermediate Language (CIL) The Job of CLR is to convert IL file to executable code i.e native OS understandable format CLR is responsible for managing the compile codes of .NET application , Memory management , type checking These tasks can be done by using CTS CLS JIT Garbage Collector CTS: It is a collection of type definition provided by the .NET framework which has to be supported by all the languages which

Interviewer : What are the design patterns you have used in your project ? Can you explain the use case ? You: I have used Dependency Injection design patterns and Singleton design patterns in my projects so far Interviewer : Can you explain Dependency Injection design pattern in short and use case ? You:  Dependency Injection design pattern that takes away the responsibility of creating dependencies from a class that way we can achieve the loosely coupled system. Let me give an simple example : When you are implementing logging , we have a logger class and in that class if you are creating an object for the database helper class (storing the information in the database)  in the constructor of the logger class. In this scenario logger class is depending upon the database helper class      The problem with this design is Logger class and Database helper class is tightly coupled  To avoid this we need to use the DIP ( dependency Inversion Principle ) , it means high level mo

  Interviewer : Why should we use SOLID principles ? Can you explain about SOLID design Principles ? You : SOLID design principles are used to develop the code in an efficient way and also it gives the benefits  Flexible, Maintainable and Understandable code. SOLID design principles are  S : Single Responsibility Principle (SRP) O : Open Closed Principle (OCP) L : Liskov Substitution Principle (LSP) I : Interface Segregation Principle (ISP) D : Dependency Inversion Principle (DIP)  SRP : class/module should have handle single unit of work E.g : When you are implementing a Login page, we have some Register/Email/Error functionalities instead of maintaining all methods in the ILogin interface. Create separate Interfaces for all the single unit of work IRegister/IEmail/IError. Code looks cleaner and easy to handle OCP : class/module should be open for extension and close for the modification E.g : Suppose we have a CalculateBonus() method in Employee class and implemented for Temporary an

 Interface Segregation Principle (ISP) Interface Segregation Principle states that "Client should not force to implement any method/functionality which is not required" at the same time one fat interface can be split into smaller interface so that clients can know about the interfaces that are relevant to them   Implementation :  Suppose we are implementing a functionality as per business they are doing transportation in 3 ways like on road, on ship and on air , so for that we have created an interface    so the problem comes when we are implementing Car class it supports only OnRoad() functionality the other two functionalities are not supported. So to overcome the above issue and Implementing Interface Segregation Principle, we can split fat interface into smaller  So after implementing Interface Segregation Principle so the code looks like this So this is the conclusion. Always remember when we implementing any functionality try to make simple if we are making a habit , wh

Interviewer: Can you explain about yourself and technical experience? You: Hi, I am Satish, I have around 10 years of Work experience in Microsoft Technologies mainly in C#, ASP.NET and SQL Server. I have good exposure on creating Web applications and windows application with different domains like logistics, financial and Health care. I have been working in Company name for the past 2 years and my current project is Project name. Coming to my technical experience so far I have involved in all phases of the projects like designing, developing, testing and deploying activities. In this current project my key responsibilities are Involved in coding and developing functionalities. Involved in bug fixes and resolving PEN Test Issues Involved in implementing Thycotic server and Logging using log4net and integration with Application insight.  we are making sure to coverage Unit test cases for all the fixes/enhancements we have done. This is pretty much from my side. Cross Questions: Intervi

Single Responsibility Responsible Principle ( SRP ) The name itself explaining the concept , the class/module should have handle single unit of work. Rather than handling multiple components in class/module/functionality. Benefits : Code becoming understandable Better design Less chance to code become complex (code is less fragile) Implementation : For example if we are implementing a login page we need maintain a user information, email notification, Logging exceptions  Code before SRP  If you observe above code all the functionalities related to login page included in one interface so we need to break the functionalities into single task. Let's have a look after implementing Single Responsibility Principle So at a glance always use a module should have a single reason to change the class/interface/function/module

 Let me introduce about myself I'm Satish and I have 12 years of experience in Microsoft Technologies   I completed more than 10 projects in  C# .NET in Major IT firms I have involved in each and every phase of the project Designing,  Development, Testing, Deployment Reason to Start a blog:   I have attend so many interview while changing the companies initially I have also interview phobia I guess many of us having the same problem. One thing to clear the interview is quite simple if you prepare right questions and explain in a proper way  So I just want to help the candidates to clear the interview by providing real time scenarios with Concepts. I give the support to candidates those who are struggling to complete day-to-day activities/tasks on daily basis Services I can offer Interview Guidance in .NET (C#, ASP.NET, SQL Server) Support to Onsite candidates Fixing the issues on .NET  Website Development Please reach out to me at nilla.satish@gmail.com