dotnet sdk: missing tcp and http namespaces -- dotnet sdk

missing tcp and http namespaces

Ron
11/26/2003 1:55:28 PM

dotnet sdk:

Hi,

Trying to work with Remoting and was neither able to
import System.Runtime.Remoting.Channels.Tcp nor
System.Runtime.Remoting.Channels.Http. IntelliSense
could only find up to the Channels namespace. It showed
the classes at that level but could not find the Tcp or
Http parts. When I tried to manually add them, the
compiler tasked them as errors. Subsequently, the
compiler complained about trying to instantiate
TcpChannel and HttpChannel. However, the MSDN Library
and a ton of other Microsoft documentation/samples are
telling me that they should be part of the FCL.

I tried writing the code on other co-worker's Visual
Studio installations and got the same results. So we
were not sure if our .NET Framework installations are
corrupted or if there is some configuration setting that
is needed.

As a side note, I am able to work with Remoting samples
that use a configuration file instead of registering an
instantiated TcpChannel/HttpChannel. Regardless, I want
to be able to use the entire FCL or know the reason why I
cannot.

I am running with the following:
Microsoft Development Environment 2003 Version 7.1.3088
Microsoft .NET Framework 1.1 Version 1.1.4322
Microsoft Visual Basic .NET 69586-335-0000007-18770
Microsoft Visual C# .NET 69586-335-0000007-18770

-- Ron

Re: missing tcp and http namespaces

Chris Taylor
11/27/2003 12:46:10 AM

Hi,

You have to add a reference to the System.Runtime.Remoting.dll assembly. The
reason that without this reference you are able to access the
System.Runtime.Remoting. namespace and sub-namespaces without this reference
is that some of the System.Runtime.Remoting. namespace and sub-namespaces
are implemented in mscorlib.dll which is referenced by default.

Hope this helps

Chris Taylor
[quoted text, click to view]