Another example of having to go down to win32 dlls was for inter-process
communication. I don't know why .Net does not have this built-in. I had to
revert back to native SendMessage and WM_COPYDATA to get that functionality.
AliR.
I've been programming C++/MFC for 18 years now, and have done some C# from
time to time in the past 5 years. I've found that development tools for
C# are a little more technologically advanced than for C++ programming in
VS. But I have ran into roadblock after roadblock with C# with things that
I'm working on. It almost seems like I have to revert to win32 calls in
C# to get anything complex done.
You can see my latest problem here:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=378161
The bad thing is that if I have to revert to win32 then I'm bypassing
.Net, which I thought was the point of switching to C#
With all that said, when we are ready to develop a new version of our
application, I'm going to switch to C#.
AliR.
"SteveR" <maxsrussellatremovethisembarqmail.com> wrote in message
news:%23zG93NKuJHA.3848@TK2MSFTNGP02.phx.gbl...
An IT guy where I work asked me today why I am using C++ when I could be
using C#.
He is experienced with C++ and says that C# saves so much time and that
there basically is no longer any reason to be working in C++, at least in
most circumstances. From what I know of him, he does a very fine job in
all respects of his job. So I value his opinions, but I also am real
interested in what responses I might get to his question/statement from
this newsgroup.
SteveR