C / C++ / MFC

15-Jan-10 0:42

Hi All,

I want to develop an 3D Image rendering software using DIRECTX which can perform some 3D Operations.My customer wants the software developed on .Net Framework.

I have experience in coding in MFC in VC6.0.If i develop an application in MFC dialog based application in Visual Studio 2008,will it be built on .Net Framework?

Also,i have done some image processing coding in C++.Basically i have some classes defined in .h and .cpp files which i want to include in the .Net application which i am going to develop.

For the above requirements should i go for VC++.Net(Forms based developed in VS 2008) application or VC++(MFC based developed in VS 2008)?

Please advice.

Thanks ,
Ashwath.

CPallini15-Jan-10 0:46

CPallini

15-Jan-10 0:46

I would use C#.
Smile | :)

LunaticFringe15-Jan-10 0:57

LunaticFringe

15-Jan-10 0:57

CPallini wrote:
I would use C#

... and OpenGL instead of DirectX ( Dead | X|

L u n a t i c F r i n g e

Rajesh R Subramanian15-Jan-10 1:14

15-Jan-10 1:14

Well, why does the customer tell you what technology to use to build a software? Shouldn't you (the developer) be suggesting what's best for accomplishing a given task?

You could wrap your C++ image processing code into a COM dll and use it from C#, instead of writing the whole thing from scratch in C#.

“Follow your bliss.” – Joseph Campbell

LunaticFringe15-Jan-10 1:28

LunaticFringe

15-Jan-10 1:28

Rajesh R Subramanian wrote:
You could wrap your C++ image processing code into a COM dll and use it from C#, instead of writing the whole thing from scratch in C#.

Why bother with COM? It's simple enough to write DLLImport statements and use a native C++ DLL as is.

L u n a t i c F r i n g e

glitteringsound17-Jan-10 21:04

glitteringsound

17-Jan-10 21:04

by writing functionalities in COM u'll be able to build it as server components and call them in any technology(e.g C#)as client and can perform out of process calling easily..
DLL's always not allow you out of process calling untill RPC which's tough to manage.

So I think writing COM dll in VC++ idea is better and integrating it with C# will blend things moore significant way..

ashwath197915-Jan-10 1:28

15-Jan-10 1:28

Thank you very much for the advice.Well,if i develop the software using
VC++(MFC) in Visual Studio 2008 IDE, will it be built on .Net framework.Why i ask is because i have good experience in VC++(MFC).

Thanks,
Ashwath.

Rajesh R Subramanian15-Jan-10 5:15

15-Jan-10 5:15

ashwath1979 wrote:
Well,if i develop the software using
VC++(MFC) in Visual Studio 2008 IDE, will it be built on .Net framework

What are you talking about? Unless you target one of those versions of the .NET framework and write managed code, your application would remain native. Just because you use the VS 2008 IDE doesn't mean your application is built on .NET framework.

“Follow your bliss.” – Joseph Campbell

ashwath197915-Jan-10 17:31

15-Jan-10 17:31

Thanks Rajesh for the answer.If i develop a VC++.Net application(Form type),will it be developed on .Net framework.

Rajesh R Subramanian15-Jan-10 18:52

15-Jan-10 18:52

You mean a managed c++ (C++/CLI) application? Then yes, it would be using the .NET framework.

“Follow your bliss.” – Joseph Campbell

ashwath197915-Jan-10 19:15

15-Jan-10 19:15

Yes, i have choosen the "windows forms application"(Managed c++/cli) type project in the "new project" menu.This is built on top of .Net framework right?

Please advice,

thanks,
Ashwath

Rajesh R Subramanian15-Jan-10 19:24

Re: 3D Software [modified]

15-Jan-10 19:24

Yes Ashwath, you're correct. If you choose the c++/cli type project, then that would be using the .NET framework.

PS (Shameless plug): May I ask you to kindly mark the helpful replies by clicking "Good Answer" on the reply posts? Smile | :)

“Follow your bliss.” – Joseph Campbell

Adam Roderick J15-Jan-10 1:16

