In my development environment I can add references to the Microsoft Practices
libraries and everything works ok. But when I copy the application to the
test server I get the message "CS0234: The type or namespace name 'Practices'
does not exist in the namespace 'Microsoft' (are you missing an assembly
reference?)".

A search of the web suggests that I am missing an assembly reference
(exactly as the message says). I cannot find any place in the project where
the Microsoft Practices libraries are referenced. Other libraries are
referenced in the Web.Config file, but not the Microsoft Practices libraries.
They are physically copied to a Bin folder instead.

How can I get this to work on my test server? How do other people handle this?

Thanks!

Most likely an install of the Enterprise Library is all that you need. I am
not sure, however, as I do not know what you have played with.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
"MichaelQuinlan" <maquinlan (AT) nospam (DOT) nospam> wrote

I downloaded the EnterpriseLibrary project from msdn, and installed it.

when you run through the installer, it compiles and gac's and creates all
the files nicely for you.

http://msdn2.microsoft.com/en-us/library/aa480453.aspx




"MichaelQuinlan" <maquinlan (AT) nospam (DOT) nospam> wrote

Usually these assemblies are specified through entries in the web.config
file. If, for example your entries specifiy strong-named assemblies that may
be installed in the GAC and your web-server doesn't have them there, or the
versions are different, that would be one cause of this type of issue.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com


"MichaelQuinlan" wrote:

Does this mean the Enterprise Library needs to be installed on every computer
the application will run on?

I will try this. Thanks for the reply.

"Cowboy (Gregory A. Beamer)" wrote:

No, the developer machine can build them.

Then you can copy them to a common "ThirdPartySourceReferences" folder or
something like that. And reference them from there, and deploy them with
you application.

This is the option if you don't want to gac them on every deployment
machine.


...

Install the library on a development machine.
Find (do a search for)
Microsoft.Practices.EnterpriseLibrary*.*

Copy them (dlls and xmls ) to

c:\common\ThirdPartySourceReferences\ (or whatever you want)

Have your csproj or vbproj reference them from there.




"MichaelQuinlan" <maquinlan (AT) nospam (DOT) nospam> wrote