Catálogo de publicaciones - libros

Data access is essential for all but the most trivial web applications. However, the data-access code itself should not hinder a programmer’s productivity. Easy and intuitive data facilities are crucial in any good development environment, and VS .NET, together with ADO.NET, fulfills both requirements. In this Chapter, we looked at ADO.NET components and how they interact with the IDE to enhance our experience. You saw that VS .NET includes some powerful wizards and design-time advantages that have not previously been seen in a Microsoft IDE.

Components and data binding make the process of displaying and editing data a breeze. You learned how it works with simple controls, as well as with the more advanced DataGrid and DataList controls. You saw how the incredibly versatile templates can be used to achieve some real-world goals. Our Friends Reunion sample application became much more useful, and it’s a good example of the possibilities of the new platform.

In the next Chapter, you will learn about the importance of state in web applications, and you’ll find out how ASP.NET overcomes the stateless nature of the HTTP protocol through its impressive state management features.

Security in web applications is very important, because of the exposure to the entire Web (of hackers!). In this Chapter, we looked at some general security concepts, as well as modern role-based security.

We examined the various authentication options available in ASP.NET, and provided some guidance that should allow you to choose among them. We discussed application configuration files in the context of security settings, and we used authentication and authorization to secure an application. We also used custom authentication to meet application requirements, showing the level of extensibility available in the general security infrastructure.

In order to describe the close relationship between IIS and ASP.NET, we provided an overview of the modular and extensible architecture that exists to process web requests, and how the various authentication options are implemented internally, as well as their interaction with the main web application.

Now our Friends Reunion application has become much more secure, through the use of the concepts you’ve learned in this Chapter. However, we certainly haven’t covered every possible security-related feature available in .NET, as that is a subject for a whole book. As noted earlier, one such book is , which can also be downloaded as a PDF from www.microsoft.com/practices.

During this exploratory journey into ASP.NET’s brand-new web forms landscape, we have uncovered a lot of new features. We looked at the various categories of server controls—HTML controls, web controls, user controls, and custom controls—and performed some of the most common tasks with them. The consistent object model makes it easy to handle all of them in a standard manner, and server-side, event-driven programming raises programmer productivity to a new level.

Almost every part of the architecture is extensible, so that once you’ve mastered the built-in functionality, you can move on and extend it to provide powerful and reusable user controls or custom controls. This is a big leap forward for web application developers, who are no longer constrained by the limitations of the default features.

Although we’ve touched on the idea of creating dynamic web sites in this Chapter, we haven’t yet considered the most important tools for creating them: . In the next Chapter, you’ll learn how databases can be used with web forms to make great applications with minimal code.

Data access is essential for all but the most trivial web applications. You have learned the basics of ADO.NET, Microsoft’s new strategy for data access, and you have seen how the various pieces fit in the whole picture of web application development.

In this chapter, you started to add some data-aware pages to your application, which allowed you to leverage the power of data-driven pages. We discussed how to programmatically access a database and handle its data. You were able to display that data in web forms, taking advantage of the techniques you learned about in previous chapters.

Up to now, however, you have been typing a lot of code manually. VS .NET goes much further in programmer productivity, introducing the key concept of . In the next chapter, we’ll discuss this concept, and you’ll discover what components are and how they work in conjunction with the IDE to perform some automatic coding tasks. We’ll also dig into some exciting new features introduced by VS .NET to simplify web forms and data interaction through . You’ll learn how to use the more advanced wizards provided by components, and how to leverage web server controls to display and edit data in highly customizable ways through the use of another technique: .

Data access is essential for all but the most trivial web applications. However, the data-access code itself should not hinder a programmer’s productivity. Easy and intuitive data facilities are crucial in any good development environment, and VS .NET, together with ADO.NET, fulfills both requirements. In this Chapter, we looked at ADO.NET components and how they interact with the IDE to enhance our experience. You saw that VS .NET includes some powerful wizards and design-time advantages that have not previously been seen in a Microsoft IDE.

Components and data binding make the process of displaying and editing data a breeze. You learned how it works with simple controls, as well as with the more advanced DataGrid and DataList controls. You saw how the incredibly versatile templates can be used to achieve some real-world goals. Our Friends Reunion sample application became much more useful, and it’s a good example of the possibilities of the new platform.

In the next Chapter, you will learn about the importance of state in web applications, and you’ll find out how ASP.NET overcomes the stateless nature of the HTTP protocol through its impressive state management features.

Security in web applications is very important, because of the exposure to the entire Web (of hackers!). In this Chapter, we looked at some general security concepts, as well as modern role-based security.

