TAILIEUCHUNG - Professional ASP.NET 3.5 in C# and Visual Basic Part 136

Professional in C# and Visual Basic Part 136. Building on the revolutionary release, adds several key new developer features including AJAX, LINQ, and a new CSS designer in Visual Web Developer 2008. The dramatic reduction in code that developers realized from the more than 50 new server controls in now allows developers the time to make their applications more interactive with AJAX, to work with data in their preferred language with LINQ, and to build visually attractive and consistent standards-based sites with CSS. . | Chapter 28 Using Business Objects file for a second time. Using this method meant that when you upgraded a component you automatically upgraded all the utilizing applications. However this practice didn t work out so well. In fact it became a very big contributor to DLL hell and the main reason why Microsoft began promoting the practice of installing private .NET component assemblies. After you have your components physically in place the only remaining task is to register the ActiveX component using regsvr32 just as you would when deploying an ActiveX-enabled application. Public Assemblies The opposite of a private assembly is a public assembly. Public assemblies share the RCW Interop DLL for other applications. In order to create a public assembly you must put the RCW file into the Global Assembly Cache GAC as shown in Figure 28-11. You can find the GAC at C windows assembly. Installing items in the GAC can be as simple as dragging-and-dropping the item into this folder through Windows Explorer. Although the GAC is open to everyone it is not recommended that you blindly install your components into this section unless you have a very good reason to do so. You can also add items to the GAC from the command line using the Global Assembly Cache Tool . It enables you to view and manipulate the contents of the global assembly cache and download cache. While the Explorer view of the GAC provides similar functionality you can use from build scripts makefile files and batch files. It is hard to find a very good reason to install your ActiveX Interop Assemblies into the GAC. If we had to pick a time to do this it would be if and when we had a highly shared ActiveX component that many .NET applications would be utilizing on the same machine. In a corporate environment this might occur when you are upgrading existing business logic from ActiveX to .NET enablement on a server that many applications use. In a commercial setting we avoid using the GAC.

TỪ KHÓA LIÊN QUAN
TAILIEUCHUNG - Chia sẻ tài liệu không giới hạn
Địa chỉ : 444 Hoang Hoa Tham, Hanoi, Viet Nam
Website : tailieuchung.com
Email : tailieuchung20@gmail.com
Tailieuchung.com là thư viện tài liệu trực tuyến, nơi chia sẽ trao đổi hàng triệu tài liệu như luận văn đồ án, sách, giáo trình, đề thi.
Chúng tôi không chịu trách nhiệm liên quan đến các vấn đề bản quyền nội dung tài liệu được thành viên tự nguyện đăng tải lên, nếu phát hiện thấy tài liệu xấu hoặc tài liệu có bản quyền xin hãy email cho chúng tôi.
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.