ASP.NET EoCRM(Administration Panel)

Sorry for the delay. Been having some DDoS issues...coughdopeflyffcough.

UPDATES:

  • DataTables integration
  • Account Searching
  • Multiple Cluster Support
  • Fast Column-by-Column Sorting
  • Result Searching
  • Account Details added
  • Some donation management features are done

Mootie - ASP.NET EoCRM(Administration Panel) - RaGEZONE Forums



Mootie - ASP.NET EoCRM(Administration Panel) - RaGEZONE Forums
 
Sorry for the delay. Been having some DDoS issues...coughdopeflyffcough.

UPDATES:

  • DataTables integration
  • Account Searching
  • Multiple Cluster Support
  • Fast Column-by-Column Sorting
  • Result Searching
  • Account Details added
  • Some donation management features are done

Mootie - ASP.NET EoCRM(Administration Panel) - RaGEZONE Forums



Mootie - ASP.NET EoCRM(Administration Panel) - RaGEZONE Forums
Nice Mootie :thumbup1:
Are you fixing it/Improving or remaking it?
And are you using Apache to test?
If so can you explain how? I had to try EoCRM trough iis(I dont like it for testing)
 
Nothing is wrong with IIS if it makes it easier for you. Personally, I've worked for years with Apache and only recently in the last 8 years have I done ASP. The interfaces are like day and night to me. Almost everyone wants PHP and Xammp, Wammp, Lammp experience so I stuck with it. It doesn't mean I can't use ASP however.

Its really a personal preference.
 
Well, I do like the management console for IIS7, it's all very organized and I can usually find what I need within seconds (especially with php manager, for lazy editing of php.ini without having to find the file xD)
Also, I'm not sure which it is (my linksys router, Windows Server 2008 R2 OS, or IIS7 webserver), but something has my server immune to DDoS (DDoSing the server itself, not any address you hit before the server). I've had people test DDoS on my server and my server wasn't effected.
 
Well, I do like the management console for IIS7, it's all very organized and I can usually find what I need within seconds (especially with php manager, for lazy editing of php.ini without having to find the file xD)
Also, I'm not sure which it is (my linksys router, Windows Server 2008 R2 OS, or IIS7 webserver), but something has my server immune to DDoS (DDoSing the server itself, not any address you hit before the server). I've had people test DDoS on my server and my server wasn't effected.

Facebook isn't immune to DDoS. IIS does handle DDoS better than Apache traditionally though. I'm not sure about with mod_evasive, but I'm currently using litespeed(I plan to switch to IIS7.5 eventually). The issue is the bandwidth that the DDoS attack consumes. It's quite difficult to block multi-gigabit attacks when your uplink can't pipe it.

In my opinion, Apache should never be used for any sort of enterprise(if you run an MMORPG, you should be working as though it is an enterprise). IIS is much better for scalability, security, and (in general) performance.

Also note that this project is ASP.NET. Apache has support for ASP, not ASP.NET. Looking at benchmarks and personal experience, ASP can't compare to ASP.NET. PHP can compare only because of the flexibility of runtime-compiled code(ASP.NET's performance, features, security, and scalability outclass PHP as well).

The main reason I like ASP.NET is because it allows a better object oriented interface than PHP by integrating C# code into the project. The strongly typed aspect is another big plus that PHP doesn't offer. PHP code just gets messy too fast.
 
To better elaborate.

ASP is Microsoft's proprietary language for server development maintained by their professional and highly paid programmers.

PHP is open sourced and while it does have a lot of talent driving the language it is not as organized nor as professional as Microsoft's team.

However, people are starting to turn away from ASP more and more and PHP is gaining a substantial lead. Big enterprises are looking for more flexibility as well as the security it needs. As stated, ASP is more reinforced against attacks than PHP but its not invulnerable. Its been stated on the internet and around many offices I've consulted with that soon it may be gone with all the new mobile technology and newer languages coming out all the time. Time will tell.

I prefer ASP programming because it feels much like the programming I've been doing for years. PHP feels a lot like C++ mixed with Javascript.

And for the record, I wouldn't go around stating your system is impenetrable to DDoS. There are many ways around walls. There are hackers out there who spend all their time trying to get this accomplished. Something you want to keep in mind, especially around here.
 
Thanks Lethal, for telling me how good IIS7.5 is lol I honestly didn't know, just figured it'd be the better choice over apache or something else. And yes, I know about the bandwidth issue with DDoS, I'm just saying that with one person testing it, my server didn't lag at all. If multiple did, then idk.

Glaphan, I didn't say my server is impenetrable, I merely said that a few people have tested it and the server didn't show any effect. If many did it at once, it might have, but I really don't know. Besides, even though I did say what I did, it's not like I'm advertising my server address for people to go and try it lol
 
