Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

<wellknown> Element (Client Instance)

This topic is specific to a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using the  Windows Communication Foundation (WCF).

Contains information about server-activated (well-known) objects the application wants to consume. When a client uses a <wellknown> element, the parent <client> element does not need a url attribute. This element may occur in an application configuration file, machine configuration file.


The following sections describe attributes, child elements, and parent elements.


Attribute Description


Required attribute.

Specifies the full type name of the object and the assembly name of the type implementation on the client. This includes version, culture, and public key information if the containing assembly is in the global assembly cache.


Required attribute.

Specifies the full URL of the server-activated type, including the object Uniform Resource Identifier (URI).


Optional attribute.

Used by the .NET Framework Configuration Tool to create a list of server-activated objects this client is registered to call. The .NET Framework remoting system does not use this attribute.

Child Elements


Parent Elements

Element Description


Contains information about remote objects the application consumes and exposes.


Contains objects the application consumes. Because the url attribute is required for client-activated types, but not for server-activated types, each unique URL will have its own client element containing the client-activated types published at that location.


The root element in every configuration file used by the common language runtime and .NET Framework applications.


Contains information about remote objects and channels.

The following configuration file declares a server-activated (well-known) remote type for consumption and specifies that the client application should use the HttpChannel but allow the .NET Framework remoting system to find an appropriate port on the client's behalf.

               type="RemoteType, RemoteAssembly"

Copyright © 2007 by Microsoft Corporation. All rights reserved.

Community Additions

© 2015 Microsoft