Any VB.NET account creation projects with code?

I'm looking for a VB.NET (preferrably Visual Studio 2008) project that deals with some sort of account creation like a Gmail account creator, Yahoo account creator etc. so I can take that code and make several other different kinds of account creators with it. Can anyone help?

Look into the webbrowser object.. With this you can simulate actual user behaviour such as filling out and submitting forms..

I wrote a multithreaded AOL creator with proxy support but it took allot of work so I cant just give away the source code. I used the chilkat http library, you can find it with a serial on almost any warez forum. GL

I just started programming less than a month ago.
I've made a bot that tells me how many twitter followers all my accounts have.
I made one to submit articles to AC
I made a couple of other ones to manipulate files offline.

Anyways, It is really kind of easy.

Please note my programs are super basic. Using mshtml webbrowser. No multithreading or webrequests for me yet.

Learn the basics - multithreading, webbrowser automation, webrequest and then invent the things for yourself. There's no ready made samples, as this is very small niche compared to other softwares, and you can't just hit up some VB/C# forums with the question "How do I make a bot..." because these people and forums are pussies and don't anything "illegal" such as bot creation

hi

first navigate to your sign up page

then you can fill every textbox with your content. but you must know
the id of the box in the browser (use firebug plugin in firefox)

after you have the name of the textbox in the webbrowser
use this code to fill it


to submit the form use

don't bother with web browser objects. you will get much more power out of HTTPWebrequest in the System.Net namespace.

that being said, HTTPWebRequest is crappy (better than the web browser object though) so ideally a long term solution would involve learning the actual sockets namespace and the functionality exposed within.

the sockets namespace is pure sex when it comes to web interaction.

trust me, it's a lot to grapple with, but in the long run it will give power and flexibility that you just can't get from webbrowser or httpwebrequest.

here are some links to get you started:

hxxp://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.aspx
hxxp://msdn.microsoft.com/en-us/library/system.net.sockets.aspx

can you post a demo code?

coolcurrent said:

can you post a demo code?

Click to expand...

creating your own HTTP wrapper class for System.Net.Sockets is way outside the scope of a thread like this. if you read the links that i provided it will give you a good base and you can find a lot of good articles on google to help you develop it out.

i'm not going to sugar coat it, it's not an easy thing that you can do in 10 lines of code but it is an incredibly powerful thing that can give you great experience and understanding of the nuts and bolts of making a truly excellent bot.

Being that it's a class can you create the wrapper class once and use it for all the sites that you are going to be interacting with during the coding process?

Ex: I may start out with a bot that programmically enters my information and creates an account on 10 sites but over time I want to be able to add more sites to the list....will creating a wrapper class be flexible enough to apply to all sites or just the ones that I created during the coded time?

Thanks

simpleonline1234 said:

Being that it's a class can you create the wrapper class once and use it for all the sites that you are going to be interacting with during the coding process?

Ex: I may start out with a bot that programmically enters my information and creates an account on 10 sites but over time I want to be able to add more sites to the list....will creating a wrapper class be flexible enough to apply to all sites or just the ones that I created during the coded time?

Thanks

Click to expand...

if you're smart about your architecture and design you can make completely re-useable and site agnostic. the wrapper class abstracts the bare implementation of the sockets namespace and allows you to create your own objects, structs, and the like the pass in to the wrapper class.

this is fun because it lets you design something that you can interface with the way that you want too.

an over simplistic example would be creating a method called "request" that accepts an object of type "request information" and then uses that to initialize all your params for the socket calls and parse and return responses in a more friendly and re-useable manner, as opposed to duplicating the raw socket calls and stream writes each and every time.

You down with OOP? Yeah You.Know.Me()