Đang chuẩn bị liên kết để tải về tài liệu:
Wrox Professional Web Parts and Custom Controls with ASP.NET 2.0 phần 3

.NET Compact Framework là nền tảng của Microsoft để phát triển các ứng dụng di động, hỗ trợ khả năng khai thác sức mạnh của các dịch vụ web trên thiết bị di động. Ngoài ra, lập trình viên có thể tận dụng những tính năng cao cấp của Visual Studio "Everett" để xây dựng các ứng dụng hữu ích cho doanh nghiệp một cách nhanh chóng. Smart Device Extensions, một phần mở rộng cho IDE của Visual Studio .NET, cung cấp các chức năng giúp đơn giản hoá việc lập trình ứng dụng di động | Creating Custom Controls It would be helpful then if the custom controls were presented to the developer in a way that reflects these functional groups rather than just as a list of custom controls in a DLL. However these custom controls reflect the requirements for a single site the book site. It s not hard to imagine that the organization supporting the book site might also support sites selling music CDs DVDs and other entertainment products. Because these kinds of products have different information needs than books these sites will use different custom controls to display product information and to search for products. Furthermore a site that loads the DVD-enabled versions of the custom controls won t use the book-enabled versions. As a result it makes sense to create separate DLLs for the DVD CD and book custom controls. This will result in separate projects for the book CD and DVD sites custom controls for instance. The customer information custom control has different considerations however. The customer information used on one site is the same for all the sites because customer information is defined at the organization level rather than the site level. As a result the customer custom control will be common to all of the sites. It makes sense then to have the customer information custom control in a project by itself so that it will be compiled into its own DLL. With the custom information control in its own DLL any of the sites can load the customer custom control without loading other custom controls that the site won t use. As this case study suggests you are always looking at the tradeoffs between keeping your DLLs small while ensuring that loading one DLL will also pre-load other custom controls that your application will likely be using. While it would certainly be helpful if developers using your custom controls read your documentation you did write the documentation didn t you developers prefer to figure out how to use your custom controls by .