Wipro DOT NET Developer Interview Questions and Answers for Experienced

Solid Principles are a set of five design principles for writing clean, maintainable, and scalable code.

• Single Responsibility Principle (SRP) - A class should have only one reason to change.

• Open/Closed Principle (OCP) - Classes should be open for extension but closed for modification.

• Liskov Substitution Principle (LSP) - Objects of a superclass should be replaceable with objects of its subclasses without affecting the ...read more

Dependency Injection is a design pattern where dependencies are injected into a class rather than created within the class.

• Dependency Injection helps in achieving loose coupling between classes.

• It allows for easier testing by enabling mocking of dependencies.

• There are different ways to implement Dependency Injection such as constructor injection, property injection, and method injection.

• Popular DI containers/frameworks

Configuration settings can be stored in various places such as appsettings.json, environment variables, database, or Azure Key Vault.

• appsettings.json file in ASP.NET Core projects

• Environment variables for sensitive data

• Database for dynamic configuration

• Azure Key Vault for secure storage

Sheiks class is a class in C# that allows for secure communication over a network using SSL/TLS protocols.

• Sheiks class is part of the System.Security.Cryptography namespace in C#.

• It provides methods for creating secure channels for communication.

• It can be used to implement secure client-server communication in applications.

• Examples include using Sheiks class to encrypt data sent over a network or to authenticate client

Shield class is used for encapsulating sensitive data and providing controlled access to it.

• Shield class helps in protecting sensitive data from unauthorized access.

• It allows for controlled access to the data through defined methods.

• Examples include encrypting passwords in a Shield class to prevent direct access.

MVC architecture is a software design pattern that separates an application into three main components: Model, View, and Controller.

• Model represents the data and business logic of the application

• View is responsible for displaying the data to the user

• Controller acts as an intermediary between Model and View, handling user input and updating the Model accordingly

• MVC helps in achieving separation of concerns, making the c

SQL joins are used to combine rows from two or more tables based on a related column between them.

• Use INNER JOIN to return rows when there is at least one match in both tables

• Use LEFT JOIN to return all rows from the left table, and the matched rows from the right table

• Use RIGHT JOIN to return all rows from the right table, and the matched rows from the left table

• Use FULL JOIN to return rows when there is a match in on

DI concept in .NET Core allows for loosely coupled components by injecting dependencies at runtime.

• DI stands for Dependency Injection

• It helps in achieving Inversion of Control (IoC)

• Reduces tight coupling between components

• Improves testability and maintainability of code

• Example: Services are injected into controllers in ASP.NET Core