Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞
The IIS-side (SxS) collection allows an ASP application to specify which version of the system DLL or traditional COM component to use, such as MDAC, MFS, MSVCRT, MSXML, and so on. For example, if your ASP application relies on MSXML version 2.0, you can ensure that even the ServerAfter the Service Pack has been applied, your application still uses MSXML version 2.0. Any new version of MSXML is still installed on your computer, but it retains version 2.0 and is used by your application. Configuring the SxS assembly requires that you know the path to the DLL, and that the COM + manifest file exists in each virtual directory that needs to use the DLL. The COM + manifest is an XML file that contains information about the location of the DLL installation. IIS does not verify that the manifest exists. The manifest looks similar to the following file excerpt:
You can enable side-by-side collections either programmatically or by using IIS Manager on the IIS side.
Using IIS Manager on the IIS side to enable side-by-side collections
In IIS Manager, right-click the Web site or virtual directory, and then click Properties.
Click the Virtual Directory tab, and then click Configure.
If the configuration button is not available, the reason is that the application has not yet been created for the virtual directory. Click Create to create an application.
In the Application Configuration dialog box, click the Options tab.
Select the Enable collection by side together check box.
In the Manifest file name box, type a name for the COM + manifest file.
Click OK two times.
To programmatically enable side-by collection, set the ASPENABLESXS flag for AspAppServiceFlags metabase properties. Also, set the AspSxsName metabase property to the name of the COM + manifest. Set both metabase properties at the application level.
Important even if the feature is configurable at the application level, only one version of the system DLL can be used in any one of the application pools. For example, if an application App1 uses MDAC version 2.5 and the application APP2 uses MDAC version 2.4, APP1 and APP2 should not be in the same application pool. If they are in the same application pool, the application loaded first will load the corresponding version of MDAC, and other applications will only be forced to use that version until the applications are unloaded.
This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or
reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or
complaint, to firstname.lastname@example.org. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
and provide relevant evidence. A staff member will contact you within 5 working days.