VC++6 MFC migration managed C++(windows form )

[Bredal Jensen]

I want to port my MFC (VC++6) application to manageg VC ++. 7. I want to do
this because some things are much better done with C#. So i could write a C#
class and use in
my VC++ code as Languague interoperabilit y is one of the main features of
the .Net
framework. I know my application would have to obey to the CTS (common type
specification) but my main concerns are the MFC stuff!
I do not really know which options you have with windows forms. Can they do
what MFC
can do? How about functions pointers. How does managed C++ deal with this?
Maybe this is not the right place to post this, but any usefull comment will
be very
appreciated.

Thanks

[Bredal Jensen]

What i want to do:

I was once C++ addict but since i tried C#, i just don't want to use
too much of C++ anymore.
I have this huge MFC application and it needs new features. I then want to
do all
new developement in C# and work my way through like this.

An alternative is a whole rewrite in C# , but it does not seem like our
budget
allow this for now.
So here is what want to do. Did that sound Crazy? ;)


"Niki Estner" <ni*********@cu be.net> skrev i en meddelelse
news:eo******** ******@tk2msftn gp13.phx.gbl...

"Bredal Jensen" <br****@jensen. dk> wrote in
news:O9******** ******@TK2MSFTN GP11.phx.gbl...

Now my program compiles as manages C++ and actually runs.
Is that all i had to do to run as managed C++?
It's not 100% managed code yet, but you can reference managed assemblies

and create managed types. The possibility to have managed and unmanaged code in one assembly is one of the major advantages of managed C++. The price is
that you often have to use keywords like __gc or __value to tell the
compiler which way to go.

Well i must say your informations are very accurate and i'm
really thankfull for all these help.

I still have questions though. I now decided to write one of my user
interface part as a C# "windows control" .

I need to do the equivalent of (Postmessage or SendMessage) plus send data like with (wParam and lParam) . Is there a way of doing this?

You can still P/Invoke SendMessage and PostMessage with the DllImport
attribute, and every control has a protected virtual method "WndProc".
However, it's usually a bad idea to use them if you can avoid it: First of
all, those "wParam/lParam" parameters tend to disturb the GC if they carry
pointers; They are ugly to debug, and error-prone.
Depending on what you want to do, I'd suggest having a deeper look at
events, delegates, interfaces (for loose-coupling), or the Control.Invoke
method (for inter-thread communication).

Niki

[Niki Estner]

"Bredal Jensen" <br****@jensen. dk> wrote in
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

What i want to do:

I was once C++ addict but since i tried C#, i just don't want to use
too much of C++ anymore.
I have this huge MFC application and it needs new features. I then want to
do all
new developement in C# and work my way through like this.

An alternative is a whole rewrite in C# , but it does not seem like our
budget
allow this for now.
So here is what want to do. Did that sound Crazy? ;)

No: thanks to managed C++ you can port an application step-by-step without
pain.
But you should always keep the architecture of your application in mind: If
you have to add a new feature which you would have put into a separate DLL
anyway, fine write it in managed code. However, if you have to add a feature
to an existing class, you should either write it in C++, or port the whole
class (or maybe even bigger chunks of your application) to C#. Otherwise
your application will be a mess quite soon.
Also, you should identify parts of your application that would profit most
from .NET (especially the ones that are bound to change), and port them to
C# when you have the time (you'll be lucky you did when you don't have the
time any more).

I think that's a good way to go, and if you do it right, it should save you
lots of time.

Niki

[Bredal Jensen]

well , i'm mostly going to build "windows control library" and use "Add
reference" and instantiate the classes.
Actually i though i could also just instantiate a C# class not in a binary
form. shouldn't that in theory be possible?


"Niki Estner" <ni*********@cu be.net> skrev i en meddelelse
news:uZ******** ******@tk2msftn gp13.phx.gbl...

"Bredal Jensen" <br****@jensen. dk> wrote in
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

What i want to do:

I was once C++ addict but since i tried C#, i just don't want to use
too much of C++ anymore.
I have this huge MFC application and it needs new features. I then want to do all
new developement in C# and work my way through like this.

An alternative is a whole rewrite in C# , but it does not seem like our
budget
allow this for now.
So here is what want to do. Did that sound Crazy? ;)
No: thanks to managed C++ you can port an application step-by-step without
pain.
But you should always keep the architecture of your application in mind:

If you have to add a new feature which you would have put into a separate DLL
anyway, fine write it in managed code. However, if you have to add a feature to an existing class, you should either write it in C++, or port the whole
class (or maybe even bigger chunks of your application) to C#. Otherwise
your application will be a mess quite soon.
Also, you should identify parts of your application that would profit most
from .NET (especially the ones that are bound to change), and port them to
C# when you have the time (you'll be lucky you did when you don't have the
time any more).

I think that's a good way to go, and if you do it right, it should save you lots of time.

Niki

[Niki Estner]

"Bredal Jensen" <br****@jensen. dk> wrote in
news:ux******** ******@tk2msftn gp13.phx.gbl...

well , i'm mostly going to build "windows control library" and use "Add
reference" and instantiate the classes.
use the "new" operator to instantiate classes. adding a reference only makes
the classes in an assembly visible, it doesn't instantiate them yet.
Actually i though i could also just instantiate a C# class not in a binary
form. shouldn't that in theory be possible?

