Inside Microsoft® Visual Studio® .NET 2003 [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Inside Microsoft® Visual Studio® .NET 2003 [Electronic resources] - نسخه متنی

Brian Johnson

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید










Merge Modules


When creating software for the Windows operating system, developers commonly place code into DLLs so it can be shared among multiple applications. To distribute software to your customers, you could install the DLLs you create with a .msi setup project, but this would be a less-than-ideal way to install the code. Suppose you've built a .NET user control library that you want to sell; your customers can use this library to build their own applications. How can customers redistribute this library to their own customers? You could provide detailed instructions that explain to your users how to include the component in their own .msi setup. However, this could be problematic because if they don't install your component properly, other software that uses your component might stop functioning. Alternatively, you could create a setup project that installs and uninstalls your library, but that's not a good option because your users would have to give their customers two .msi files and make sure they were installed in the correct order.

To make installing your library easy and reduce the risk of a user incorrectly installing and uninstalling a component, you can store your library in a merge module (.msm file). Merge modules are like the DLLs of a setup project. You can use a DLL to store code shared among different applications; a merge module contains installation logic shared among many .msi files. Merge module projects are similar to setup projects, except you cannot use the User Interface and Launch Conditions editors. One other difference between a setup project and a merge module project is that with a merge module project, the File System editor adds the folders Web Custom Folder and Module Retargetable Folder. If you place files in these folders, the user consuming your merge module can choose which location on disk to place the files. The user can change the installation path of the merge module contents by selecting the merge module in Solution Explorer and modifying the ModuleRetargetableFolder property in the Properties window. Consuming a merge module in a setup project is easy; you select the setup project in Solution Explorer and choose Project | Add | Merge Module.


/ 118