From Glass.Mapper.Sc.CastleWindsor

In the next release of Glass.Mapper.Sc.CastleWindsor (V3.3.0) we have removed the WebActivator reference. We have chosen to do this because some users of Glass.Mapper.Sc.CastleWindsor were experience problems with WebActivator's assembly scanning. Often this issue wouldn't appear until it was on the production environment which meant debugging it was difficult. We also wanted to reduce the number of dependencies that are downloaded  when using Glass.Mapper.Sc.CastleWindsor. 

To replace this we are adding a processor to the Sitecore Initialise pipeline. When you install this version of Glass.Mapper.Sc.CastleWindsor you will notice that a Glass.Mapper.Sc.CastleWindsor.config has been added to the /App_Config/Includes folder:



Within this folder you will find the following code which still calls the class /App_Start/GlassMapperSc.cs:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
	<sitecore>
		<pipelines>
			<initialize>
				<processor type="Glass.Website.App_Start.GlassMapperSc, Glass.Website" />
			</initialize>
		</pipelines>
	</sitecore>
</configuration>


If you haven't modified your GlassMapperSc.cs file then you should be able to overwrite the old file with the new file without any problems. If you have modified the GlassMapperSc.cs file the you should refer to the source code on GitHub to see what changes you need to make.

If you still want to use WebActivator with your solution instead of using the Sitecore Initialise pipeline then you need to remove the Glass.Mapper.Sc.CastleWindsor.config file and uncomment the WebActivator attribute that is in the GlassMapperSc.cs file.

Let us know if you have any problems with this latest change.

comments powered by Disqus