The .NET Framework introduces a wholly new concept of security

The .NET Framework introduces a wholly new concept of security (at least for those steeped in the Windows tradition). Instead of basing security on objects, it’s based on tasks. That’s a gross, somewhat inaccurate generalization, so don’t take our word for it. Instead, read Don Box’s article on .NET security.

Several attacks in the past year have targeted servers running Microsoft Internet Information Services (IIS). No matter how safe a system is, the more ports you leave open, the more chances a hacker has to find a hole. Windows .NET Server will ship with IIS 6.0, which showcases several key security advances. Use some of these new features and compare them to the way you did things in IIS 5.0. surely you will learn a lot.

Today, there are many different flavors of Windows: Windows 95, Windows 98, Windows 98 SE, Windows Me, Windows NT® 4.0, Windows 2000 (with various service packs), Windows CE, and soon a 64-bit version of Windows 2000. Most of these systems run on x86 CPUs, but Windows CE and 64-bit Windows run on non-x86 CPUs. Once written and built, a managed .NET application (that consists entirely of managed code, as I’ll explain shortly) can execute on any platform that supports the .NET common language runtime. It is even possible that a version of the common language runtime could be built for platforms other than Windows in the future. Users will immediately appreciate the value of this broad execution model when they need to support multiple computing hardware configurations or operating systems.

For complete guide refer http://msdn.microsoft.com/msdnmag/issues/0900/Framework/ 

Related posts

• Source Code for the .NET Framework Libraries (0)
• Knowledge of language features, “Operator Overloading “ (0)
• “Live From Redmond” Webcast series (0)
• Zimbra Toaster email services for mac (0)
• you may be the victim of software counterfeit (0)