C# Video Tutorial

[Santa]

Originally Posted by unknownone

As Tao suggests, your understanding of Flush() is flawed.

You need practice pronouncing "binary".

"Can't read as plain text" is not a reason why binaries are good, in fact, it's one of the major disadvantages. Reduced size is an advantage, but you missed what are the main advantages of binary files - Direct, rather than sequential access.

Why are you using words like "encrypt" and "decrypt" in a cryptography-free context?
Hint: You should be using words like Serialization and Marshalling.

There's no need to close a filestream if you've closed the reader/writer attached to it (closing a reader auto closes the underlying stream).

The video I watched generally fails what it was meant to teach. It's just apparently someone watching you write code without any real explanations to what is happening.

As a tip, get someone who knows what they're talking about to review your guides before you release em (or before you bother recording them even). People here who don't know what they're doing (like the above poster), assume it's like something written in the bible, and will copy you religiously, including all your mistakes - not good teaching material.

Hmm. Why don't you make some tutorials?

Originally Posted by Zion~

I beg to differ.

Really? You took all that time to post something completely useless? If you can do so much better then do it.

Originally Posted by _legitimate_

i will be making a video tutorial on this soon, my intro will be "duhhh daa duuuhh is you went to lern to code like profezionel? den dis is da rite video for jou. if you went to meke a npc den u need to encrypt da stoopid ting called file npc.ddl i tink"

Your a doucher.

[SimplyPerfection]

Originally Posted by _tao4229_

Your description of 'flush' is really off.
Also, considering you're not writing UInt32's you really shouldn't be reading them - you're writing signed integers by default.

Yeah, I know, sorry. The main thing I wanted to show was how to read and write binary, and the values are obvious for themself, such as level(0-255) - byte, UID - uint etc etc.

@unknownone
Well, as I'm not an english speaking person, and I have never been in the need of words like that, I did not know them.
Although, I also explained that I didn't know the correct word for it. Thanks anyways



I'll try to explain stuff a bit more in the upcoming tutorials.

[elmo3zeb]

Useful Ranked 5/5 and Thanked

[SimplyPerfection]

Originally Posted by elmo3zeb

Useful Ranked 5/5 and Thanked

Thank you!

[unknownone]

Originally Posted by StarBucks

Hmm. Why don't you make some tutorials?

Reinventing the wheel. There's already plenty of tutorials for pretty much everything, and if anyone was serious enough about learning, they'd search for them, rather than waiting for the videos to come to them.
If you do have a topic for which you cannot find a tutorial and want one, provided I have the knowledge, I wouldn't mind putting a video together.

Originally Posted by SimplyPerfection

@unknownone
Well, as I'm not an english speaking person, and I have never been in the need of words like that, I did not know them.
Although, I also explained that I didn't know the correct word for it. Thanks anyways.

binary is pronounced with bi as in biphasic, bisexual, bicentennial etc. ()

As for the writing/reading of ints, it's pretty much irrelevant, since there's no concept of sign for stored memory values. Sign only matters for arithmetic and such when compiled down to assembly, so provided you have the right casts in place then, it doesn't matter how you read/write em to a file.