Explore topic-wise InterviewSolutions in Current Affairs.

The steps are as follows:

1. You need to create a new ASP.NET Core Project “CalculateSum”. Open Visual Studio 2015, GOTO File–> New–> Project. SELECT the option Web in Left Pane and go for the option ASP.NET Core Web Application (.NET Core) under the central pane. Edit the project name as “CalculateSum” and click on OK.

2. In the TEMPLATE window, select Web Application and set the Authentication into “No Authentication” and click on OK.

3. Open “Solution Explorer” and right-click on the folder “Home” (It is Under Views), then click on Add New Item. You need to select MVC View Page Template under ASP.NET Section and rename it as “addition.cshtml” and then click on the Add button.

4. Open addition.cshtml and write the following code:

Here, we have created a simple form that is having two text boxes and a single Add Button. The text boxes are named as txtFirstNum and txtSecondNum. On the controller page, we can access these textboxes using:
<form asp-controller="Home" asp-action="add" method="post">

This form will indicate all the submissions will be moved to HomeController and the method add action will be executed.

5. Open the HomeController.cs and write the following code onto it:

In this program, we have added two IAction Methods addition() and add(). Addition() method will return the addition view page and add() method obtains input from the browser, processes it, and results will be kept in ViewBag.Result and then returned to the browser.

Now, press Ctrl+F5 for running your program. This will launch an ASP.NET Core WEBSITE into the browser. Add /Home/addition at the end of the link and then hit on enter. The output format is given below:

The .NET is a full-stack software development framework, which is essentially used to build large enterprise-scale and scalable software applications. The .NET framework has wide scope in the market. It is a flexible and user-friendly framework, that goes well along with other technologies.

The .NET Core was developed in response to the surge in Java popularity. The .NET Core is normally used in low-risk projects. Some of the .NET components can be used in .NET core applications (but not the other way around). This article mainly concentrates on the framework concepts of .Net and .NET Core. We are sure that it would give you sufficient information and a fair knowledge of the common questions that will be asked during an interview.

Useful Resources:

.Net Developer: Career Guide

ASP. NET Interview

C# Interview

.NET CORE is a RUNTIME and is used for the EXECUTION of an application that is built for it. Whereas ASP.NET Core is a collection of libraries that will form a framework for developing web applications. ASP.NET Core libraries can be used on .NET Core as well as on the “Full .NET Framework”.

An application using the tools and libraries of ASP.NET Core is NORMALLY referred to as “ASP.NET Core Application”, which in theory doesn’t say whether it is built for .NET Framework or .NET Core. So an application of “ASP.NET Core” can be considered as a “.NET Core Application” or a “.NET Framework Application”.

• Xamarin is an open-source platform useful in developing a modern and efficient application for iOS, Android, and Windows with .NET. It is an abstraction LAYER USED to manage the communication of shared code with fundamental platform code.
• Xamarin runs in a managed environment that gives benefits like garbage collection and memory allocation.
• Developers can share about 90% of their applications over platforms using Xamarin. This PATTERN permits developers for writing entire business logic in a single language (or reusing existing app code) but accomplish native performance, LOOK and feel on each platform. The Xamarin applications can be written on MAC or PC and then they will be compiled into native application packages, like a .ipa file on iOS, or .apk file on Android.

• Docker is an open-source PLATFORM for the development of applications, and also for shipping and running them. It allows for separating the application from the infrastructure using containers so that software can be delivered quickly. With Docker, you will be able to manage the infrastructure in the same ways you used to manage your applications.
• It supports shipping, testing, and deploying application code quickly, thus reducing the delay between code writing and running it in production.
• The Docker platform provides the ability of packaging and application execution in a LOOSELY isolated environment namely container. The isolation and security permit you for running multiple containers at the same TIME on a given host. Containers are lightweight and they include every necessary thing REQUIRED for running an application, so you need not depend on what is currently INSTALLED within the host.

.NET Core SDK is a set of tools and libraries that ALLOWS the developer to CREATE a .NET application and library for .NET 5 (also .NET Core) and later versions. It includes the .NET CLI for building applications, .NET libraries and runtime for the purpose of building and running apps, and the dotnet.exe(dotnet executable) that runs CLI COMMANDS and runs an application. Here's the LINK to download.

