C# - Register Application

[Demantor]

Omg, this is nothing!!!

in vb:

webbrowser1.navigate(textbox1.text)

IS THIS SOMETHING? Answer: No.

[Guy]

Purple, you should just use ASP.Net (Visual Web Developer) and create your own User Creation Wizard.

~Vengeance

ASP.NET is meant to be used for server-sided scripts; not browser-type applications.

[Tyggo]

Correct, but he wants to make a register app, so PHP or ASP would be the beat choice.

~Vengeance

[Guy]

Correct, but he wants to make a register app, so PHP or ASP would be the beat choice.

~Vengeance

No, he wants to make a program that accesses the registration script, not the actual script itself.

[frenchfatcat]

0/10 srry... very bad. besides when it redirects all they have to do is right click the web browser and hit properties.... and yeah it fails.

didn't we discuss this on msn, about a similar thread on GZP?

[X-Weaver]

o.o nice xD this is like a local web register xD

[Joe9099]

This is just a cheap way of trying to get past sql injection, but its not going to work.

[Guy]

This is just a cheap way of trying to get past sql injection, but its not going to work.

No, that's not the point - the point is to look "pretty".

And, this does nothing to sanitize data before it's sent.

[4ndr34s]

.... nice "release"

[XZeenon]

This is just a cheap way of trying to get past sql injection, but its not going to work.

Well... I tried that the other day... And I'm not sure if it worked or not because I don't SQL Inject. I released it. Where you enter your data hit submit and tada.

[purpleCRAYON]

The point of this it to stop regpage spamming, that's why I said use an invisible redirect so even if they do the right click -> properties, then it will show the URL to the invisible redirect. Which you can change if your page starts getting DDoS'd.

The MAIN point of this it to just have it bundled in with your client, so once it is installed just double click the application, register, and then they can play.

[Guy]

The point of this it to stop regpage spamming, that's why I said use an invisible redirect so even if they do the right click -> properties, then it will show the URL to the invisible redirect. Which you can change if your page starts getting DDoS'd.

The MAIN point of this it to just have it bundled in with your client, so once it is installed just double click the application, register, and then they can play.

There's no such thing as an "invisible redirect" - there's different types of requesting a redirect (HTTP tag w/REQUIV attribute, scripting via J/VB, "Location" header, etc), but all are visible some way or other.

Regardless, you launching a distributed attack on one page would be pointless - the server would continue to get flooder, only requests wouldn't be processed; still resulting in a flood causing damage.