Click to See Complete Forum and Search --> : Calling all experienced .Net developers


Vaderman
July 19th, 2004, 08:40 AM
I'm in a quandry as to what to do. I have a few ideas already, but I feel that its long winded and error prone.

[Scenario] I have about 70+ classes all written in unmanaged VC++ code that needs to be rewritten for the purposes of C#. Each of these classes generates their own .Lib file after compilation.

My thoughts that I can write wrapper code for each of these classes, but this, I feel, is rather long winded and subject to buggy code along the way.
Another way is I can port the code over to COM objects, but after reading about such a possiblility, I feel that, again, is prone to errors, complex in itself and the overhead in speed can impact on the general running of the app - mainly thru InterOp.

If I go through with writing wrappers (urghhh!!) then there rises another question : How do we rid ourselves of MFC such as CLists, CArrays? How I see this is writing wrapper code to interact with these MFC classes themselves!

I have ordered myself a couple of books that deal with Managed Extensions, but I wanted to find out what experience other people have had and what is the best approach.

Best Regards

DNA5122
August 3rd, 2004, 01:02 PM
Would it be possible to just rewrite the classes?

Vaderman
August 3rd, 2004, 01:16 PM
That rather would be defeating the whole point of .NET migration. :rolleyes:

DNA5122
August 3rd, 2004, 01:21 PM
Fresh starts...