MP3 Skull Searcher (Download MP3 Instantly + ProgressBar)

[Jason]

2 Things:
1) In this case, yes he should rename the controls. But i think it's important that people realize that you shouldn't ALWAYS rename the controls to something predictable. When you go to release and sell a compiled work, it makes a pirate/cracker's job easier when you've renamed your login button to "LoginBtn"
2) I've never seen an issue with disabling CheckForIllegalCrossThreadCalls besides people bitching at you for doing it and calling you lazy. But i have yet to see a case where it really jeopardizes program functionality. Would you be willing to expand into how it could cause problems for people?

1) I guarantee that renaming your controls is not going to make a crackers job any easier than it already would be if you're releasing plain, unobfuscated .NET binaries. If you're using an obfuscater it will already randomize things like controls names for you. No need to sacrifice your codebase's readability for the illusion of security that a toddler could break

2) Read here for just some of the reasons why turning off CheckForIllegalCrossThreadCalls is bad practice, lazy and should be avoided.

[Sixx93]

good job, tryed and works well!