3/25/2017 12:04 AM Productividad: Factor clave para ser un gran desarrollador en ASP .NET 2.0 Willy Marroquín BEA SOA J2EE Architech MCSD 6.0, MCSD .NET,

Presentación del tema: "3/25/2017 12:04 AM Productividad: Factor clave para ser un gran desarrollador en ASP .NET 2.0 Willy Marroquín BEA SOA J2EE Architech MCSD 6.0, MCSD .NET,"— Transcripción de la presentación:

1 3/25/ :04 AM Productividad: Factor clave para ser un gran desarrollador en ASP .NET 2.0 Willy Marroquín BEA SOA J2EE Architech MCSD 6.0, MCSD .NET, MCT MVP 2k3-2K4 Borland C++ Certified © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2 Agenda Master Pages Controles Data Source Refactoring Snippets
Enterprise Library 2.0 Roadmap © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

3 Nuevas caracteristicas de ASP.NET 2.0
3/25/ :04 AM Nuevas caracteristicas de ASP.NET 2.0 Controles Data Controles Login Web Parts Otros nuevos controles Controles Paginas Maestras Themes y Skins Mejora Scripting del cliente Compilación y Localización Framework Page Membresía Administración De Roles Perfiles Configuración ASP.NET 2.0's numerous new features can be grouped into three categories: new controls (more than 50 in all), new features in the page framework, and new services. In addition, myriad enhancements have been made to existing controls and services. The features covered in this session include: Master pages Data controls (and data access in general) Membership, role management, and login controls Profiles Site maps Servicios y APIs Mapas de Sitio Monitoreo Otros nuevos servicios © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

4 Paginas Maestras Contenido Heredado Pagina Maestra Pagina Contenido
ASP.NET 2.0 introduces a number of new features designed to help developers build cutting-edge UIs with a minimum of effort. First there's master pages, which enable pages to be templatized and which enjoy great design-time support in the Visual Studio 2005 IDE. Next, there's themes and skins, which allow controls, pages, and even entire sites to be visually themed with the stroke of a mouse. Finally, ASP.NET 2.0 introduces about 50 new control types ranging from the simple (e.g., BulletedList and ImageMap) to the sublime (e.g., GridView, DetailsView, Menu, TreeView, and Wizard). This slide depicts master pages. On the left is a master page as seen in the Visual Studio 2005 IDE. On the right is a content page that uses that master page, also shown in Visual Studio. Note the rich design-time exeprience: when the content page is open in the designer, content declared in the page itself is shown in full color, while content inherited from the master page is shown in half-color. Master pages enable developers to build templates that contribute code and content to other pages ("content pages") on the site. Because ASP.NET 1.x lacked template support, developers often resorted to factoring common UI elements--elements that appear on multiple pages--into user controls and then declaring the user controls in each page that uses them. Master pages provide a more elegant solution to the problem of defining common look and feel. The term "visual inheritance" is often used to describe master pages because content pages inherit appearance from master pages the same way derived classes inherit methods, properties, and other type members from base classes. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

5 Como funcionan las paginas maestras
3/25/ :04 AM Como funcionan las paginas maestras Las paginas maestras definen el contenido común y el espacio reservado para el contenido personalizado Las paginas de contenido referencia a la maestra y rellenan el espacio reservado con el contenido Site.master default.aspx The first and most important concept to grasp when learning about master pages is that of Content and ContentPlaceHolder controls. Master pages use ContentPlaceHolder controls to define where content pages can plug in content. Content pages plug in content by declaring Content controls whose ContentPlaceHolderID properties match ContentPlaceHolder IDs in the master. A master page can contain an unlimited number of ContentPlaceHolder controls. All content defined in content pages MUST appear in Content controls--that is, between <asp:Content> and </asp:Content> tags. Reservado para contenido Contenido © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

6 Page.Master Nueva propiedad de System.Web.UI.Page
3/25/ :04 AM Page.Master Nueva propiedad de System.Web.UI.Page Provee a las paginas de contenido con acceso programático a las paginas maestras Determina si una pagina tiene una maestra Accesa los controles definidos en la maestra Accesa los métodos y propiedades publicas definidos en la maestra Integración a nivel de código de las paginas maestras y las paginas de contenido In practice, master pages often include controls that need to be accessed at run-time by content pages. In ASP.NET 2.0, the System.Web.UI.Page class includes a new property named Master that contains a reference to a content page's master page (or null if the page lacks a master page). This enables controls defined in master pages to be supported by code contained in content pages. Of course, master pages can also include code that interacts with controls declared in master pages. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

