ASP.Net Web Developer Guide |
||||||||
|
||||||||
Sitemap : Content in Chapter 1 |
Content in Chapter 2 |
Content in Chapter 3 |
||||||||
|
||||||||
Saturday, January 21, 2006
Utilizing the Flexibility of ASP.NET (Chapter 1)
With the .NET Framework and ASP.NET, Microsoft has not just shown itself to be a contender in Web development technologies, but many commentators also believe Microsoft has taken the lead.ASP.NET is well equipped for any task you want to put to it, from building intranets to e-business or e-commerce mega sites.
Microsoft has been very careful to include the functionality and flexibility developers will require, while maintaining the easy-to-use nature of ASP.
Microsoft has been very careful to include the functionality and flexibility developers will require, while maintaining the easy-to-use nature of ASP.
- With ASP.NET you now have a true choice of languages. All the .NET languages have access to the same foundation class libraries, the same type of systems, equal object orientation and inheritance abilities, and full interoperability with existing COM components.
- You can use the same knowledge and code investment for everything from Web development to component development or enterprise systems, and developers do not have to be concerned about differences in APIs or variable type conversions, or even deployment.
- ASP.NET incorporates all the important standards of our time, such as XML and SOAP, plus with ADO.NET and the foundation class libraries, they are arguably easier to implement than in any other technology, including Java.
- An ASP.NET programmer still only needs a computer with Notepad and the ability to FTP to write ASP code, but now with the .NET Framework command-line tools and the platform’s XML-based configuration, this is truer than before!
- Microsoft has included in the .NET Framework an incredibly rich feature set of library classes, from network-handling functions for dealing with Transmission Control Protocol/Internet Protocol (TCP/IP) and Domain Name System (DNS), through to XML data and Web Services, to graphic drawing.
- In the past, the limitations of ASP scripting meant components were required for functionality reasons, not just for architectural reasons. ASP.NET has access to the same functionality and uses the same languages in which you would create components, so now components are an architectural choice only.
- A .NET developer is shielded from changes in the underlying operating system and API, as the .NET technologies deal with how your code is implemented; and with the Common Type System, you don’t have to worry whether the component you are building uses a different implementation of a string or integer to the language it will be used in.
posted by Mr.Q at 12:18 AM
0 Comments:
Post a Comment
<< Home