469,626 Members | 877 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,626 developers. It's quick & easy.

Namespace "Configuration" does not exist in Microsoft.practices.En

Hi,
I may be doing something dumb but.......I have been using the data access
ent lib to do the HOL's. All is well. However I now want to add the data
access functionality to my BTS2004 project, therefore requiring strong name
key. When I try to compile the Data solution from source I get

Namespace "Configuration" does not exist in
Microsoft.practices.EnterpriseLibrary.Data are you missing.....

The problem is that I am not. I can't see anywhere in the source where there
is a class / interface called Configuration in the
Microsoft.practices.EnterpriseLibrary.Data namespace.

I also get a similar error with
Microsoft.practices.EnterpriseLibrary.Data.Instrum entation

Any help appreciated
Oct 25 '05 #1
1 1923
Sorry, false alarm, I removed and reinstalled. Second time round te source
built fine for me with the new strong name key.
"Bakunin" wrote:
Hi,
I may be doing something dumb but.......I have been using the data access
ent lib to do the HOL's. All is well. However I now want to add the data
access functionality to my BTS2004 project, therefore requiring strong name
key. When I try to compile the Data solution from source I get

Namespace "Configuration" does not exist in
Microsoft.practices.EnterpriseLibrary.Data are you missing.....

The problem is that I am not. I can't see anywhere in the source where there
is a class / interface called Configuration in the
Microsoft.practices.EnterpriseLibrary.Data namespace.

I also get a similar error with
Microsoft.practices.EnterpriseLibrary.Data.Instrum entation

Any help appreciated

Oct 25 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by samarthkumar84 | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.