Where should I start?

07/30/2012 23:24 ProperCodes#1
I know i've posted quite a lot recently but I have been wanting to discuss a few things so I am letting some stuff out. ANYWAYS! What I would like to ask now is I have decided to try learn to make a source for Conquer obviously. Where should I start on the source? Like should would I begin? I know more than the basics of coding C# and this will be my first time on starting my own source. If you can list where I should start it would be great. :)
07/30/2012 23:35 diedwarrior#2
Well, it depends really, its always better to study the language itself before attempting co stuff, but I didn't do that, all I did was like study a source for 6 months, I ended up doing pretty awesome stuff on it, but yeah, if you just want to do stuff for co, then I advice you to get a proper source and start looking at it, if otherwise, then just look for any guides online :).
07/31/2012 01:10 _DreadNought_#3
Learn how a source works first and the answer is simple.

Noone will tell you, its very obvious if you know how it works

Client connects to server
--They transfer packets--
Client or server closes the connection.

Rather simple to see what comes first.
07/31/2012 02:14 InfamousNoone#4
Quote:
Originally Posted by ProperCodes View Post
I know i've posted quite a lot recently but I have been wanting to discuss a few things so I am letting some stuff out. ANYWAYS! What I would like to ask now is I have decided to try learn to make a source for Conquer obviously. Where should I start on the source? Like should would I begin? I know more than the basics of coding C# and this will be my first time on starting my own source. If you can list where I should start it would be great. :)
Use another source as reference material, and from that start building your own. Even if you're taking pieces from the other source code, so long as you're re-writing a majority of it, you'll be learning something.

Btw, suppose that a structure Foo implements IFoo. Foo contains only primitive data types, none of which are string. Foo's method SomeCall() -- which is defined by IFoo makes a pinned statement, i.e.
Code:
fixed (Foo* pThis = &this)
Suppose that an instance of Foo is casted to IFoo and later on the instance of IFoo invokes SomeCall() is the object unboxed y/n, explain.
^ it's stuff like this you should be researching if you're interested in making a server; I wonder how many people can answer this properly w/ out using Google o: