Printable View
Hi. I would like to create an application that acts as an instant messenger without the use of other Instant messengers. So pretty much I want to build an application that sends and receives messages sent from the same application to the same application but on another computer. Would I use sockets? I am really confused because this is my first time using network programming. Any help or links would be appreciated! Thanks!
check out this post .. yes basically you could use the Winsock Control.
http://www.vbforums.com/showthread.php?t=297308
Been a long time....Anyway that looks like VB6 code to me. I was wondering anything in vb.net?
how hard can it be just get a textbox/richtextbox to send the text so someone's ip..and it the gets opened with an windows message box
Ya nice......how am i gonna access their ip? Because believe it or not most people don't know their friends ip address. So thats all I'm saying.
Hard enough that you can't provide a relative example or a glimpse of help. ;)Quote:
Originally Posted by Daemoncraft
The idea of a mesnger is that the two people on either end don't know each others IP (and really... shouldn't). The client systems should pass that information to the server and it should handle all of the relaying. In a tru IM program, both computers are clients that subscribe into a server. This will give you both an async state and also anonymity (real word, right?). FOr an intranet, this is an easy project, but when you add in proxies and seperate domains... It's a whole new game. Sockets are still the solution, but there's a whole new dynamic to it. If your problem is with the latter, I can't help you. It's beyond me right now. If everything is on an intranet, let me know where you're at and what you need. I have source code for both the client and server (in .net) and can get you going real quick.
How different is it from the VB6 code .. just curious ..?
anyway also check out vbip.com they have some .net stuff at the top of the home page ..
One word, framework.
More words, strict OOP dependency.
The way you do it in VB6 can work (with many pointless hours of hooking the same APIs). In .Net, there's basically.... A bunch of objects you literally confgure and handle their events. There's no real nitty gritty involved.
Ahh, ok i see .. yeah im a sucker for making it harder .. lol .. hence i still use Asp .. and not asp.net :D
though winsock in vb6 is pretty simple ..
Actually, that's good. ASP.Net is soo easy and simplistic that people forget about the ASP part. Having an ASP background is clutch when it comes to ASp.Net.Quote:
Originally Posted by rory
Guys.....could you help me in this thread? I'm the one with the big code....i should have put it in a zip file....oh well whats done is done....just read my posts.....something is wrong with either the client or server: http://vbforums.com/showthread.php?p...18#post2509918 starting on post 13.
check out the microsoft rtc sdk http://www.microsoft.com/downloads/d...F-DFA0ADF264AA. You may need a server os machine to handle all the presence functionality though.
Is this for use in Vb.net 2005? I haven't fully downloaded it yet.
its com based, but can be used from vb.net through interop. Next version of .net will have all this integrated, but this is all there is for the moment.