MFC or.NET

[Guest]

I am making a new application (server) which will beserving about 10,000
peopleand i would like to know if .NET is ssuitable language to make this
server .
Iwas thinking about making it inC++ with the winsock2 API and use MFC to
make the client.
Also i would like to know if MFC is suitable to make new applications.

Thank you..

 

[Peter van der Goes]

I am making a new application (server) which will beserving about 10,000
peopleand i would like to know if .NET is ssuitable language to make this
server .
Iwas thinking about making it inC++ with the winsock2 API and use MFC to
make the client.
Also i would like to know if MFC is suitable to make new applications.

Thank you..

Here is a recent article that should help you assess the future viability of
MFC:

http://msdn.microsoft.com/visualc/whidbey/mfc2005/default.aspx

 

[Lloyd Dupont]

C# would handle the load without any trouble and you would be way more
productive.
In fact C# is usually much more productive than C++ and have performance
varying from 95% to 105% of native C++ code, depending on what you do.

C++, ManagedC++ I would say, makes only sense if:
- 1. you already know it and adamandtly don't want to move to C# (mistake).
- 2. want to tap into huge or complex legacy C API, in which case it's more
productive than C# as you don't spend endless time writing the PInvoke
declaration (which could be quite tricky sometimes).

 

[Olaf Baeyens]

I am making a new application (server) which will beserving about 10,000

peopleand i would like to know if .NET is ssuitable language to make this
server .
Iwas thinking about making it inC++ with the winsock2 API and use MFC to
make the client.
Also i would like to know if MFC is suitable to make new applications.

First of all .NET programs are far more secure without having to do a lot of
effort, because the security is built inside it.

MFC programs might be a little faster but the time you design it wil be a
factor of 5-7 times longer than when you would do it in C#. And also
extending it is a nightmare in MFC, but in .NET it is simpler.

Any speed loss could be caught by writing parts in managed/unmanaged C++.
But notice that the C# compiler is lightning fast compared to the C++
compiler when your project gets big as the projects I have here.

Tests here regarding to .NET programs is that I lose about 5% speed compared
to none-.NET. SOme things are even faster (because of the libraries) some
things are slower.

I hope this helps?