loaded dll instead when intent to load specification config

Bug #914181 reported by Guanglei Li
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The convention which concordion uses to locate the specification configuration is "replacing the .dll extension with the .config extension". While Windows is case insensitive. On some machine (at least mine), the dll file contains spec is XXX.DLL, which the extension is uppercase. So the replacement failed since no lowercase "dll" found and the original dll file path was returned as the configuration file. Then when the parser tries to parse it as xml, it failed for sure.

The fix is quite simple, just as the following code:

- var configFileName = pathToAssembly.Replace(".dll", ".config");
+ var configFileName = pathToAssembly.ToLowerInvariant().Replace(".dll", ".config");

Revision history for this message
Guanglei Li (ajaxchelsea) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers