Deploying Strong-named Configuration Block project causing errors

[Guest]

I was able to compile (Debug) and reference an Configuration Block project
for my primary application "AppPrimary.exe". When I add a strong name file
to the Configuration Block project and recompile the projects my
"AppPrimary.exe" no longer works correctly.

I've noticed that when AppPrimary.exe runs with the Non-Strong-Named version
of the Config Block the following has the proper values (i.e.
Current.builder=
"{Microsoft.Practices.EnterpriseLibrary.Configuration.ConfigurationBuilder}" )

public static object GetConfiguration(string sectionName)
{
return Current.builder.ReadConfiguration(sectionName);
}

BUT
when AppPrimary.exe runs with the Strong-Named version of the Config Block
the Current.builder value is empty.

This causes errors to be thrown further down the line of the Config Block
library code.

Any help is greatly appreciated.
Thanks.

 

[Dmytro Lapshyn [MVP]]

Hi Robert,

My guess is when your configuration handler gets serialized, it includes
information on the assembly in which the handler is implemented. For
strong-named assemblies, the assembly name must include the public key
token.