7 Paginas Maestras <Inheritance> 3/25/2017 12:04 AM
© 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8 Controles Data Source Enlace a Datos declarativo (“sin código") Sql-
3/25/ :04 AM Controles Data Source Enlace a Datos declarativo (“sin código") Sql- DataSource Object- DataSource Access- DataSource Xml- DataSource SiteMap- DataSource Data Component Site Map Provider ASP.NET 2.0 makes building data-driven sites easier than ever before by introducing declarative data binding utilizing data source controls (which dramatically reduce the amount of code you have to write), providing new (and very rich) data controls such as GridView and DetailsView, introducing SQL cache dependencies (which allow cached items to be keyed to database entities), and offering an expanded and simplified syntax for data-binding expressions. Data source controls (shown here) reduce the amount of code you write by replacing code that queries data sources and binds the results to controls with <asp:> tags. In Visual Studio 2005, you can create these tags using drag-and-drop. You can also use the Visual Studio 2005 IDE to configure data sources. ObjectDataSource controls are particularly interesting because they allow you to practice declarative data binding without sacrificing the ability to perform data accesses with data access components. ObjectDataSources place declarative wrappers around data components. SQL Databases Any Data Access Databases XML Data Site Maps © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

9 Controles de Datos Nuevos controles de enlace a Datos
3/25/ :04 AM Controles de Datos Nuevos controles de enlace a Datos Soporte integrado para seleccionar, edición, paginación, ordenamiento y más Vista Grid Vista Detalle Vista Forma GridView is best described as a super DataGrid: it does everything DataGrid does and then some. Unlike the DataGrid, which requires code to do sorting, paging, selecting, and editing, the GridView control can perform all these actions innately--that is, with no code. GridView also supports a richer assortment of column types than DataGrid. Whereas GridView is designed to render sets of records into HTML tables, DetailsView is designed to take one record or a set of records and display them one at a time. Built-in paging support enables records bound to a DetailsView to be browsed with no code. Built-in editing support allows records to be inserted, updated, and deleted, again with no code (although the reality is that you'll end up writing some code to handle concurrency issues and respond to update failures). The same field types--ImageField, CheckBoxField, and so on--that can be declared in a GridView can also be declared in a DetailsView. In demonstrations, DetailsView controls are often paired with GridView controls to implement master-detail views. However, DetailsView is perfectly capable of working without GridView. The DetailsView control shown here is currently in editing mode. FormView is similar to DetailsView but is entirely template-driven (in the same way that Repeater controls are entirely template-driven). © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

10 Enlace a datos en 2 sentidos
3/25/ :04 AM Enlace a datos en 2 sentidos Los controles de datos proveen las UIs de Edición Propiedades AutoGenerateXxxButton Propiedades Insert/EditRowStyle Eventos Inserting/ed, Updating/ed, Deleting/ed Los controles de fuentes de datos proveen la lógica Propiedades Insert/Update/DeleteCommand Propiedades Insert/Update/DeleteParameters Visual Studio provee la unión Data source contols can fetch data from data sources, but they can update the data sources, too--a feature known as 2-way data binding. In addition, data controls such as GridView and DetailsView contain built-in editing support. 2-way data binding vastly reduces the effort required to build Web-editable UIs. RE: "Visual Studio supplies the glue." There can be a lot of work involved in defining the InsertCommand, UpdateCommand, and DeleteCommand properties of a data source control, not to mention the InsertParameters, UpdateParameters, and DeleteParameters sections that accompany them. Visual Studio's Configure Data Source command will do most of that work for you. It even lets you decide whether the UpdateCommands and DeleteCommands that it generates implement a first-in wins or last-in wins strategy, which determines what happens when multiple users edit the same data at the same time. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

11 3/25/ :04 AM Caching Muchos de los controles de fuente de Datos proveen soporte incorporado a caching EnableCaching – Activa/Desactiva el caching CacheDuration – Tiempo de duración (segundos) Caching de datos sin código! In ASP.NET 1.x, you had to write code to cache query results. In 2.0, the data source controls will do the caching for you. Caching is enabled by setting EnableCaching="true" and CacheDuration to the number of seconds you want the data cached. Under the hood, data source controls uses the ASP.NET application cache to store the data. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

12 CacheSync Dependencias de Cache SQL
3/25/ :04 AM CacheSync Dependencias de Cache SQL Conecta items en cache con entidades de la Base de Datos Cambios en la data original elimina los items correspondientes en cache Trabaja con SQL Server 7, SQL Server 2000 y SQL Server 2005 Requiere preparacion en SQL Server 7 y SQL Server 2000 (Aspnet_regsql.exe) “Ya trabaja" con SQL Server 2005 SQL cache dependencies are one of ASP.NET 2.0's coolest new features. In ASP.NET 1.x, you could place items in the application cache and create dependencies between those items and objects in the file system or other objects in the cache. Missing, however, was a means for creating dependencies between cached items and database entities, which would enable cached query results to be automatically evicted from the cache if the underlying data changed. SQL cache dependencies ("CacheSync") do exactly that. SQL cache dependencies are more powerful when paired with SQL Server 2005 because 1) they are more granular (row level versus table level), 2) they don't rely on polling (instead relying on query notifications from SQL Server 2005), and 3) they require no preparation of the database. Set a data source control's SqlCacheDepdendency property to "CommandNotification," for example, and CacheSync just works! NOTE: A late-breaking change to ASP.NET 2.0's CacheSync feature requires an application to call System.Data.SqlClient.SqlDependency.Start () before using SQL cache dependencies. This is easily accomplished by adding an Application_Start method to Global.asax. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

13 <Data Controls> <Data Binding> <Manager Cache>
3/25/ :04 AM Fuentes de Datos <Data Controls> <Data Binding> <Manager Cache> © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

14 Refabricación VB 2005 Simplifica el código en Visual Basic
3/25/ :04 AM Refabricación VB 2005 Simplifica el código en Visual Basic Para ejecutar el método extraer, solo seleccione el bloque de código que desea extraer, y presione la opción Refactor Para reordenar parámetros, colocar el cursor en el tipo de parámetro y presionar la opción Refactor Para crear un método sobrecargado, colocar el cursor al inicio de la declaración del método y presionar la opción Refactor Para reversar una condicional o condición anidada con una cláusula protegida, colocar el cursor en el "if" y presionar la opción Refactor SQL cache dependencies are one of ASP.NET 2.0's coolest new features. In ASP.NET 1.x, you could place items in the application cache and create dependencies between those items and objects in the file system or other objects in the cache. Missing, however, was a means for creating dependencies between cached items and database entities, which would enable cached query results to be automatically evicted from the cache if the underlying data changed. SQL cache dependencies ("CacheSync") do exactly that. SQL cache dependencies are more powerful when paired with SQL Server 2005 because 1) they are more granular (row level versus table level), 2) they don't rely on polling (instead relying on query notifications from SQL Server 2005), and 3) they require no preparation of the database. Set a data source control's SqlCacheDepdendency property to "CommandNotification," for example, and CacheSync just works! NOTE: A late-breaking change to ASP.NET 2.0's CacheSync feature requires an application to call System.Data.SqlClient.SqlDependency.Start () before using SQL cache dependencies. This is easily accomplished by adding an Application_Start method to Global.asax. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

15 Refactoring C# Simplifica el código C# Método Extraer
3/25/ :04 AM Refactoring C# Simplifica el código C# Método Extraer Campo encapsulado Extraer Interfases Reordenar Parámetros Eliminar Parámetros Renombrar Promover variables locales a Parámetros SQL cache dependencies are one of ASP.NET 2.0's coolest new features. In ASP.NET 1.x, you could place items in the application cache and create dependencies between those items and objects in the file system or other objects in the cache. Missing, however, was a means for creating dependencies between cached items and database entities, which would enable cached query results to be automatically evicted from the cache if the underlying data changed. SQL cache dependencies ("CacheSync") do exactly that. SQL cache dependencies are more powerful when paired with SQL Server 2005 because 1) they are more granular (row level versus table level), 2) they don't rely on polling (instead relying on query notifications from SQL Server 2005), and 3) they require no preparation of the database. Set a data source control's SqlCacheDepdendency property to "CommandNotification," for example, and CacheSync just works! NOTE: A late-breaking change to ASP.NET 2.0's CacheSync feature requires an application to call System.Data.SqlClient.SqlDependency.Start () before using SQL cache dependencies. This is easily accomplished by adding an Application_Start method to Global.asax. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

16 <Visual Basic 2005> <C# 2005>
3/25/ :04 AM Refactoring <Visual Basic 2005> <C# 2005> © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

17 Snippets VB2005 Fragmentos de código
3/25/ :04 AM Snippets VB2005 Fragmentos de código Los fragmentos de código son reutilizables, bloques de código orientados a tareas Visual Basic 2005 incluye mas de 500 fragmentos de código en un rango que va desde la creación de errores personalizados hasta el envío de correos, dibujo de imágenes En adición a las 500 piezas de código preescritas, la biblioteca de fragmentos de código es extensible SQL cache dependencies are one of ASP.NET 2.0's coolest new features. In ASP.NET 1.x, you could place items in the application cache and create dependencies between those items and objects in the file system or other objects in the cache. Missing, however, was a means for creating dependencies between cached items and database entities, which would enable cached query results to be automatically evicted from the cache if the underlying data changed. SQL cache dependencies ("CacheSync") do exactly that. SQL cache dependencies are more powerful when paired with SQL Server 2005 because 1) they are more granular (row level versus table level), 2) they don't rely on polling (instead relying on query notifications from SQL Server 2005), and 3) they require no preparation of the database. Set a data source control's SqlCacheDepdendency property to "CommandNotification," for example, and CacheSync just works! NOTE: A late-breaking change to ASP.NET 2.0's CacheSync feature requires an application to call System.Data.SqlClient.SqlDependency.Start () before using SQL cache dependencies. This is easily accomplished by adding an Application_Start method to Global.asax. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

18 <Creando y Usando fragmentos de código>
3/25/ :04 AM Fragmentos de Código <Creando y Usando fragmentos de código> © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

19 Marco de Trabajo Web Parts
3/25/ :04 AM Marco de Trabajo Web Parts Hay dos maneras básicas de crear un Web Part. Se puede tratar cualquier control Standard ASP.NET como un Web Part o se puede construir un control personalizado que derive de la clase WebPart. No es necesario modificar los controles para ser usados como Web Parts Se puede compartir información entre Web Parts en la misma pagina Se pueden importar o exportar los settings de los Web Parts SQL cache dependencies are one of ASP.NET 2.0's coolest new features. In ASP.NET 1.x, you could place items in the application cache and create dependencies between those items and objects in the file system or other objects in the cache. Missing, however, was a means for creating dependencies between cached items and database entities, which would enable cached query results to be automatically evicted from the cache if the underlying data changed. SQL cache dependencies ("CacheSync") do exactly that. SQL cache dependencies are more powerful when paired with SQL Server 2005 because 1) they are more granular (row level versus table level), 2) they don't rely on polling (instead relying on query notifications from SQL Server 2005), and 3) they require no preparation of the database. Set a data source control's SqlCacheDepdendency property to "CommandNotification," for example, and CacheSync just works! NOTE: A late-breaking change to ASP.NET 2.0's CacheSync feature requires an application to call System.Data.SqlClient.SqlDependency.Start () before using SQL cache dependencies. This is easily accomplished by adding an Application_Start method to Global.asax. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

20 Construyendo Web Parts en ASP .Net 2.0
3/25/ :04 AM Construyendo Web Parts en ASP .Net 2.0 <Creando un Web Parts simple> <Personalizando Web Parts> <Creando un menú Web Part personalizado> <Importando y Exportando settings de Web Part> © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

21 3/25/ :04 AM patterns & practices Recomendaciones específicas sobre como diseñar, desarrollar, implementar y operar soluciones en escenarios complejos. Para profesionales de IT; arquitectura, diseño, implementación, y operaciones de Infraestructura Core Infrastructure Solutions (CIS) team IT Infrastructure Platform Architecture Guidance (PAG) team Application Platform Para arquitectos y desarrolladores; arquitectura, diseño, desarrollo, implementación y operaciones de soluciones con .Net © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

22 patterns & practices: características
3/25/ :04 AM patterns & practices: características Revisadas y aprobadas por ingenieros de equipos de producto, consultores y servicios de soporte de Microsoft, además de socios y clientes. Probadas Basadas en experiencia de campo. Autorizadas Ofrecen la mejor recomendación disponible. Válidas Técnicamente validadas y probadas. Prácticas Ofrecen pasos concretos. Aplicables Tratan problemas de escenarios reales de clientes. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

23 Platform Architecture Guidance (PAG) ¿Qué ofrece?
3/25/ :04 AM Platform Architecture Guidance (PAG) ¿Qué ofrece? Application Blocks Guía para servicios comunes a nivel de sub-sistemas. Arquitecturas de Referencia Guía a nivel de sistemas para escenarios comunes. Patrones Soluciones atómicas para problemáticas recurrentes Guías Prescriptivas Guía en principios de arquitectura y recomendaciones en temas comunes como seguridad y performance. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