- Project Info -

For the last couple days I've been working on recoding EoCRM(official flyff management panel) in ASP.NET. This would offer countless security, performance, and compatibility improvements if done properly. I'm new to ASP.NET/C# but C# is very similar to C++, which I've been coding for awhile.

Out of general interest, what're you using? the MVC Framework or just general ASP.net? You said you created a custom MSSQL framework and method of handling cookies/sessions - what led you to these decisions rather than using the in-built methods like LinQ?

Facebook isn't immune to DDoS. IIS does handle DDoS better than Apache traditionally though. I'm not sure about with mod_evasive, but I'm currently using litespeed(I plan to switch to IIS7.5 eventually). The issue is the bandwidth that the DDoS attack consumes. It's quite difficult to block multi-gigabit attacks when your uplink can't pipe it.

In my opinion, Apache should never be used for any sort of enterprise(if you run an MMORPG, you should be working as though it is an enterprise). IIS is much better for scalability, security, and (in general) performance.

Also note that this project is ASP.NET. Apache has support for ASP, not ASP.NET. Looking at benchmarks and personal experience, ASP can't compare to ASP.NET. PHP can compare only because of the flexibility of runtime-compiled code(ASP.NET's performance, features, security, and scalability outclass PHP as well).

The main reason I like ASP.NET is because it allows a better object oriented interface than PHP by integrating C# code into the project. The strongly typed aspect is another big plus that PHP doesn't offer. PHP code just gets messy too fast.

It's nice being able to leverage the .net framework too, with all its libraries, and language interoperability allowing you to code in C#, C++, VB, F#, Python, Ruby, etc depending on what's the best language for the job.

Personally, I find lighttpd or nginx to be the best choice for a web server in high-load environments. There's a lot to be said about the event-driven model in web programming. Especially if you're on a project which requires something like long-polling (obviously not something like this though!).

Also might be worth noting that you can actually get ASP.net to work on other web servers than IIS (including apache).
To better elaborate.

ASP is Microsoft's proprietary language for server development maintained by their professional and highly paid programmers.

PHP is open sourced and while it does have a lot of talent driving the language it is not as organized nor as professional as Microsoft's team.

However, people are starting to turn away from ASP more and more and PHP is gaining a substantial lead. Big enterprises are looking for more flexibility as well as the security it needs. As stated, ASP is more reinforced against attacks than PHP but its not invulnerable. Its been stated on the internet and around many offices I've consulted with that soon it may be gone with all the new mobile technology and newer languages coming out all the time. Time will tell.

I prefer ASP programming because it feels much like the programming I've been doing for years. PHP feels a lot like C++ mixed with Javascript.

And for the record, I wouldn't go around stating your system is impenetrable to DDoS. There are many ways around walls. There are hackers out there who spend all their time trying to get this accomplished. Something you want to keep in mind, especially around here.

Actually, this is incorrect.

ASP is dead. If any new applications are being developed in it, the development team are either
a) Idiots
b) Have specific business interests

ASP has been more or less completely superseded by ASP.net, which, as the name may suggest, is part of the .net framework. Whilst the original asp is a language in itself, asp.net is a bunch of languages and technologies which allow you to develop web applications. ASP.net is under active development, has support from Microsoft, and has the .net framework (and associated development) behind it too. This leads to better security, faster updates, more flexibility and power, etc. Especially when you couple it with good coding practices like the MVC framework.


PHP is also not used in companies a massive amount (or at least, not here). If they're large corporations they tend to opt for sites in Java or C# (asp.net) because it has massive corporate backing (from oracle or MS) which obviously provides a hell of a lot of insurance. Companies trust them quite a bit. There also may be the advantage of having other technologies in the company in .net or Java, and there's a considerable advantage to having your stack in one language/technology. In general, they're enterprise level solutions.
Small start ups tend to go for more Agile solutions like Python, Ruby or node.js. They don't have the same risk associated with going with those newer, open source solutions and they need the faster development speed. Like Java/.net fit the enterprise level development group, these languages fit the web start-up philosophy very well.

PHP sits in the middle. That's why it tends to be used by companies who make sites for other people and small (non-tech) companies. Its cheap to host, relatively quick to develop, cheap and easy to get developers (usually not quality ones though), and stuff like that.

PHP is also not 'more secure' than ASP. Whilst ASP.net has built in components to handle passports, windows based auth, and a ton of other stuff like that I'm fairly sure that original ASP doesn't. In essence, your security is likely to come down to the application based code which means your programmers competence with the language, and the structure you use with your code, are much more likely to be important. PHP can be messy as hell, but you can also code it well (aka - using a framework).




In regards to the actual project, I'd be interested, but only if it were open source completely, and if it uses ASP.net MVC (not just standard webforms).
 
Back