I will put the subjects in bullets and when i find the answers i will hyper-link them to another post where I write the answer I found.

• How exceptions are implemented by compilers? How does the assembly generated by the compiler look like?
• In public key cryptography, what is the algorithm used to raise very large numbers to very large exponents? I know it uses assembly to do bit manipulation but what is the exact algorithm.

If anyone can point me to some reference to fulfill my lust to learn about any of the subjects above, I’d appreciate it.

It’s really weird how it works as it is now. Below is an excerpt from a post found on the DotNukeForum:

How forms authentication cookies worked under asp.net 1.1

session cookies expiration = current datetime +the forms timeout value e.g. 60
persistent cookies expiration = current datetime + 50 years

 

How forms authentication cookies work under asp.net 2.0

session cookies expiration=current datetime +the forms timeout value e.g. 60
persistent cookies expiration= current datetime +the forms timeout value e.g. 60

• Use error-handling code for conditions you expect to occur; use assertions for conditions that should never occur
• Use assertions to document and verify preconditions and postconditions
• Throw exceptions at the right level of abstraction; include all information that led to the exception
• Always have a mechanism to log application errors and a way to read that log.

Note that this method will only work if you have the following registry key set to the correct value..
under HKEY_Current_User/Control Panel/Input Method, set EnableHexNumpad to 1

Use the Character Map to find the hexadecimal Unicode values for different characters.

Also, it’s worth noting that if you are using MS Word you can simply type in the Unicode hex value first and then press Alt+x. The hex number will be replaced by it’s equivalent Unicode character automagically.