• CoreRT is the native runtime for the compilation of .NET natively ahead of time and it is a part of the new .NET Native (as announced in April 2014).
• It is not a virtual machine and it does not have the facility of generating and running the code on the FLY as it doesn’t INCLUDE a JIT. It has the ability for RTTI(run-time type identification) and reflection, along with that it has GC(Garbage Collector).
• The type system of the CoreRT is designed in such a way that metadata for reflection is not at all required. This feature enables to have an AOT toolchain that can link AWAY unused metadata and can identify unused APPLICATION code.

.NET Core library is used if there is a requirement to increase the SURFACE area of the .NET API which your library will ACCESS, and permit only applications of .NET Core to be compatible with your library if you are okay with it.

.NET Standard library will be used in case you need to increase the COUNT of applications that are compatible with your library and reduce surface area(a piece of code that a user can INTERACT with) of the .NET API which your library can access if you are okay with it.

The MEF(Managed Extensibility Framework) is a library that is USEFUL for developing extensible and lightweight applications. It permits application DEVELOPERS for using extensions without the need for configuration. It also allows extension developers for easier CODE encapsulation and thus avoiding FRAGILE hard dependencies. MEF will let you reuse the extensions within applications, as well as across the applications. It is an INTEGRAL part of the .NET Framework 4. It improves the maintainability, flexibility, and testability of large applications.

• Ahead-of-time(AOT) compilation is the process of compiling a high-level language into a low-level language during build-time, i.e., before program execution. AOT compilation reduces the workload during run time.
• AOT provides faster start-up time, in larger applications where most of the code executes on startup. But it needs more amount of disk space and memory or virtual address space to hold both IL(Intermediate Language) and precompiled images. In this case, the JIT(Just In Time) Compiler will do a lot of work like disk I/O actions, which are expensive.
• The explicit compilation will convert the upper-level language into object code on the execution of the program. Ahead of time(AOT) compilers are designed for ensuring whether the CPU will UNDERSTAND line-by-line code before doing any interaction with it.
• Ahead-of-Time (AOT) compilation happens only once during build time and it does not require shipping the HTML templates and the Angular compiler into the bundle. The source code generated can begin running immediately after it has been downloaded into the browser, EARLIER steps are not required. The AOT compilation will turn the HTML template into the runnable code FRAGMENT. AOT will analyze and compile our templates statically during build time.

Benefits of AOT Compilation:

• Application size is smaller because the Compiler itself isn’t shipped and unused features can be removed.
• Template the parse errors that are detected previously(during build time)
• Security is high (not required to dynamically evaluate templates)
• Rendering of a component is faster (pre-compiled templates)
• For AOT compilation, some tools are required to accomplish it automatically in the build process.

• Middleware is software assembled into an application pipeline for request and response handling. Each component will choose whether the request should be passed to the next component within the pipeline, also it can carry out work before and after the next component within the pipeline.
• For EXAMPLE, we can have a middleware component for user authentication, another middleware for handling errors, and one more middleware for serving static files like JavaScript files, images, CSS files, etc.
• It can be built-in into the .NET Core framework, which can be added through NuGet packages. These middleware components are built as part of the CONFIGURE method’s application startup class. In the ASP.NET Core application, these Configure methods will set up a request processing pipeline. It CONTAINS a sequence of request delegates that are called one after another.
• Normally, each middleware will handle the incoming requests and passes the response to the next middleware for processing. A middleware component can take the decision of not calling the next middleware in the pipeline. This process is known as short-circuiting the pipeline or terminating the request pipeline. This process is very helpful as it avoids unnecessary work. For example, if the request is made for a static file such as a CSS file, image, or JavaScript file, etc., these static files middleware can process and SERVE the request and thus short-circuit the remaining pipeline.

Here, there are three middlewares are associated with an ASP.NET Core web application. They can be either middleware provided by the framework, added through NuGet, or your own custom middleware. The HTTP request will be added or modified by each middleware and control will be optionally passed to the next middleware and a FINAL response will be generated on the execution of all middleware components.

The .NET Core Framework is composed of the following components:

