Server Application .net OR VC++

[batista]

Hello there,

I am currently working in .net. Now i need to know that in order to
build a server/client architecture which one is more suitable Vc++ or
..net. There is a server in our company that has been build over vc++,
now we are looking for any chances of shifting it to .net. BTW speed of
delievering messages and other networking efficiency issues are very
important. So, cud anyone give me any advice on it, or tell me
performance comparison of vc++ or .net,or tell me any link where i can
find it.

Thanks in advance..
Cheers.......

Bye

 

[Tim Haughton]

Hello there,

I am currently working in .net. Now i need to know that in order to
build a server/client architecture which one is more suitable Vc++ or
.net.

..Net excels in creating distributed components such as found in
client-server apps. It's certainly easier than doing them in C++.

There is a server in our company that has been build over vc++,
now we are looking for any chances of shifting it to .net. BTW speed of
delievering messages and other networking efficiency issues are very
important.

Well, the obvious question is "how fast does it need to be?" Assuming the
client and server are seperated by a network, the network lag will likely
swamp any differences in processing speed. If you can define how fast it
needs to be, then profile a .Net prototype. If it meets your targets, go for
it.

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton

 

[batista]

Thanks for reply,

how fast it be?
I'm not really sure by this quest, anyway i try to explain

It's a real time system, in which thousands of messages can go through
the nerwork, and any sort of delay can be troublesome.

And i also want to know that
which is better(in the same cleint/server scenario),

having a backend of vc++ and front end .net, or
having a every thing in .net

i'm a .net programmer and wud love to find sum way of having it all in
..net without
problems of speed issues,because i believe that .net is not just about
a toolbox and drag drop

Cheers...
Bye

 

[batista]

Thanks for reply,

how fast it be?
I'm not really sure by this quest, anyway i try to explain

It's a real time system, in which thousands of messages can go through
the nerwork, and any sort of delay can be troublesome.

And i also want to know that
which is better(in the same cleint/server scenario),

having a backend of vc++ and front end .net, or
having a every thing in .net

i'm a .net programmer and wud love to find sum way of having it all in
..net without
problems of speed issues,because i believe that .net is not just about
a toolbox and drag drop

Cheers...
Bye

 

[batista]

Thanks For REply,

If i'l loose performance than how can C# is better than C++
Considering my scenario of client/server

Cheers....
Bye

 

[Tim Haughton]

It's a real time system, in which thousands of messages can go through
the nerwork, and any sort of delay can be troublesome.

There will always be some delay. Any project where performance is critical
should have a benchmark specified right at the start, otherwise you end up
doing blue sky optimisation.

You know that Windows isn't a real time OS though, right?

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton

 

[Sharon]

IHMO, C# is better than C++.
But since VC++ compiles to native code, and C# to MSIL,
you will loose performance migrating to C#.

 

[batista]

Thanks Again For Reply,

I think i'm not being very clear

Man i only want to know that out of the 2 options

1)having a backend of vc++ and front end .net, or
2)having a every thing in .net

in which one will the server take more time ro process a request from a
client?

and if u(Tim Haughton) or anyone know about any web links or any
paper(not very long)
which have some performance comparisons between .net and vc++
(regarding my scenario
of client/server), then plz let me know...

And BTW(Tim Haughton),

"You know that Windows isn't a real time OS though, right? "

THANKS MAN FOR "OPENING MY EYES", I REALLY DID'NT KNEW THAT...

 

[Tim Haughton]

Man i only want to know that out of the 2 options

1)having a backend of vc++ and front end .net, or
2)having a every thing in .net

in which one will the server take more time ro process a request from a
client?

Native C++ is faster than C#. Therefore any component written in C++ will
take less time to process a request than the equivalent component in C#.

--
Regards,

Tim Haughton

Agitek
http://agitek.co.uk
http://blogitek.com/timhaughton

 

[batista]

Thanks For Reply Tim Haughton.

 

[Sharon]

As a programming languge, C# is better.
Plus, as Tim mentioned, the dot net framework is designed
to make distributed applications more easy to implement.

 

[Willy Denoyette [MVP]]

You won't start another language war don't you. Each language has it's
strengths and it's weaknesses, that valid for all of them. What's better for
you is not necessarely better for someone else, it depends highly on your
skills and the task at hand, some programming tasks can't/shouldn't simply
be done in C# (because it's not designed for the task at hand) or any other
managed language, while there might be others are better done in a managed
language, but not necessarely C#. Someone having years of experience in C++
won't/shouldn't move to C#, he can stay with C++ and at the same time take
advantage of both the the framework and the power of C++ when moving to
C++/CLI. Someone experienced in VBA who needs to interop/integrate with
Office applications is much better off when using VB.NET.

Willy.

 

[Willy Denoyette [MVP]]

Thanks for reply,

how fast it be?
I'm not really sure by this quest, anyway i try to explain

It's a real time system, in which thousands of messages can go through
the nerwork, and any sort of delay can be troublesome.

And i also want to know that
which is better(in the same cleint/server scenario),

having a backend of vc++ and front end .net, or
having a every thing in .net

i'm a .net programmer and wud love to find sum way of having it all in
.net without
problems of speed issues,because i believe that .net is not just about
a toolbox and drag drop

Cheers...
Bye

C++ is a language, .NET is NOT, so please be more explicit, .NET includes a
number of languages as from MS you can choose between C++, C# and VB.NET as
major languages. So if you have existing applications written in C++, I
don't see any reason to port these to .NET using another language, you can
migrate to the .NET environment and take advantage of the CLR and the
framework without changing the language, of course if the C++ skill-set is
rather limited and you have the intention to move to a managed language
because you think it will be easier to grasp, it could be a good move, but
you are the one to answer this question, also you should keep in mind that
the language is not key in .NET, it's the framework, start learning the FCL
learn the CLR it's features and it's non-features. Take care it's not
designed to solve all programming problems, try to find out why .NET has
been designed for and use it at your advantage, don't try to use it for
things it wasn't designed for, you will get disappointed.

Willy.