• +91 9971497814
  • info@interviewmaterial.com

Computer Interview Questions Answers

DotNet Interview Questions Answers

Question - 11 : - Why only boxed types can be unboxed?.

Answer - 11 : -   Unboxing is the process of converting a Reference type variable to Value type and thus allocating memory on the stack . It happens only to those Reference type variables that have been earlier created by Boxing of a Value Type , therefore internally they contain a value type , which can be obtained through explicit casting . For any other Reference type , they don’t internally contain a Value type to Unboxed via explicit casting . This is why only boxed types can be unboxed .

Question - 12 : -   How is the DLL Hell problem solved in .NET?

Answer - 12 : - Assembly versioning allows the application to specify not only the library it needs to run (which was available under Win32), but also the version of the assembly.

Question - 13 : - What’s the use of System.Diagnostics.Process class?

Answer - 13 : - By using System.Diagnostics.Process class, we can provide access to the files which are presented in the local and remote system.

Question - 14 : - What is the use of Internal keyword?.

Answer - 14 : -   Internal keyword is one of the access specifier available in .Net framework , that makes a type visible in a  given assembly , for e.g : a single dll can contain multiple modules , essentially a multi file assembly , but it forms a single binary component , so any type with internal keyword will be visible throughout the assembly and can be used in any of the modules .

Question - 15 : - How many languages .NET is supporting now?

Answer - 15 : - When .NET was introduced it came with several languages. VB.NET, C#, COBOL and Perl, etc. The site DotNetLanguages.Net says 44 languages are supported.

Question - 16 : -   How is a strongly-named assembly different from one that isn’t strongly-named?

Answer - 16 : -   Strong names are used to enable the stricter naming requirements associated with shared assemblies. These strong names are created by a .NET utility – sn.exe Strong names have three goals: · Name uniqueness. Shared assemblies must have names that are globally unique. · Prevent name spoofing. Developers don't want someone else releasing a subsequent version of one of your assemblies and falsely claim it came from you, either by accident or intentionally. · Provide identity on reference. When resolving a reference to an assembly, strong names are used to guarantee the assembly that is loaded came from the expected publisher. Strong names are implemented using standard public key cryptography. In general, the process works as follows: The author of an assembly generates a key pair (or uses an existing one), signs the file containing the manifest with the private key, and makes the public key available to callers. When references are made to the assembly, Previous Next

Computer Contributors

Rajeev Katiyar
Yes Baroda

Share your email for latest updates


Our partners

Copyright 2017, All Rights Reserved. A Product Design BY CoreNet Web Technology