• CLI Tools: Command Line Interface(CLI) tools is a cross-PLATFORM tool for developing, building, executing, restoring packages, and publishing. It is ALSO capable of building Console applications and class libraries that can run on the entire .NET framework. It is installed along with .NET Core SDK for the selected platforms. So it does not require SEPARATE installation on the development machine. We can verify for the proper CLI installation by typing dotnet on the command prompt of Windows and then pressing Enter. If usage and help-related texts are displayed, then we can conclude that CLI is installed properly.
• Roslyn(.NET Compiler platform): It is a set of an open-source language compiler and also has code analysis API for the C# and Visual Basic (VB.NET) programming languages. Roslyn exposes modules for dynamic compilation to Common Intermediate Language(CLI), syntactic (lexical) and semantic code analysis, and also code emission.
• CoreFX: CoreFX is a set of framework libraries. It consists of the new BCL(Base Class LIBRARY) i.e. System.* things like System.Xml, System.Collections, etc.
• CoreCLR: A JIT(Just In Time) based CLR (Command Language Runtime). CoreCLR is the runtime implementation that runs on cross-platform and has the GC, RyuJIT, NATIVE interop, etc.

Universal Windows Platform(UWP) is one of the methods used to create client applications for Windows. UWP apps will make use of WinRT APIs for providing POWERFUL UI as WELL as features of advanced asynchronous that are ideal for devices with internet connections.

Features of UWP apps:

• Secure: UWP apps will specify which resources of device and data are accessed by them.
• It is possible to use a common API on all devices(that run on Windows 10).
• It enables us to use the specific capabilities of the device and adapt the user interface(UI) to different device screen SIZES, DPI(Dots Per Inches), and resolutions.
• It is available on the Microsoft Store on all or specified devices that run on Windows 10.
• We can INSTALL and uninstall these apps without any risk to the machine/incurring “machine rot”.
• Engaging: It uses live tiles, user activities, and push notifications, that interact with the Timeline of Windows as well as with Cortana’s Pick Up Where I Left Off, for engaging users.
• It can be programmable in C++, C#, Javascript, and Visual Basic. For UI, you can make use of WinUI, HTML, XAML, or DirectX.

MSBuild is the free and OPEN-source development platform for Visual Studio and Microsoft. It is a build tool that is helpful in automating the software product creation process, ALONG with source code compilation, packaging, testing, deployment, and documentation creation. Using MSBuild, we can build Visual Studio PROJECTS and solutions without the need of installing the Visual Studio IDE.

In the Universal Windows Platform(UWP) app, if you open the folder named project, you will get to see both files namely project.json and *.csproj. But if you open our previous CONSOLE APPLICATION in .NET Core, you will get to see project.json and *.xproj files.

No. The Trace class is USED for debugging as well as for certain build releases. It gives execution plan and PROCESS timing details. While debug is used mainly for debugging. Debug means GOING through the program code FLOW during execution time.

Debug and trace ALLOW for monitoring of the application for errors and exceptions without VS.NET IDE.

Transfer-encoding is USED for transferring the payload body(information part of the data sent in the HTTP message body) to the user. It is a hop-by-hop header, that is APPLIED not to a resource itself, but to a message between two nodes. Each multi-node connection segment can make USE of various Transfer-encoding values.

Transfer-encoding is SET to “Chunked” SPECIFYING that Hypertext Transfer Protocol’s mechanism of Chunked encoding data transfer is initiated in which data will be sent in a form of a series of “chunks”. This is helpful when the amount of data sent to the client is larger and the total size of the response will not be known until the completion of request processing.

Common TYPE System(CTS) standardizes all the datatypes that can be used by different programming languages under the .NET framework.

CTS has two TYPES. They are:

1. Value Types: They contain the values that are stored on a stack or allocated inline within a structure. They are divided into :
   • Built-in Value Types - It includes primitive data types such as Boolean, Byte, Char, Int32, ETC.
   • User-defined Value Types - These are defined by the user in the source code. It can be enumeration or structure.
   • Enumerations - It is a set of enumerated values stored in the form of numeric type and are represented by labels.
   • Structures - It defines both data(fields of the structure) and the methods(operations performed on that data) of the structure. In .NET, all primitive data types like Boolean, Byte, Char, DateTime, Decimal, etc., are defined as structures.
2. Reference Types: It Stores a reference to the memory address of a value and is stored on the heap. They are divided into :
   • Interface types - It is used to implement functionalities such as testing for equality, comparing and sorting, etc.
   • Pointer types - It is a variable that holds the address of another variable.
   • Self-describing types - It is a data type that gives information about themselves for the sake of garbage collectors. It includes arrays(collection of variables with the same datatype stored under a single name) and class types(they define the operations like methods, properties, or events that are performed by an object and the data that the object contains) like user-defined classes, boxed value types, and delegates(used for event handlers and callback FUNCTIONS).

