port to .net and C# and SQL server

[bound4doom]

Just curious if anyone has worked at porting some of this into C# and SQL server instead of mySQL.

I have done this with some of the pieces of the code by moving it out into com dll done in .net. Of course you take the performance hit right on startup as the IL compiles but once it is up and running well it is fast. As far as database well I ported the whole thing over to SQL server 2000 a while ago. Which is a heck of a boost in itself however not practical for everyone. Since unless you have an MSDN subscription SQL server is expensive. But anyway I am finding a lot of the Controls in C# and .net to be much more efficient for this.

Anyway just curious if there is anyone else experimenting with this at this time?

[kathgar]

I am not convinced of any benefit of this. Yes, mysql is less mature than MSSQL. However, i do not think it is any faster. You also really can't run our code slow. If the main loop takes too long, you'll probably kill all of your clients. Then there is the whole thing about it being designed to be portable in the first place... I guess i'd still be interested to look at it, but certainly don't expect it to get into the mainline without some serious proof of merits

[duckilama]

If you had a _buttload_ of memory, you could use XML files instead of SQLServer (or MSDE), load them into .NET DataSets and do all the work from there. By the same token, if you've got that much memory, you could do the same from any "database".

Being an at-work .NETter(and a fan of anything MS for the first time), I think it would be a fun exercise to get EQEmu running as a Managed App, but just like Java(or any other managed environment) that management comes with a price.
I'd be interested in mucking around on a EQEmu.NET project, but I wouldn't expect it to perform well enough to actually become the main fork, or even a "recognized" fork.