471,599 Members | 1,582 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,599 software developers and data experts.

Deploying Strong-named Configuration Block project causing errors

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.Configurat ion.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.
Nov 17 '05 #1
1 1248
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.

--
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
"Robert N" <Ro*****@discussions.microsoft.com> wrote in message
news:AF**********************************@microsof t.com...
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.Configurat ion.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.


Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

129 posts views Thread by Torbjørn Pettersen | last post: by
reply views Thread by Sean Campbell | last post: by
3 posts views Thread by Mark Ingram | last post: by
8 posts views Thread by per9000 | last post: by
6 posts views Thread by raylopez99 | last post: by
2 posts views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by
reply views Thread by Anwar ali | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.