What Great .NET Developers Ought To Know

Everyone who writes code

• Describe the difference between a Thread and a Process?
• What is a Windows Service and how does its lifecycle differ from a "standard" EXE?
• What is the maximum amount of memory any single process on Windows can address? Is this different than the maximum virtual memory for the system? How would this affect a system design?
• What is the difference between an EXE and a DLL?
• What is strong-typing versus weak-typing? Which is preferred? Why?
• Corillian's product is a "Component Container." Name at least 3 component containers that ship now with the Windows Server Family.
• What is a PID? How is it useful when troubleshooting a system?
• How many processes can listen on a single TCP/IP port?
• What is the GAC? What problem does it solve?

Mid-Level .NET Developer

• Describe the difference between Interface-oriented, Object-oriented and Aspect-oriented programming.
• Describe what an Interface is and how it’s different from a Class.
• What is Reflection?
• What is the difference between XML Web Services using ASMX and .NET Remoting using SOAP?
• Are the type system represented by XmlSchema and the CLS isomorphic?
• Conceptually, what is the difference between early-binding and late-binding?
• Is using Assembly.Load a static reference or dynamic reference?
• When would using Assembly.LoadFrom or Assembly.LoadFile be appropriate?
• What is an Asssembly Qualified Name? Is it a filename? How is it different?
• Is this valid? Assembly.Load("foo.dll");
• How is a strongly-named assembly different from one that isn’t strongly-named?
• Can DateTimes be null?
• What is the JIT? What is NGEN? What are limitations and benefits of each?
• How does the generational garbage collector in the .NET CLR manage object lifetime? What is non-deterministic finalization?
• What is the difference between Finalize() and Dispose()?
• How is the using() pattern useful? What is IDisposable? How does it support deterministic finalization?
• What does this useful command line do? tasklist /m "mscor*"
• What is the difference between in-proc and out-of-proc?
• What technology enables out-of-proc communication in .NET?
• When you’re running a component within ASP.NET, what process is it running within on Windows XP? Windows 2000? Windows 2003?

Senior Developers/Architects

• What’s wrong with a line like this? DateTime.Parse(myString);
• What are PDBs? Where must they be located for debugging to work?
• What is cyclomatic complexity and why is it important?
• Write a standard lock() plus “double check” to create a critical section around a variable access.
• What is FullTrust? Do GAC’ed assemblies have FullTrust?
• What benefit does your code receive if you decorate it with attributes demanding specific Security permissions?
• What does this do? gacutil /l | find /i "Corillian"
• What does this do? sn -t foo.dll
• What ports must be open for DCOM over a firewall? What is the purpose of Port 135?
• Contrast OOP and SOA. What are tenets of each?
• How does the XmlSerializer work? What ACL permissions does a process using it require?
• Why is catch(Exception) almost always a bad idea?
• What is the difference between Debug.Write and Trace.Write? When should each be used?
• What is the difference between a Debug and Release build? Is there a significant speed difference? Why or why not?
• Does JITting occur per-assembly or per-method? How does this affect the working set?
• Contrast the use of an abstract base class against an interface?
• What is the difference between a.Equals(b) and a == b?
• In the context of a comparison, what is object identity versus object equivalence?
• How would one do a deep copy in .NET?
• Explain current thinking around IClonable.
• What is boxing?
• Is string a value type or a reference type?
• What is the significance of the "PropertySpecified" pattern used by the XmlSerializer? What problem does it attempt to solve?
• Why are out parameters a bad idea in .NET? Are they?
• Can attributes be placed on specific parameters to a method? Why is this useful?

C# Component Developers

• Juxtapose the use of override with new. What is shadowing?
• Explain the use of virtual, sealed, override, and abstract.
• Explain the importance and use of each component of this string: Foo.Bar, Version=2.0.205.0, Culture=neutral, PublicKeyToken=593777ae2d274679d
• Explain the differences between public, protected, private and internal.
• What benefit do you get from using a Primary Interop Assembly (PIA)?
• By what mechanism does NUnit know what methods to test?
• What is the difference between: catch(Exception e){throw e;} and catch(Exception e){throw;}
• What is the difference between typeof(foo) and myFoo.GetType()?
• Explain what’s happening in the first constructor: public class c{ public c(string a) : this() {;}; public c() {;} } How is this construct useful?
• What is this? Can this be used within a static method?

ASP.NET (UI) Developers

• Describe how a browser-based Form POST becomes a Server-Side event like Button1_OnClick.
• What is a PostBack?
• What is ViewState? How is it encoded? Is it encrypted? Who uses ViewState?
• What is the element and what two ASP.NET technologies is it used for?
• What three Session State providers are available in ASP.NET 1.1? What are the pros and cons of each?
• What is Web Gardening? How would using it affect a design?
• Given one ASP.NET application, how many application objects does it have on a single proc box? A dual? A dual with Web Gardening enabled? How would this affect a design?
• Are threads reused in ASP.NET between reqeusts? Does every HttpRequest get its own thread? Should you use Thread Local storage with ASP.NET?
• Is the [ThreadStatic] attribute useful in ASP.NET? Are there side effects? Good or bad?
• Give an example of how using an HttpHandler could simplify an existing design that serves Check Images from an .aspx page.
• What kinds of events can an HttpModule subscribe to? What influence can they have on an implementation? What can be done without recompiling the ASP.NET Application?
• Describe ways to present an arbitrary endpoint (URL) and route requests to that endpoint to ASP.NET.
• Explain how cookies work. Give an example of Cookie abuse.
• Explain the importance of HttpRequest.ValidateInput()?
• What kind of data is passed via HTTP Headers?
• Juxtapose the HTTP verbs GET and POST. What is HEAD?
• Name and describe at least a half dozen HTTP Status Codes and what they express to the requesting client.
• How does if-not-modified-since work? How can it be programmatically implemented with ASP.NET?
  Explain <@OutputCache%> and the usage of VaryByParam, VaryByHeader.
