C# ConnectServer Source

i coded this yesterday for my emulator, and i'm releasing this piece of code for those which want to know more about C#, sockets, blablabla...

this isnt 100% working like original, the server % will aways display 0, coz i haven't coded the UDP socket packets (future updates will be for emulator, not official server files, so i dont need to code udp for display emulator's playercount %)

if someone "update" the code, post it here

thanks... file is attached, and please, do not remove my team name from it, if you will repost in other place, or change the code


server list in CsInfo.xml

Code:

---

<?xml version="1.0" encoding="ISO-8859-1"?>
<Servers>
        <Server Code="0" Index="0" Address="127.0.0.1" Port="44405" />
</Servers>

---

Code = Server Index
Index = SubServer Index
Address and Port is target gameserver info


file is attached...

Another Great release, thank you :)

If Anyone Needs:
MIRROR LINK

Quote:

---

Originally Posted by Shagoon

If Anyone Needs:
MIRROR LINK

---

thanks for the mirror

Quote:

---

Originally Posted by Shagoon

If Anyone Needs:
MIRROR LINK

---

Tanks :) so fast :p

Man, I was looking upon it, I started learning the C# basics and my first project will be a MU Emulator (Obviously when I learn more complex things), the first time I saw your project in VirtualMU I start being your fan! ^^

SHAGOON always is first with mirrors! :)

Woot, very nice piece of emu :D

nice work man! =)

well, a connect server isn't an "emu", but anyways... i'll use it on the project

Perfect, grateful Wolf.
Now I am going to my tests

Thanks Bro

very hackish :\ still can be interesting for those who want to learn the very basics of mu protocol.

Thanks ;)

Can't open !

looking good. I`m sure i will test it

Quote:

---

Originally Posted by sontung306

Can't open !

---

use visual C# express 2008 to open it

I have a recomendation for your project

Everyone ever involved on server maintenance and deployment is used to have "Services" running.
Those Services have some advantages:
- windows resources priority
- security (login account) can be especified
- what to do in case of services shoot down
- system login of each event
- RPC (windows security protected)
and a very long list of extra positive things so developers use to release mission critical and long term server based tools compiled as "windows services".

So why not you?

The main problem will be "support" on how to install and remove a windows service, but install/uninstall classes can be coded inside the exe so people can attach/dettach the service from the OS as a optional feature.

U whant me to help with this?... just let me know

wolfulus can you DC a client from the CS if you want to ?

Quote:

---

Originally Posted by sandbird

wolfulus can you DC a client from the CS if you want to ?

---

if you code it, yes you can, but the current code is a console application, without interface... just a tray icon, with a "hided" console window...

Quote:

---

Originally Posted by FT1FT1

I have a recomendation for your project

Everyone ever involved on server maintenance and deployment is used to have "Services" running.
Those Services have some advantages:
- windows resources priority
- security (login account) can be especified
- what to do in case of services shoot down
- system login of each event
- RPC (windows security protected)
and a very long list of extra positive things so developers use to release mission critical and long term server based tools compiled as "windows services".

So why not you?

The main problem will be "support" on how to install and remove a windows service, but install/uninstall classes can be coded inside the exe so people can attach/dettach the service from the OS as a optional feature.

U whant me to help with this?... just let me know

---

maybe on future updates... i'm not thinking about these things now, just wanting to get it fully functional :]

yeah, bad english, i know, sorry ;D

Another advice:
Working with a fixed count of connection slots is not resource wise.
if you are going to work that way you must at least let the server manager to chose how many connections allow as a parameter so your line:

Code:

---

private DtClient[] Clients = new DtClient[100];

---

become:

Code:

---

private DtClient[] Clients = new DtClient[globalVariableMaxConnections];

---

I will recommend the use of thread pools instead of fixed count

Another Project Started by me one year ago coded in C++ if your wanna try here is SVN Repository https://opensvn.csie.org/DareEMU/

thansk a lot . usefull

thanks a lot