Microsoft .NET Framework for Windows Server 2008Microsoft .NET Framework for Windows Server 2008The word .NET refers not to a network as in computing, but to a net as in fishing. The Framework component acts as a guide for developers to build their applications. For ordinary users all they need to know is that .NET Framework takes care of scripting business. Incidentally, my killer reason for installing .NET Framework was to support PowerShell commands. Topics for Microsoft .NET Framework
.NET Framework Library ClassesIf you are a developer, a PowerShell script writer, or just plain curious, then there is a whole lot more to .NET Framework. One useful concept is that of a library, and in that library are categories or classes. Each class defines a type of objects, which in turn developers use to build applications. ASP.NET, this is one of the original classes, used for making websites interactive. There is now also a .NET class called Web Services Enhancements. Windows Presentation Foundation (WPF), for creating visually stunning effects on XP and especially on Vista. Windows Communication Foundation (WCF), enabling applications to talk to one another across your network. Goals include: secure, reliable, and transaction-based messaging. Windows Workflow Foundation (WF), to make those strange workflows diagrams a reality. Windows CardSpace, to manage digital identity. Additional library classes for XML, cryptography and text-to-speech. Every few months another library class is being added or extended for example: data and IO. Name check .NET Framework was originally WinFX. The Place of .NET Framework in Computing.NET Framework GoalsThe primary goal of .NET Framework is to provide a library of tried and tested objects. The .NET code can be executed locally or remotely, thus security has been a major consideration in developing communication between the various elements. In addition to classes library, there is a common and consistent runtime component that manages communication with the underlying operating system. This runtime component not only checks the developer's code, but also negotiates memory and other system resources on behalf of the .NET application. One way of looking at this CLR (Common Language Runtime) is as a virtual machine for the developer and their application. On reflection, Framework is a good choice of word because it reflects the library with its variety of object classes. Microsoft's Framework then encourages developers to build useful tools, applets or even major applications for we users. Another design feature of .NET Framework is that once a program is perfected, it will work on any operating system. This is because the CIL (Common Intermediate Language) can be compiled into any native code. .NET Framework ExamplesHere are examples of developers using .NET Framework to solve a particular problem. The problems may seem trivial, but they were annoying as there was no existing technology to achieve the particular solution.
The Great .NET Framework DivideThere really is a huge chasm between ordinary users, who simply take advantage of .NET Framework, and developers. What the developers do is select elements of the above classes, and using their skills, build handy tools for the rest of us. In between these two groups are techies who install .NET Framework on servers or desktops so that we can take advantage of those tools that the developers made. Like the users, these techies don't need to understand stuff like WPF, or WCF.
Guy Recommends: SolarWinds LANSurveyor
|
|||||
|
|
Guy Recommends: GFi EventsManagerLet GFI EventsManager do the dirty work! Have event logs monitored automatically and get warned about critical events! Download a copy here |
|
Home Copyright Β© 1999-2009 Computer Performance LTD All rights reserved Please report a broken link, or an error.
| |