Programming Forums > Application Development > C#

hollystyles · Jan 4th, 2008, 8:17 AM

This is where uber tools like Visual Studio hide a little too much for beginners. When you start a new project some of the framework libraries are automatically linked (depending what type of project template you select) see the references folder in solution explorer. You need to add others yourself when they are required, simply typing "using System.Net.Sockets" is not sufficient as you have now discovered.

Alias · Jan 4th, 2008, 8:51 AM

Quote:

The Program and the framework binaries are connected through the IDE.

We are talking about VS, right?, the program is the IDE, the IDE knows look in the GAC for assemblies, so basically it looks into a directory.

Quote:

If you mess something up in the IDE it wont properly connect to the Framework Binaries.

Would you care to ellaborate on that a little? Again, the IDE knows look in the GAC for assemblies, and Im not exactly sure how you would mess that up.

Quote:

So if a VS developer wanted to have some fun they could create a "System.HelloWorld" that wouldn't link to anything.

Ellabroation would be good at this point also. So we can create empty binaries? namespaces? If what you create is not legible, for one this has nothing to do with 'the' framework binaries and for two this has nothing to do with the framework binaries being tied somehow to VS.

Quote:

Or during the install one of the links could have been corrupted so "System.x" might not link to the correct library. If that's understandable.

The first piece of your post that, kind of, makes sense, congratulations. It is the bitter truth that binaries corrupted at any point, in most any circumstance, will no longer be usable - can you enlighten me though, on what this has to do with VS? Compiling, with any C# compiler, will give you the errorous results regardless of which environment you are running it from.

xavier · Jan 4th, 2008, 11:51 PM

Does it really matter ?
A friend installed .net 3.5 and the VS2008 beta environment was dead. Why ? other apps worked. He reinstalled VS2008 and everything was ok. Why ?

On my computer I installed .net3.5 - no problem here.

What i'm trying to say is that the environment was a variable that should be checked . Maybe it had something to do with it.

The OP fixed his issue - why he had to add a reference to the library, I still don't know. On my machine I don't have to do that.
.. let these be the little mysteries of life

@hollystyles - "simply typing "using System.Net.Sockets" is not sufficient as you have now discovered." - on my machine it is

.

Jabo · Jan 5th, 2008, 12:20 AM

Could it be Option Explicit or some other Option? Or is this even used in C#?

Jan 4th, 2008, 8:17 AM	#11
hollystyles Omlette du fromage Join Date: Oct 2007 Posts: 29 Rep Power: 0	Re: System.Net.Sockets Namespace Missing?? This is where uber tools like Visual Studio hide a little too much for beginners. When you start a new project some of the framework libraries are automatically linked (depending what type of project template you select) see the references folder in solution explorer. You need to add others yourself when they are required, simply typing "using System.Net.Sockets" is not sufficient as you have now discovered.

Jan 4th, 2008, 11:51 PM	#13
xavier Professional Programmer Join Date: Oct 2004 Location: .ro Posts: 383 Rep Power: 4	Re: System.Net.Sockets Namespace Missing?? Does it really matter ? A friend installed .net 3.5 and the VS2008 beta environment was dead. Why ? other apps worked. He reinstalled VS2008 and everything was ok. Why ? On my computer I installed .net3.5 - no problem here. What i'm trying to say is that the environment was a variable that should be checked . Maybe it had something to do with it. The OP fixed his issue - why he had to add a reference to the library, I still don't know. On my machine I don't have to do that. .. let these be the little mysteries of life @hollystyles - "simply typing "using System.Net.Sockets" is not sufficient as you have now discovered." - on my machine it is . __________________ Don't take life too seriously, it's not permanent !

Jan 5th, 2008, 12:20 AM	#14
Jabo Not a user? Join Date: Sep 2007 Posts: 272 Rep Power: 2	Re: System.Net.Sockets Namespace Missing?? Could it be Option Explicit or some other Option? Or is this even used in C#?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
namespace vs struct	Klarre	C++	8	Dec 29th, 2006 11:40 AM
C# corruption!!!	Kilo	C++	32	May 21st, 2006 8:44 PM
Help with this. Can you check what's missing?	DBZ	C++	2	Mar 17th, 2006 11:39 PM
Regarding namespace	aniruddha_dhondge	C++	22	Sep 29th, 2005 7:38 PM
C++ namespace question	kevin_cpp	C++	1	May 17th, 2005 3:28 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Programming Forums > Application Development > C#

System.Net.Sockets Namespace Missing??