.NET Interview Questions You'll Most Likely Be Asked

5 of 5 Stars!

Price: $19.95


Microsoft .NET Framework is a key component used for development of both online and desktop applications under Windows platform. .NET Interview Questions You'll Most Likely Be Asked is a perfect companion to stand a head above the rest in today's competitive job market. Rather than going through comprehensive, textbook-sized reference guides, this book includes only the information required immediately for job search to build a career as a .NET programmer. It covers four key topics viz: ASP.net, VB.net, C# & .NET Framework. This book puts the interviewee in the driver's seat and helps them steer their way to impress the interviewer.

Table of Contents
3. C#.NET
5. Multiple Choice Questions VB.NET
6. Multiple Choice Questions ASP.NET 
7. Multiple Choice Questions C#.NET
8. Multiple Choice Questions .NET FRAMEWORK
9. HR Questions
a) 175 .NET Interview Questions, Answers and Proven Strategies for getting hired as a .NET Programmer
b) Dozens of examples to respond to interview questions
c) 51 HR Questions with Answers and Proven strategies to give specific, impressive, answers that help nail the interviews.
d) 2 Aptitude Tests Software download available
Sample from the book
(Below Questions and Answers are randomly taken from different pages of the book)
18: What is GAC? 
The Global Assembly Cache or the popular acronym GAC refers to the machine-wide code cache in any of the computers that have been installed with common language runtime. The GAC or the Global Assembly Cache in .NET Framework acts as the central place for registering assemblies.
19: What is the concept of Strong Names? 
Strong Name is basically linked with shared Assemblies. When you publish your assembly in Global Assembly Cache, you need to give strong name to that assembly. To give strong name you can use sn.exe from .net command prompt.
A Strong Name consists of the assembly's identity — its simple text name, version number, and culture information(if provided) — plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. (The assembly file contains the assembly manifest, which contains the names and hashes of all the files that make up the assembly.) 
Remember that once you give an assembly a strong name, all assemblies that reference that assembly also have to have strong names, so that the security of the strongly named assembly is not compromised.
Note: Once an assembly is created, you cannot sign it with a strong name. You can sign an assembly with a strong name only when you create it.
20: How to add and remove an assembly from GAC? 
The gacutil.exe that ships with .NET can be used to add or remove a shared assembly from the GAC.
To add a shared assembly, from the command line enter: 
gacutil.exe /i myassembly.dll
To remove a shared assembly, from the command line enter:
gacutil.exe /u myassembly.dll
Note: When viewing the GAC in Windows Explorer shfusion.dll is used to provide the user interface. You can locate and rename this DLL to view the GAC like any other folder.
21: What is Delay Signing? 
An organization can have a closely guarded key pair that developers do not have access to on a daily basis. The public key is often available, but access to the private key is restricted to only a few individuals. When developing assemblies with strong names, each assembly that references the strong-named target assembly contains the token of the public key used to give the target assembly a strong name. This requires that the public key be available during the development process.
You can use Delayed or Partial Signing at build time to reserve space in the portable executable (PE) file for the strong name signature, but defer the actual signing until some later stage (typically just before shipping the assembly) .
22: What is Garbage Collection? 
The .NET Framework's garbage collector manages the allocation and release of memory for your application. Each time you create a new object, the common language runtime allocates memory for the object from the managed heap. As long as address space is available in the managed heap, the runtime continues to allocate space for new objects. However, memory is not infinite. Eventually the garbage collector must perform a collection in order to free some memory. The garbage collector's optimizing engine determines the best time to perform a collection, based upon the allocations being made. When the garbage collector performs a collection, it checks for objects in the managed heap that are no longer being used by the application and performs the necessary operations to reclaim their memory.