Tag | clr Posts

Assembly is the smallest unit of deployment in .NET Framework. When you compile your C# code, it will get converted into a managed module. A managed module is a standard EXE or DLL. This managed module will have the IL (Microsoft Intermediate Language) code and the metadata. Apart from this it will also have header information. The following table describes parts of a managed module. Part Description PE Header PE32 Header for 32-bit PE32+ Header for 64-bit This is a standard Windows PE header which ...
This has been pooled together from a number of resources: What is ASP.NET? Microsoft ASP.NET is a server side technology that enables programmers to build dynamic Web sites, web applications, and XML Web services. It is a part of the .NET based environment and is built on the Common Language Runtime (CLR) . So programmers can write ASP.NET code using any .NET compatible language. What are the differences between ASP.NET 1.1 and ASP.NET 2.0? A comparison chart containing the differences between ASP.NET ...
One of the best ways to understand how the CLR works internally is to have a look at the SSCLI [a.k.a Rotor] source code. In How the SSCLI [a.k.a. Rotor] managed "new" works, I have used Rotor source code to discuss what happens behind the scenes when you use the managed new operator to instantiate a managed type, discussing implications of object size, how requests from multiple threads are handled, the different validations that are done, when out-of-memory exception is thrown, etc. If you are ...
One of the new strategies for Exchange 2007 servers is to use Continuous Local or Cluster Replication (CLR or CCR) and then run the backups off of the replicated database, leaving the active one alone. However, as we know, running online backups on the database clears the transaction log files (as long as circular logging is turned off) when completed. What happens in this new scenario since backups aren’t run against the active database? Scott Schnoll, master of Exchange Server clustering, has the ...