John Migas migasj

#Prevent ImageResizer from inheriting to app folder in IIS

Apps folders in IIS will inherit the web.config file of the parent. ImageResizer if not installed in the child app will throw an error in this setup. The below solution is the fix for this issue.

Assuming you used the default names given in the installation instructions for ImageResizer the below sections must be added to the app's web.config to prevent the error "Could not load type 'ImageResizer.InterceptModule'." These additions will remove references to ImageResizer from your child application. ImageResizer does include part of this in their own troubleshooting however their solution is incomplete.

<configuration>
	<configSections>

	// Title: An exhaustive enum of all Windows System Error Codes
	// Source: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681381.aspx
	// Description: Error codes are a means to provide information to outside systems on why a program terminated. This list
	// need not be included in its entirety. It is meant to aid in conforming to the existing error code usage.
	// See this link form more information on usage. https://msdn.microsoft.com/en-us/library/system.environment.exitcode.aspx
	// Note: Internet error codes are excluded from this list. See here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa385465.aspx
	// Updated: 2016/10/31

	namespace Core
	{

	function Add-Path() {
	[Cmdletbinding()]
	param([parameter(Mandatory=$True,ValueFromPipeline=$True,Position=0)][String[]]$AddedFolder)
	# Get the current search path from the environment keys in the registry.
	$OldPath=(Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH).Path
	# See if a new folder has been supplied.
	if (!$AddedFolder) {
	Return 'No Folder Supplied. $ENV:PATH Unchanged'
	}
	# See if the new folder exists on the file system.