B
Bruce
Currently our desktop application is a large VC++ 7.1, Unmanaged, MFC
application.
We are going to be re-architecting our application and we are considering
rewriting it using C-Sharp.
So far, we have written a few pieces of our program in C# that get called
through a managed DLL. But they are used infrequently so the impact on
performance has been minimal. We wrote these pieces in C# because it was
easier to do in the short amount of time we had available. But our
experience with these components has been that the C# stuff tends to be much
more sluggish than the unmanaged MFC code in the rest of the application.
Has anyone out there had experience writing or converting a large desktop
application from MFC to C#?
Performance is a big issue with our users, so we are very concerned about
keeping our application responsive for the users.
application.
We are going to be re-architecting our application and we are considering
rewriting it using C-Sharp.
So far, we have written a few pieces of our program in C# that get called
through a managed DLL. But they are used infrequently so the impact on
performance has been minimal. We wrote these pieces in C# because it was
easier to do in the short amount of time we had available. But our
experience with these components has been that the C# stuff tends to be much
more sluggish than the unmanaged MFC code in the rest of the application.
Has anyone out there had experience writing or converting a large desktop
application from MFC to C#?
Performance is a big issue with our users, so we are very concerned about
keeping our application responsive for the users.