vb.net way of using .senddata

[r1chyb]

Am i right in thinkin this is the .net way of sending data is it winsock.send and not winstock.senddata?

What im trying to do is this.

WskIrc1.Send("USER RichyB21" & vbCrLf)

im having trouble with getting connected to irc you see. I get the following report in a txtbox

[]: Connecting to irc.bluehell.org port 6668...
[]: :kitty.bluehell.org NOTICE AUTH :*** Looking up your hostname...
:kitty.bluehell.org NOTICE AUTH :*** Checking ident...
:kitty.bluehell.org NOTICE AUTH :*** Found your hostname

[]: Username: 
[]: :kitty.bluehell.org NOTICE AUTH :*** No ident response; username prefixed with ~

[]: :kitty.bluehell.org 451 
[]: USER :You have not registered
:kitty.bluehell.org 451 
[]: MSG :You have not registered
:kitty.bluehell.org 451 
[]: JOIN :You have not registered

Anyone have an idea of thats going wrong?

[Atheist]

the .Net way of sending data through TCP/IP doesnt involve any winsock controls at all, like I told you guys in this thread, you shouldnt be using 3rd party components to do something that is already provided in the framework.
It will save yourself future headaches and make yourself a better programmer.

[r1chyb]

Well whats the .net way of doing it.. system.net.sockets then what?

[Atheist]

You use the System.Net.Sockets.TcpListener for server applications, and System.Net.Sockets.TcpClient for client applications. Search the forums and/or MSDN. There are many examples, I know because I've posted many of them.

[Campion]

you shouldnt be using 3rd party components to do something that is already provided in the framework.

People upgrading from VB6 to VB.Net aren't going to get how to do it the .NET way, and would take a while to understand what's happening--even with examples. Why not have a familiar face until they are competent enough with .Net to be able to handle network sockets and the related coding? When the time comes, they can swap out code. There's no need to be bitchy about it.

Also, VB is supposed to be a rapid development tool. When you force people to code something in a way that they don't understand without decent documentation, then it stops becoming a rapid development tool, and instead turns into an I-gave-up-because-people-think-there's-only-one-way-to-code-things-and-expected-me-to-follow-to-a-T-and-it-slowed-my-learning-down-so-much-I-downgraded development tool.

[timeshifter]

People upgrading to .NET are doing it FOR the .NET way! Why else would you bother making the upgrade? .NET is much more powerful, has so much more included in it, and it makes using it so much easier. If you're going to insist on using VB6 methods in a world with much better possibilities, then I question why you're programming at all.

[Atheist]

People upgrading from VB6 to VB.Net aren't going to get how to do it the .NET way, and would take a while to understand what's happening--even with examples. Why not have a familiar face until they are competent enough with .Net to be able to handle network sockets and the related coding? When the time comes, they can swap out code. There's no need to be bitchy about it.

If you think I am being bitchy then Im sorry but thats your problem. I am just pointing out that its completely unnecessary to go learning how some 3rd party component work when the time could be spent learning how the built in classes work. You shouldnt delay the learning because its convenient to do so. The way you see it, it would be perfectly ok to use nothing but VB6 syntax in a VB .Net application, would it not? Then why move to .Net in the first place?
The support and documentation is also a million times greater if you stick to the .Net classes.

Also, VB is supposed to be a rapid development tool. When you force people to code something in a way that they don't understand without decent documentation, then it stops becoming a rapid development tool, and instead turns into an I-gave-up-because-people-think-there's-only-one-way-to-code-things-and-expected-me-to-follow-to-a-T-and-it-slowed-my-learning-down-so-much-I-downgraded development tool.

Without decent documentation? You cant be serious, have you ever visited MSDN?
And about forcing people to code in ways they dont understand. This is .Net isnt it? I am not forcing anyone to do anything, but I assumed that as a programmer, you want to learn how to do things yourself. You are right, it is a very fast way to code if you keep downloading premade code from the net, but are you learning from it? Will you be able to modify it? Will you be able to fix it when a bug occurs? No, no and no. These 3 no's will certainly halt your "coding speed", eventually.

I'm just trying to help people write good code, but apparently thats not appreciated.

[Campion]

People upgrading to .NET are doing it FOR the .NET way! Why else would you bother making the upgrade?

I should rephrase it to say "know it off the bat" which a lot of upgrading programmers AREN'T going to know. There's more to upgrading than the .NET way. A lot of it is to ensure compatibility with Vista. Sure, there are work arounds to get VB6 apps working on Vista, but that's tedious.

Without decent documentation? You cant be serious, have you ever visited MSDN?
And about forcing people to code in ways they dont understand. This is .Net isnt it? I am not forcing anyone to do anything, but I assumed that as a programmer, you want to learn how to do things yourself.

Yes, MSDN is useful, but only when you can find what you are looking for. The availability of information one get for free from MSDN Online is limited, and they were only verbose enough to comment the code, but little else. I, for one, am NOT going to shell out the money they want every year so that I might have access to better docs.

Now, as far doing things for oneself, for the most part that's true, there are a lot of hard things that most people are NOT going to be able to program no matter how they try. And then there are simple things that would take some people AGES to figure out, while very complex things come easy to them. It's all relativity.

[r1chyb]

.Net is alot harder to pick up i think, I mean i wasnt a pro at vb 6 but i no .net is the way forward, and Yes i no using 3rd party program's maybe a easy fix but it does give me a starting point.

Thanks everyone for your posts