The C# class would have to be compiled, so it has to be in a binary form;
You can compile it at runtime, but I'm not sure if that's what you mean.

Niki

[Bredal Jensen]

What i mean is :

making my C# class available to a c++ class with:
"using Mynaspace.Mycla sss "

and Myclass mc = new Myclass(....


"Niki Estner" <ni*********@cu be.net> wrote in message
news:un******** ******@TK2MSFTN GP14.phx.gbl...

"Bredal Jensen" <br****@jensen. dk> wrote in
news:ux******** ******@tk2msftn gp13.phx.gbl...

well , i'm mostly going to build "windows control library" and use "Add
reference" and instantiate the classes.
use the "new" operator to instantiate classes. adding a reference only

makes the classes in an assembly visible, it doesn't instantiate them yet.

Actually i though i could also just instantiate a C# class not in a binary form. shouldn't that in theory be possible?

The C# class would have to be compiled, so it has to be in a binary form;
You can compile it at runtime, but I'm not sure if that's what you mean.

Niki

[Bredal Jensen]

An other issue.
Now that my code is Dot net "ready"
i though i could just use fx: using System.Net . in my C++ file.
But that does not seem to work. I recall you saying my code
was not 100% manged . is that why i can not do this?


"Bredal Jensen" <Br***********@ mimosa.com> skrev i en meddelelse
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

What i mean is :

making my C# class available to a c++ class with:
"using Mynaspace.Mycla sss "

and Myclass mc = new Myclass(....


"Niki Estner" <ni*********@cu be.net> wrote in message
news:un******** ******@TK2MSFTN GP14.phx.gbl...

"Bredal Jensen" <br****@jensen. dk> wrote in
news:ux******** ******@tk2msftn gp13.phx.gbl...

well , i'm mostly going to build "windows control library" and use "Add reference" and instantiate the classes.

use the "new" operator to instantiate classes. adding a reference only

makes

the classes in an assembly visible, it doesn't instantiate them yet.

Actually i though i could also just instantiate a C# class not in a binary form. shouldn't that in theory be possible?

The C# class would have to be compiled, so it has to be in a binary form; You can compile it at runtime, but I'm not sure if that's what you mean.

Niki

[Niki Estner]

"Bredal Jensen" <br****@jensen. dk> wrote in
news:eF******** ******@TK2MSFTN GP12.phx.gbl...

An other issue.
Now that my code is Dot net "ready"
i though i could just use fx: using System.Net . in my C++ file.
Did you reference the right assemblies? I think this namespace is
implemented in System.dll - you'll have to add a reference to it.
But that does not seem to work. I recall you saying my code
was not 100% manged . is that why i can not do this?

You should be able to do this; However it is possible that you will not be
able to use managed code in some of your functions because they already
contain native code; simply create a new empty function then, put the
managed code in it , and call it from your unmanaged function.

Niki

[Bredal Jensen]

I think i have a problem my visusal studio installation. i need to do a
reinstall.
I can not even see the add reference option .

But you are right i have not added a reference to "System.dll ".

I 'll try again later when i ahve a reliable visual studion installation.

"Niki Estner" <ni*********@cu be.net> skrev i en meddelelse
news:u4******** ******@TK2MSFTN GP15.phx.gbl...

"Bredal Jensen" <br****@jensen. dk> wrote in
news:eF******** ******@TK2MSFTN GP12.phx.gbl...

An other issue.
Now that my code is Dot net "ready"
i though i could just use fx: using System.Net . in my C++ file.

Did you reference the right assemblies? I think this namespace is
implemented in System.dll - you'll have to add a reference to it.

But that does not seem to work. I recall you saying my code
was not 100% manged . is that why i can not do this?

You should be able to do this; However it is possible that you will not be
able to use managed code in some of your functions because they already
contain native code; simply create a new empty function then, put the
managed code in it , and call it from your unmanaged function.

Niki

[Niki Estner]

"Bredal Jensen" <br****@jensen. dk> wrote in
news:uO******** ********@TK2MSF TNGP11.phx.gbl. ..

I think i have a problem my visusal studio installation. i need to do a
reinstall.
I can not even see the add reference option .

Really? Select your project in the solution explorer and choose "Add
Reference" from the project menu.

You can also do the same from the source code with the "#using" preprocessor
directive.

Niki

[Bredal Jensen]

I can not see it in the project menu .
The IDE "Itself" also prompted me to reinstall .

But before i do , could you show code snippet of how to use "#using " thing.
Assum i want to get the list of my local ip/ips . I know
this can be done with Ip helper but i guess it must be much
more straight forward using .Net.

"Niki Estner" <ni*********@cu be.net> skrev i en meddelelse
news:u%******** *******@TK2MSFT NGP15.phx.gbl.. .

"Bredal Jensen" <br****@jensen. dk> wrote in
news:uO******** ********@TK2MSF TNGP11.phx.gbl. ..

I think i have a problem my visusal studio installation. i need to do a
reinstall.
I can not even see the add reference option .
Really? Select your project in the solution explorer and choose "Add
Reference" from the project menu.

You can also do the same from the source code with the "#using"

preprocessor directive.

Niki