We examined the various authentication options available in ASP.NET, and provided some guidance that should allow you to choose among them. We discussed application configuration files in the context of security settings, and we used authentication and authorization to secure an application. We also used custom authentication to meet application requirements, showing the level of extensibility available in the general security infrastructure.

In order to describe the close relationship between IIS and ASP.NET, we provided an overview of the modular and extensible architecture that exists to process web requests, and how the various authentication options are implemented internally, as well as their interaction with the main web application.

Now our Friends Reunion application has become much more secure, through the use of the concepts you’ve learned in this Chapter. However, we certainly haven’t covered every possible security-related feature available in .NET, as that is a subject for a whole book. As noted earlier, one such book is , which can also be downloaded as a PDF from www.microsoft.com/practices.

Data access is essential for all but the most trivial web applications. You have learned the basics of ADO.NET, Microsoft’s new strategy for data access, and you have seen how the various pieces fit in the whole picture of web application development.

In this chapter, you started to add some data-aware pages to your application, which allowed you to leverage the power of data-driven pages. We discussed how to programmatically access a database and handle its data. You were able to display that data in web forms, taking advantage of the techniques you learned about in previous chapters.

Up to now, however, you have been typing a lot of code manually. VS .NET goes much further in programmer productivity, introducing the key concept of . In the next chapter, we’ll discuss this concept, and you’ll discover what components are and how they work in conjunction with the IDE to perform some automatic coding tasks. We’ll also dig into some exciting new features introduced by VS .NET to simplify web forms and data interaction through . You’ll learn how to use the more advanced wizards provided by components, and how to leverage web server controls to display and edit data in highly customizable ways through the use of another technique: .

Data access is essential for all but the most trivial web applications. However, the data-access code itself should not hinder a programmer’s productivity. Easy and intuitive data facilities are crucial in any good development environment, and VS .NET, together with ADO.NET, fulfills both requirements. In this Chapter, we looked at ADO.NET components and how they interact with the IDE to enhance our experience. You saw that VS .NET includes some powerful wizards and design-time advantages that have not previously been seen in a Microsoft IDE.

Components and data binding make the process of displaying and editing data a breeze. You learned how it works with simple controls, as well as with the more advanced DataGrid and DataList controls. You saw how the incredibly versatile templates can be used to achieve some real-world goals. Our Friends Reunion sample application became much more useful, and it’s a good example of the possibilities of the new platform.

In the next Chapter, you will learn about the importance of state in web applications, and you’ll find out how ASP.NET overcomes the stateless nature of the HTTP protocol through its impressive state management features.

In this Chapter, we provided an introduction to web services, showing how they’re not only an open standard in themselves, but are built up from other open standards such as HTTP and XML. You’ve seen that by making use of web services, you have a method for allowing disparate applications to interact with one another very simply, where it would have taken a great deal of painstaking integration work in the past.

These features and ease of use were put into action in the development of web service functionality for our Friends Reunion application. By creating a test application, we showed how this functionality can be used (consumed) as simply as any other object in .NET, once a reference has been added within the project.

After we created and used our own web services, we took a look at one of the key underlying technologies of web services, SOAP, which allows information to be passed around in a structured XML format. We then went on to look at exception handling, and saw how this tied in to SOAP with the SoapException object.

We then discussed the performance of web services. You saw how you can improve performance by retrieving less data by using built-in mechanisms and by creating your own mechanisms, as well as by taking advantage of and controlling XML serialization support in .NET.

Finally, we looked at how you can publish your web services so that others can use them, and how you can find third-party services to use in your own applications, including a few examples of currently available services that can be used to add further functionality to the Friends Reunion application.

Security in web applications is very important, because of the exposure to the entire Web (of hackers!). In this Chapter, we looked at some general security concepts, as well as modern role-based security.

We examined the various authentication options available in ASP.NET, and provided some guidance that should allow you to choose among them. We discussed application configuration files in the context of security settings, and we used authentication and authorization to secure an application. We also used custom authentication to meet application requirements, showing the level of extensibility available in the general security infrastructure.

In order to describe the close relationship between IIS and ASP.NET, we provided an overview of the modular and extensible architecture that exists to process web requests, and how the various authentication options are implemented internally, as well as their interaction with the main web application.

Now our Friends Reunion application has become much more secure, through the use of the concepts you’ve learned in this Chapter. However, we certainly haven’t covered every possible security-related feature available in .NET, as that is a subject for a whole book. As noted earlier, one such book is , which can also be downloaded as a PDF from www.microsoft.com/practices.