There's the MS .NET RichText box, but he wants more than that. I realized that this[^] might be what he needs. It's a new article, posted just yesterday. I haven't gotten a chance to look it over more than briefly yet, though.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi
Use the merge modules provided with your setup authoring package. If you're using a free tool to make your MSI, you may try to download the merge module from www.installshield.com or www.wisesolutions.com - I don't think that they hold any copyright on them.
Finally, I don't think that you need to deploy DCOM on anything after Windows 95.
Can MC++ produce normal CLI programs. The same platform
independant programs that C# produces?
I have done a small MC++ console program but first it
becomes huge compared to a C# program (the first was
100kb, and the second below 8kb) and while the first
seems to be only Win32 compatible the second one runs on
My question is can I use Managed C++ to do the same things
I can do with C#? I have some pretty complex algorithms
written in C++ and I want to use them in my .NET programs
but I'd prefer not to port them to C# if possible.
But also keep in mind that MC++ is not verifiable (even in non-mixed mode), and is not garaunteed to run on non-Win32 platforms as leppie is referring. This also means that the code can't be verified by the CLR and many .NET security features are circumvented.
now I am confused... but why the MC++ code is so much bigger than the one created by C#? what I did is a small console application in C#, VB.NET JScript.NET and C++ to compare what are the differences between them when compiled. The MC++ assembly looked like a mixed .exe (native and MSIL).
Is there something special that I might miss?
Zibar wrote: The MC++ assembly looked like a mixed .exe (native and MSIL).
Probably. Make sure all the files are compiled with the clr flag. Also make sure you are using multi threaded (this mite be the problem, with the entrypoint causing it to link unmanaged libs). Try compile a dll assembly rather and check again.