Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / .NET SDK / November 2003

Tip: Looking for answers? Try searching our database.

missing tcp and http namespaces

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ron - 26 Nov 2003 21:55 GMT
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
Chris Taylor - 26 Nov 2003 22:46 GMT
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
> Hi,
>
[quoted text clipped - 29 lines]
>
> -- Ron

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.