The .NET framework : At the foundation of .NET is the .NET Framework. The .NET Framework provides a standards-based, Multilanguage environment for integrating existing applications with next generation applications and services. The .NET Framework consists of three main functional areas:
- The Common Language Runtime (CLR)
- .NET Framework Class Libraries
ASP.NET has the following advantages :
- The .NET Framework currently supports over twenty languages, four of which may be used to build ASP.NET Websites.
- ASP.NET pages are compiled , not interpreted. Instead of reading and interpreting our code every time a dynamic page is requested, ASP.NET compiles dynamic pages into efficient binary files that the server can execute very quickly. This represents a big jump in performance when compared with the technology’s interpreted predecessor, ASP.
- ASP.NET has full access to the functionality of the .NET Framework. Support for XML, Web Services, database interaction, email, regular expressions, and many other technologies are built right into .NET, which saves we from having to reinvent the wheel.
- ASP.NET allows we to separate the server-side code in our pages from the HTML layout. When we’re working with a team composed of programmers and design specialists, this separation is a great help, as it lets programmers modify the server-side code without stepping on the designers' carefully crafted HTML-and vice versa.
FXCOP for code review : The .NET Framework is very powerful, which means there is great potential to create excellent applications, but there is equal opportunity to create poor programs. FXCOP is one of the tools that can be used to help create better applications by enabling you to examine an assembly and check it for compliance using a number of different rules. FXCOP comes with a set number of rules created by Microsoft, but you can also create and include your own rules. For instance, if you decided that all classes should have a default constructor that takes no arguments, you could write a rule that checks for a constructor on each class of an assembly. This way, no matter who writes the code, you will have a certain level of consistency.