I came in here because you're upgrading the site and stuff

[u_name]

Knowledge in HTML, CSS, ASP.NET, and MySQL. JavaScript is a plus.
Knowledge in the security in ASP.NET and MySQL to avoid security holes on the site
2+ years experience in programming and/or web design.
Very organized with their code.

HTML, CSS, Javascript, MySQL are whatever but why ASP?

[GoldenPower89]

Nice, nice. Looks like K7 might finally have some help.

[Redhollowlives999]

Awesome.


You still have to play the game before I accept you as a user and a human being.

[Zup]

maaaan lemme tell u i found hella job listings for u in my area

[u_name]

Somebody is hella hecka from the http://bay.area.jpg.to

[K73SK]

Because the site will be based in ASP.NET since I'm fluent in C# (and it's easier to manage IMO).

[u_name]

If you do it in PHP, you will have my sword.
What will you use for a repository? Github, bitbucket, some other third thing?
Also, just an idea, but if you do it in PHP, you can tie features from the forum into the site (because phpBB runs on php).

[meth962]

Ahh C#. My fav, and what I built all the Legaia tools out of.

[K73SK]

We're going to be throwing out the phpbb forums and redesigning the new site to tie in users from both the main site and the forums. Of course, I'll be sure to program it so that all information is transferred, but not yet. And I'll be simply transferring this site host to another one that runs on Microsoft so that I can just work on the C# version of the site alongside this one at the same time. Originally I was going to use a repository, but decided that this was easier.

[u_name]

It's my opinion that one should avoid Microsoft products when it makes sense. If you were doing a client-side application that was going to be running as an executable, I would say that using C# makes sense; however, in the case of server-side scripting/programming, I think you would find it more beneficial to be able to leverage all of the tools that already exist.

But even considering this, I would say the most crucial point is that if you run into a problem with a Microsoft product, you can only debug so far on your own before you hit the proprietary wall. With open source, you can go as far as you need to. If it's too tough, then you can talk to the community that maintains that particular tool, instead of "Microsoft Experts".

I didn't realize you had user registration on the main site. What's that for?