Rules & Guidelines (READ FIRST)
Rules & Guidelines (READ FIRST)
Standard Rules:
1. Your Releases Should:
Be Uploaded using the attachments feature provided by mpgh.net
(If for some reasons a upload to a sharing site is absolutely necessary
you must get permission from myself or a mod, Do not just post the link)
Include at-least (1) Screenshot
(if your application has multiple features or extra forms, another screenshot may be warranted)
Virus scans are now automated — MPGH scans every uploaded archive with VirusTotal and shows the verdict on the download button, so you do not need to include scan links.
(if you use another VirusScan Site, We may require a VirusTotal
Scan as well)
2. Don't flame anyone, especially if there is no reason for it
(intentional baiting or flaming posts will be deleted, and I will contact the mod about which actions to take)
3. Do not spam at all and always stay on topic
(spam posts will be deleted, granted there is some leniency as it is possible to go off topic, and I myself do it on occasion, I am referring to way off topic posts or comments )
4. Do not bump your thread if you do not get a quick response.
5. Do not intentionally double post
( I realize that on occasion it may occur unintentionally , however use the edit button when you need to make or add a comment)
6. No advertising: Including Programs that open up a website other than mpgh, and posting advertisements in the post, or program.
(advertisements will be removed, as well as any images containing advertisements )
7. Leave the Modding and Minion(ing...?) to those appointed to do so,
if someone breaks the rules, report them via PM or VM to to the appropriate section's minion.
8. Do not create a thread for a simple question similar to one already asked (search before posting)
9. Anti Leech (per Why06 with Daves Approval)
Link:http://www.mpgh.net/forum/31-c-c/127...ml#post1697018
Guidlines: - These can help us help you
- USE SEARCH FIRST!
- BE DESCRIPTIVE
1. Explain to us what your code does ( or in most cases, what your code supposed to do)
2. Explain to us what exactly the error is. Vb.net allows you to copy the error by right clicking and clicking copy in the fly out menu
If you do not know the error, catch the error and tell us what it is saying , to catch a error use
Code:
Try ' Your code here Catch Msgbox (ex.message) End Try
3. Keep in mind that you know more about your code then we do, don't assume just because we understand code, that we will understand what you are attempting.
MAKE YOUR TOPIC NAMES UNDERSTANABLE AND NOT MISLEADING
Post a descriptive topic name!
Example: [Help]Syntax Error in my injector
[Question] Why is my application crashing
Give a short summary of your problem in the subject. Don't use attention getting subjects, they're not fair to other users!
Things like "HELP ME NOW!" or "URGENT", "OH MY GOD HELP!!!!" make your post unfairly look like a priority over other users post who need help just as much as you.
- BOLD THE CODE WITH THE ISSUE
If you post your whole code, try to figure out where the error is coming from, and mark it with bold tags
Code:
Use [B] [/ B]
PUT YOUR CODE IN HIGHLIGHT BRACKETS OR CODE BRACKETS
Very often we see people post a huge ugly eye sore of a code that lacks any real sence of professionalism with no notations, not seperated or tagged, lacks in declarations and then they take that horrible piece of code and paste it right into the message.
There's a problem with that - tabs and spacing don't show up properly That makes it really difficult to read.
There's a really "Cool" code and highlight tag built in that will format your code when you post it. You can use that easy highlight=vb.net Tag or Code tag or buttons right above the box where you type your message. The result will look like this:
Code:
Dim MyMsg as new msgbox ("hello world")
If textbox1.text = "message" then
mymsg
end if
Code:
Dim MyMsg as new msgbox ("hello world)
If textbox1.text = "message" then
MyMsg
End if
IF YOU GET AN ERROR ON A CERTAIN LINE, TELL US WHAT'S ON THAT LINE AND THE LINES ABOVE AND BELOW IT
It's not too helpful when you mention an error on a certain line but don't tell us what code is on that line. Because errors can sometimes be caused by lines of code above or below the one the error is mentioned on, please post those lines as well.
IF YOU ARE NOT GOING TO TAKE THE ADVICE, DON'T ASK FOR HELP
REMEMBER THAT WHEN PEOPLE HELP YOU, THEY ARE DOING YOU A FAVOR
Nice one NG, although I don't really agree with this:
Originally Posted by NextGen1
Visual Basic Section - Should be used for discussing Visual Basic Codes, Help with Visual Basic Codes, To share a release or code snippet created in Visual Basic.
(No Tutorials or Tutorial Requests)
No-one ever looks in the tutorial section, they come to the specific section first and if they find no tuts there they just ask a question about it regardless. 
Originally Posted by NextGen1
Visual Basic Section - Should be used for discussing Visual Basic Codes, Help with Visual Basic Codes, To share a release or code snippet created in Visual Basic.
(No Tutorials or Tutorial Requests)
Purpose is to increase traffic to other sections, we have a tutorials section with 0 activity and a tutorials request section without any activity.
defeats the purpose of the sections. Members need to get used to using it. There was a time where everything was moved where it should be, Pixie (when he was minion) didn't care what section it was in, So eventually tuts began dwelling in this section, and what was (decently) active has no activity.
defeats the purpose of the sections. Members need to get used to using it. There was a time where everything was moved where it should be, Pixie (when he was minion) didn't care what section it was in, So eventually tuts began dwelling in this section, and what was (decently) active has no activity.
awesome as always, richy 
Originally Posted by NextGen1
No block level vB code tags (e.g. [code], [qute], [vb], [php]) are allowed in signatures, and signatures should be no larger than 3 or 4 lines.
@Xscape, Ignore that.
It was a rule that doesn't apply, it was from my old minions day when I first asked about size of sigs. But it's not enforced, I C&Ped from one of my documents , forgot that was there.
(side note, I posted 50 posts today and my activity dropped 2 %)
It was a rule that doesn't apply, it was from my old minions day when I first asked about size of sigs. But it's not enforced, I C&Ped from one of my documents , forgot that was there.
(side note, I posted 50 posts today and my activity dropped 2 %)
Originally Posted by NextGen1
@Xscape, Ignore that.
It was a rule that doesn't apply, it was from my old minions day when I first asked about size of sigs. But it's not enforced, I C&Ped from one of my documents , forgot that was there.
It was a rule that doesn't apply, it was from my old minions day when I first asked about size of sigs. But it's not enforced, I C&Ped from one of my documents , forgot that was there.
/
Caught an error, fixed it.
Caught an error, fixed it.Ha, I see what it was. 
