I know I can convert, and have been, however it is time consuming. Clearly
there is an inherent latency in conversion. I would rather stay in C++ -
land, just as C# / VB.NET programmers want to stay in theirs.
Also, I mix vanilla C++ with managed which involves a few caveats when
dealing with objects on different heaps.
The reason I mix is becuase I have a large library of C++ code which lives
perfectly happily alongside managed classes. I mainly want to use .NET for
the UI, XML classes. Yes, I could just stick to using MFC, but we all have
to start somewhere and I am happy to leave all of my backend code as C++ and
begin learning the .NET framework in small doses.
By the way, I think there is a misconception that it's significantly easier
to use the .Net framework in langauges other than C++, which simply isn't
true. I haven't run into any problems yet at all. Also, consider mixing
C++ and C#. C# obviously can't access C++ structures/classes, so moving
from C++ is a backwards step. Don't get be wrong, I really like C#, and
wouldnt use that for any code I write for web development, such as aspx, but
for desktop application development I am very happy/fast with C++. IE: Just
because I change to .NET doesn't mean I need to change languages.
So, I just want a nice .NET framework application programming reference book
on my desk, just like i've got for MFC. I would much rather invest the time
now in learning and using the .NET framework than continuing down the MFC
path.
Regards,
Shane
PS: Does anyone know how I can added my own control types to a PropertyGrid?
( In C++ ;) )
[quoted text, click to view] "Flare" <nomail@sorry.dk> wrote in message
news:u9UDGRtTEHA.3768@TK2MSFTNGP11.phx.gbl...
> > > I am a very experienced programmer migrating from MFC to the .NET
> > framework
> > > and i'm having a hard time finding good C++ code. Everything is in C#
> or
> > > VB.NET!
>
> If you are very experienced programmer you should find no problems
> converting to C# unless you have sone very good arguments choosing C++.
It´s
> rather cumbersome to use C++ in manged conditions. But if you require eg.
> multiinheritance or other c++ specialties you could be a point. But if the
> reason is that you feel "home" in C++ i think the week or two you use
> converting your knowledge is very well spend compared to the productivity
> you would gain with C#.
>
> But tells us more about way you would want to use C++.
>
> Regards
> Anders Jaocbsen
>
>