A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
[6.0.441.2] EPiServer.Shell - Inconsistency in assembly load configuration
Good point. We have now updated it so that module.config is written like this:
<module ...>
<assemblies>
<!-- This configuration refers to the (unreleased) RTM version of EPiServer CMS 6 -->
<add assembly="..." />
</assemblies>
</module>
If you need to write this file today to be compatible with both RC and RTM versions you can add both name and assembly attributes. Leaving just name will throw an exception.
Feb 15, 2010 14:22
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
I notieced a small inconsistency in how assemblies are added to modules.
In episerver.shell section in web.config uses assembly attribute but module manifest uses name attribute:
Web.config:
<episerver.shell>
<protectedModules rootPath="~/cms/UI/" >
<add name="Shell">
<assemblies>
<add assembly="EPiServer.Sample.GlobalNavigation.UI" />
</assemblies>
</add>
Module.config:
<?xml version="1.0" encoding="utf-8" ?>
<module loadLocalBin="false"
helpFile="/i2/ts/Help.aspx?culture={culture}"
productName="I2 Translation Service">
<assemblies>
<add name="I2.TS.Plugin.6R1" />
</assemblies>
</module>