Adam Roderick J

15-Jan-10 1:16

definitely C#.net as suggest earlier
and surely OpenGL. Smile | :)

And if you use nvidia GPU then performance of 3D rendering will be very high, [^].
But surely difficult to write the programe with GPU Smile | :)

Величие не Бога может быть недооценена.

modified on Friday, January 15, 2010 7:29 AM

Execute two classes

darshic14-Jan-10 23:50

darshic

14-Jan-10 23:50

Hi
My application is such that I have a main dialog class which interacts with the User, at the same time another complete class that performs all background functions needs to be running simultaneously.
Please suggest a method of how that can be executed. On start of application both classes have to be initialised. The background class cannot be called by a button or any other user interface method.

Thanks a ton
Regards
Darshi

Adam Roderick J15-Jan-10 0:05

Adam Roderick J

15-Jan-10 0:05

Then you have to make two classes
one on main thread, and another on worker thread.
Where main thread should interact with the user actions, while the background processing is done by worker thread.
On the OnInitdialog of main dialog, you can start the worker thread.

Worker thread can be created using AfxbeginThread or CWinthread [^]

Величие не Бога может быть недооценена.

darshic15-Jan-10 0:15

darshic

15-Jan-10 0:15

Thanks adam
can you also help me with the syntax of the thread function and how the class should be called from the thread function

Adam Roderick J15-Jan-10 0:24

Adam Roderick J

15-Jan-10 0:24

hey drishi, just google it.
well, just check this stuff Simple Multithreaded Application in pure C, Win32 and MFC[^]

Величие не Бога может быть недооценена.

Rajesh R Subramanian15-Jan-10 1:09

15-Jan-10 1:09

Multithreading is a fairly complex subject. While you may get away writing multithreaded code by reading online articles, I strongly recommend that you read a book chapters devoted to this subject.

“Follow your bliss.” – Joseph Campbell

Rajesh R Subramanian15-Jan-10 1:08

15-Jan-10 1:08

Adam Roderick J 09 wrote:
Worker thread can be created using AfxbeginThread or CWinthread [^]

If a worker thread is what is needed, then AfxBeginThread() and a thread function is the ONLY correct way to go (as far as MFC usage is concerned).

Deriving from CWinThread is needed only when a message pump for the thread is needed (so called "UI thread").

“Follow your bliss.” – Joseph Campbell

CPallini15-Jan-10 0:19

CPallini

15-Jan-10 0:19

As already suggest, you should use a worker thread. Have a look at the classic J.M.Newcomer's article: "Using Worker Threads".
Smile | :)

Mattias G15-Jan-10 1:34

Mattias G

15-Jan-10 1:34

I would not recommend multi-threading. Don't go there, it won't do you any good. If you need to perform several tasks at once, you are MUCH better off using "idle time processing" using CWinApp::OnIdle() and calling Continue() in the worker object where you perform one little piece of work each time, using a state variable or similar.

Multi-threading should be avoided at all costs. It's hopeless to debug, a maintenance nightmare and you get absolutely no performance benefits from it, except in very special cases (number crunching on a multi CPU, low-level drivers or things like that). Do not use multi-threading, I cannot stress this enough. I speak from bitter experience Smile | :)

Cedric Moonen15-Jan-10 2:23

Cedric Moonen

15-Jan-10 2:23

Mattias G wrote:
Multi-threading should be avoided at all costs. It's hopeless to debug, a maintenance nightmare and you get absolutely no performance benefits from it, except in very special cases (number crunching on a multi CPU, low-level drivers or things like that). Do not use multi-threading, I cannot stress this enough. I speak from bitter experience Smile
Quote Selected Text

I don't agree at all... Mutli-thread can't be avoided in some cases. Of course, you shouldn't overuse it but there are a lot of cases where it simply can't be avoided.
I agree that this is something hard to learn and difficult to debug but it is sometimes necessary. If it was that bad, why would it be so widely used ?

Cédric Moonen
Software developer

Charting control [v3.0 - Updated]
OpenGL game tutorial in C++