It’s useful to generate a SQL script, WHENEVER you are trying to debug or DEPLOY your migrations to a PRODUCTION database. The SQL script can be used in the FUTURE for REVIEWING the accuracy of data and tuned to fit the production database requirement.

IGCToCLR interface will be PASSED as an argument to the InitializeGarbageCollector() function and it is USED for runtime COMMUNICATION. It CONSISTS of a lot of built-in methods such as RestartEE(), SuspendEE(), etc.

COREFX is the set of CLASS library implementations for .NET Core. It includes collection TYPES, CONSOLE, file systems, XML, JSON, ASYNC, etc. It is platform-neutral code, which means it can be shared across all platforms. Platform-neutral code is implemented in the form of a single portable assembly that can be used on all platforms.

Zero GARBAGE Collectors allows you for object allocation as this is required by the Execution Engine. Created objects will not get deleted automatically and theoretically, no longer required memory is never reclaimed.

There are TWO main USES of Zero Garbage Collectors. They are:

• Using this, you can develop your own Garbage Collection mechanism. It provides the necessary FUNCTIONALITIES for properly doing the runtime work.
• It can be USED in special use cases like very short living applications or almost no memory allocation(concepts such as No-alloc or Zero-alloc programming). In these cases, Garbage Collection overhead is not required and it is better to get rid of it.

WEBHOSTBUILDER function is used for HTTP pipeline creation through webHostBuilder.Use() chaining all at once with WebHostBuilder.BUILD() by using the BUILDER pattern. This function is provided by Microsoft.AspNet.HOSTING namespace. The Build() method’s purpose is building necessary services and a Microsoft.AspNetCore.Hosting.IWebHost for hosting a web application.

CoreCLR is the run-time execution engine provided by the .NET Core. It consists of a JIT COMPILER, garbage collector, low-level classes, and primitive data types. .NET Core is a modular implementation of .NET, and can be used as the base stack for large scenario types, ranging from console utilities to WEB applications in the cloud.

Here, various programming languages will be compiled by respective compilers(Roslyn can compile both C# and VB code as it includes C# and VB compilers) and Common Intermediate Language(CIL) code will be generated. When the application execution BEGINS, this CIL code is compiled into native machine code by using a JIT compiler included within CoreCLR. This CoreCLR is supported by many OPERATING systems such as Windows, Linux, etc.

C# is a general-purpose and object-oriented programming language from Microsoft that runs on the .NET platform. It is designed for CLI(Common Language Infrastructure), which has executable code and a RUNTIME environment that allows for the usage of different high-level languages on various computer platforms and architectures. It is mainly used for DEVELOPING web applications, desktop applications, mobile applications, database applications, games, etc.

F# is an open-source, functional-first, object-oriented and, cross-platform programming language that runs on a .NET platform and is used for writing robust, SUCCINCT, and performant code. We can say that F# is data-oriented because here code involves transforming data with functions. It is mainly used in MAKING scientific models, artificial intelligence research work, mathematical problem SOLVING, financial modelling, GUI games, CPU design, compiler programming, etc.

• .NET Core is useful in the server application creations, that run on various operating systems like Windows, Mac, and LINUX. Using this, developers can WRITE libraries as well as applications in C#, F#, and VB.NET in both runtimes.
• Generally, it is used for cloud applications or for modifying LARGE enterprise applications into microservices.
• .NET Core 3.0 supports cross-development between WPF, UWP, and Windows Forms.
• .NET Core supports microservices, which PERMITS cross-platform services to work with the .NET Core framework including services developed with .NET Framework, RUBY, Java, etc.
• .NET Core’s features like lightweight, modularity, and flexibility make it easier to deploy .NET Core applications in containers. These containers can be deployed on any platform, Linux, cloud, and Windows.

.NET Core can be SAID as the newer version of the .NET Framework. It is a cost-free, general-purpose, open-source application development PLATFORM provided by Microsoft. It is a cross-platform framework because it runs on various operating systems such as Windows, LINUX, and macOS. This Framework can be used to develop applications LIKE mobile, web, IoT, machine learning, game, cloud, microservices, etc.

It consists of important features like a cross-platform, sharable library, etc., that are necessary for running a basic .NET Core application. The remaining features are supplied in the form of NuGet packages, that can be added to your application according to your needs. Like this we can say, the .NET Core will boost up the performance of an application, decreases the memory footprint, and becomes easier for maintenance of an application. It follows the modular approach, so instead of the entire .NET Framework installation, your application can install or use only what is required.