• How does VaryByCustom work?
• How would one implement ASP.NET HTML output caching, caching outgoing versions of pages generated via all values of q= except where q=5 (as in http://localhost/page.aspx?q=5)?

Developers using XML

• What is the purpose of XML Namespaces?
• When is the DOM appropriate for use? When is it not? Are there size limitations?
• What is the WS-I Basic Profile and why is it important?
• Write a small XML document that uses a default namespace and a qualified (prefixed) namespace. Include elements from both namespace.
• What is the one fundamental difference between Elements and Attributes?
• What is the difference between Well-Formed XML and Valid XML?
• How would you validate XML using .NET?
• Why is this almost always a bad idea? When is it a good idea? myXmlDocument.SelectNodes("//mynode");
• Describe the difference between pull-style parsers (XmlReader) and eventing-readers (Sax)
• What is the difference between XPathDocument and XmlDocument? Describe situations where one should be used over the other.
• What is the difference between an XML "Fragment" and an XML "Document."
• What does it meant to say “the canonical” form of XML?
• Why is the XML InfoSet specification different from the Xml DOM? What does the InfoSet attempt to solve?
• Contrast DTDs versus XSDs. What are their similarities and differences? Which is preferred and why?
• Does System.Xml support DTDs? How?
• Can any XML Schema be represented as an object graph? Vice versa?

Conceptual diagram of .NET Framework

Singleton Vs Static Classes

Static classes can have only static variables which will not participate in Serialization.
Singleton classes are best in that case.

We cant always depend on order of Static Initialization. By explicitly initializing our singleton classes we can be sure that someone doesn’t destroy our carefully crafted static initialization bootstrap code by accidentally calling something when it shouldn’t be.

You can't extend static classes, but singletons you can.

For library code static classes can be nice, such as the static System.Math class in C#.

With Singleton, you can keep track of who's using it easily. This is because you need to call the getInstance() or whatever method which returns an instance of the class.

Also, because of the above, you can control the amount of actual instances. In some special cases, it might be useful to have multiple instances of the singleton class, for example for load balancing.

Static classes are stateless. If state is required Singleton can be used.

1. You can control the number of instances. ie, it's not actually *Single*ton.
2. You can sub-class a Singleton while it doesn't make sense to sub-class a class with only static methods.
3. You can control the creation of the actual instance whereas a static approach wouldn't give that flexibility.

DLL Vs EXE

exe file is a excutable file which runs in a seperate process which is managed by OS,where as a dll file is a dynamic link library which can be used in exe files and other dll files

DLL - inprocess
DLL runs along with the application which is sharing that particular DLL. If we interrupt that application that DLL also affected which in turn affects all onter applications which is using that application.

EXE - outprocess
EXE runs seperately.

In short the EXE is not resuable in other application, while the DLL is.

DLL stands for dynamic-link library and is Microsoft’s implementation of a shared library. This means that many different programs can use this library to do their tasks making it easier on the programmers so that they do not have to keep reinventing the wheel each time they write software. In simple terms a .DLL file will contain logic that other programs will use.

EXE stands for executable and denotes that a program is executable. This just means that if you double click on the file a program will run, normally with some kind of interface for a user to interact with. The file formats for EXE and DLL actually the same.

DLL: Doesn't have own main entry point, handled by other method(s).
EXE: Have own entry point, handled by OS.

Response.Redirect vs Server.Transfer

Response.Redirect should be used when:

• we want to redirect the request to some plain HTML pages on our server or to some other web server
• we don't care about causing additional roundtrips to the server on each request
• we do not need to preserve Query String and Form Variables from the original request
• we want our users to be able to see the new redirected URL where he is redirected in his browser (and be able to bookmark it if its necessary)

Server.Transfer should be used when:

• we want to transfer current page request to another .aspx page on the same server
• we want to preserve server resources and avoid the unnecessary roundtrips to the server
• we want to preserve Query String and Form Variables (optionally)
• we don't need to show the real URL where we redirected the request in the users Web Browser

HTTP Vs HTTPS

The HyperText Transfer Protocol is an application layer protocol, which means it focuses on how information is presented to the user of the computer but doesn’t care a whit about how data gets from Point A to Point B. It is stateless, which means it doesn’t attempt to remember anything about the previous Web session. This is great because there is less data to send, and that means speed. And HTTP operates on Transmission Control Protocol (TCP) Port 80 by default, meaning your computer must send and receive data through this port to use HTTP.

Secure HyperText Transfer Protocol (HTTPS) is for all practical purposes HTTP. The chief distinction is that it uses TCP Port 443 by default, so HTTP and HTTPS are two separate communications. HTTPS works in conjunction with another protocol, Secure Sockets Layer (SSL), to transport data safely. Remember, HTTP and HTTPS don’t care how the data gets to its destination. In contrast, SSL doesn’t care what the data looks like. People often use the terms HTTPS and SSL interchangeably, but this isn’t accurate. HTTPS is secure because it uses SSL to move data.
HTTPS differentiates one sender and receiver from another. SSL takes the data, going or coming, and encrypts it. This means that SSL uses a mathematical algorithm to hide the true meaning of the data. The hope is that this algorithm is so complex it is either impossible or prohibitively difficult to crack

The encryption begins when the owner of the Web site purchases a time-sensitive certificate from a trusted certificate authority such as VeriSign. You can get a certificate anywhere, or even make your own, but is it trusted? Your browser will let you know. This certificate is a security code created specifically for that one user, or even for that one Web site. The code is so complex that no one else on Earth should have a duplicate.

Getting a certificate can be an involved task. All types of information must be recorded so the issuer of the certificate can be a reliable authority on the certificate’s owner. Information that must be provided includes the name of the site and even the name of the server that hosts the site. Complexity makes counterfeiting incredibly difficult.

This makes the issuer a trusted third party. When your browser sees the secure Web site, it uses the information in the certificate to verify that the site is what it claims to be. Browsers commonly indicate security by presenting a picture of a shiny closed lock at the bottom of the screen. This process is not always perfect because of human error. Maybe 53.com is a valid banking site, but 53RD.com is not. We call that phishing. Unscrupulous people phish for careless people. So be cautious. After the identity of the Web site is accepted, the encryption is negotiated between the browser and the Web server, and the data is all but locked up tight.

Stored Procedures Vs User Defined Functions

• Stored procedures are called independently, using the EXEC command, while functions are called from within another SQL statement.
• Stored procedure allow you to enhance application security by granting users and applications permission to use stored procedures, rather than permission to access the underlying tables. Stored procedures provide the ability to restrict user actions at a much more granular level than standard SQL Server permissions. For example, if you have an inventory table that cashiers must update each time an item is sold (to decrement the inventory for that item by 1 unit), you can grant cashiers permission to use a decrement_item stored procedure, rather than allowing them to make arbitrary changes to the inventory table.
• Functions must always return a value (either a scalar value or a table). Stored procedures may return a scalar value, a table value or nothing at all.
• UDFs can't change the server environment or your operating system environment, while a SPROC can.
  
• Operationally, when T-SQL encounters an error the function stops, while T-SQL will ignore an error in a SPROC and proceed to the next statement in your code (provided you've included error handling support).
  
• You'll also find that although a SPROC can be used in an XML FOR clause, a UDF cannot be.