Hi,

first of all, if you browse the archives for this newsgroup (on google
groups for example) you will find that this question has been debated quite
extensively (february i think).

I say this not to chase you away, but there were so many posts (the most for
one topic this year) that you will find a lot of information and points of
view.
search for:
Is C++/CLI gaining any traction???
and
C++/CLI the fastest compiler?
read inline for the rest of my comments

Personally (this is just my opinion) I would stay away from COM.
Instead, build a .NET class library. either in C++/CLI or in C#
that way you are developing on technology that is the 'wave of the future'
(tm) and most importantly, you can use the .NET framework classes, which are
awesome.

even if you want to use COM for legacy reasons for your client application,
you can simply register your .NET class library as a COM library and It Just
Works.

if you go with .NET you have to learn quite a lot anyway. whether you go
with C++ or C#.
check out www.codeproject.com for tutorials and examples.

The C++ vs C# speed debate has been argued back and forth, an month or so
ago. (see above)
If you go with C++/CLI you can have both the .NET infrastructure and the raw
speed of C++ if you need it.
It also allows you to reuse existing C++ code, should you have any.

there are probably lots of other things to consider, but with a question
like this I think you are going to get a lot of answers :-)

Hi,

You could use both.

C++ with a C++/CLI library wrapper for the back end code and C# or any
other language for the GUI part.
IMHO it's more straightforward and somewhat easier in C# and other
managed (only) languages to code a GUI application.

The compiled C++/CLI library can be easily used from any .NET language
and additionally you have separated your GUI from the other code.
Which is a good idea anyway, since a new GUI framework will be
introduced for Vista / Windows XP - Windows Presentation Framework.
Though both frameworks will be supported side by side. And you will be
able to mix them.

I miss some features of C++ in C#, like RAII, but IHMO that's not that
relevant for the GUI part. On the other side C# compiles much faster and
offers more IDE features (better Intellisense, code snippets,
refactoring) than C++/CLI.

C++/CLI will compile to faster IL code, no doubt, but I doubt that you
will see a relevant speed difference for your managed GUI.

For a more (significant) responsive GUI (running on slow PCs) you would
have to choose a native compiler / IDE, which Microsoft offers only for
C++. But using MFC to start a new IDE isn't a good idea - IMHO. You
should IMHO choose another vendor if you want to go that way.

I would suggest you to play around somewhat with C++/CLI and C# and code
some simple GUI applications with both languages. Additionally you
should create a simple .NET library in C++/CLI and see how easy it is to
consume the managed objects / classes from any .NET language you like.
Then you can make a decision of your code.

If you need speed and supporting native code (assembly language, mixing
managed and native code) then C++/CLI is the way to go. But you can
compile this code to a library (dll) which has some C++/CLI objects
wrapping the native code. Which you would have to do anyways in a
C++/CLI only application, because you need to marshal data from and to
native code when mixing native and managed code.

Hope my post has helped somewhat.

Andre