24 Application Blocks El problema
3/25/ :04 AM Application Blocks El problema … alguna vez se preguntó? Muchas aplicaciones necesitan “algo así”. Los desarrolladores han escrito “esto” cientos de veces. Desearía encontrar una solución para “esto” que pueda reutilizar. ¿Estaré resolviendo “esto” de la mejor forma? Ejemplo: manejo de configuraciones en una aplicación © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

25 Application Blocks ¿Qué son?
3/25/ :04 AM Application Blocks ¿Qué son? “Piezas” de software reutilizables que implementan servicios o mecanismos típicamente requeridos en las aplicaciones Guías implementadas y entregadas en forma de código Nos permiten: Escribir aplicaciones más sencillas de mantener, escalables y eficientes Escribir (mantener y testear) menos código Estandarizar de forma sencilla ciertos servicios para diferentes aplicaciones Una buena forma de aprender © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

26 Application Blocks ¿Qué incluyen?
3/25/ :04 AM Application Blocks ¿Qué incluyen? Código (VB, C#) Modificables Capacidad de extensión a través de la implementación de Providers en puntos previstos Implementación de patrones y buenas prácticas Buena documentación y ejemplos Soporte en su uso por Microsoft y la comunidad © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

27 Application Blocks disponibles
3/25/ :04 AM Application Blocks disponibles User Interface Process ASP.NET Updater Servicios de Adm., operación y seguridad Interfaz Web Interfaz Windows Smart Client Offline Interfaz de usuarios (multicanal) Configuration Management Procesos de interfaz de usuario Asynchronous Invocation Async. Invocation Application Block Exception Management Servicios del Negocio Interfaz de servicios Interfaz de servicios Servicio de Negocios Interno Servicio de Negocios Servicio de Negocios Caching Logging Hub de integración Servicios de Acceso a información Acceso a datos Agentes de servicio Orquestación de procesos Conectores y agentes Authorization & Profile Base de datos Data Access Entity Agreg. Application Block Aggregation © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

28 Enterprise Library for .NET Framework 2.0
Nueva liberación mayor de la biblioteca empresarial Diseñada para el Framework 2.0 Apalanca las nuevas capacidades ofrecidas por la plataforma Ciertas características de la Enterprise Library v1.x han sido desechadas a favor de la plataforma © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

29 Cambios claves desde la Enterprise Library 1.x
Configuración construida sobre System. Configuration No existe el bloque de aplicación (Application Block) Más facilidad de uso de los bloques con o sin archivos de configuración Instrumentación configurable y desactivada por defecto Mejoras en el bloque de Aplicaciones de Logging Flexibilidad y Rendimiento Más simple y poderoso bloque de aplicación para acceso a Datos Usado con OLE-DB, ODBC o cualquier proveedor La mayor parte del bloque de aplicación de seguridad ha sido eliminado Descartado a favor de las nuevas características de .NET Membership y Profile © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

30 Enterprise Library para .NET Framework 2.0
Caching Data Access Logging Plug-in Config Helpers & Design Instrumen- tation Object Builder Core Cryptography First up is the configuration application block and configuration tool. Security Exception Handling Optional Provider Dependency Block Dependency © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

31 Enterprise Library para .NET Framework 2.0
Caching Data Access Logging Core Plug-in Config Helpers & Design Instrumen- tation Cryptography Object Builder First up is the configuration application block and configuration tool. Security Exception Handling Optional Provider Dependency Block Dependency © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

32 Enterprise Library 2.0 <Bloque de aplicación de Seguridad>
3/25/ :04 AM Enterprise Library 2.0 <Bloque de aplicación de Seguridad> <Bloque de Aplicación de Acceso a Datos> © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

33 Recursos www.WillyDEV.NET Centro de Desarrollo ASP .NET Sitio ASP .NET
3/25/ :04 AM Recursos Centro de Desarrollo ASP .NET Bits, Forums, Quickstarts, Docs, Updates Sitio ASP .NET © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

34 Recursos Enterprise Library 2.0
3/25/ :04 AM Recursos Enterprise Library 2.0 Bits, Forums, Quickstarts, Docs, Updates © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

35 © 2006 Microsoft Corporation. All rights reserved.
3/25/ :04 AM © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.