Re: VC++ and .NET
I would like to know if it make sense to use .NET component in VC++ MFC
application.
Using .NET components in a native application (using mixed mode code) makes
perfect sense for components that are easy to use in .NET and have no native
alternative. Of course, each native - managed transition carries a
performance overhead, so having hundreds of transitions per second would
kill your performance stone dead.
It is ideal for low frequency things, for example if you want to use the
email or event log component.
For example, I've seen that Ahead Nero software integrate the menu strips
which are in .NET, however the rest of application seems to be in pure
VC++ and ATL.
That is because Ahaed Nero probably has a codebase that is several hundreds
of thousands of lines of C++ code.
Companies do not want to waste that, nor should they.
The best strategy is to extend existing codebases with new functionality
where required.
Rewriting a large app in .NET is a huge cost, and the end result will be
more buggy than the current version.
And it is not .NET apps will get you more sales.
I'm afraid about .NET because everything can be decompiled without any
trouble via .NET reflector and therefore everybody are able to read your
code.
This point is from my point of view a breach in registering application as
patent or license.
Or is there any solution ?
Sigh...
We had that discussion over the last couple of days in your original thread.
Please don't start it over again. If you feel that your question has not
been answered, follow up in the original thread.
--
Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"