MFC/VC++ to .NET ????

[Duncan Edwards Jones]

I'd have thought that the size of the framework means it is unlikely that it will be used for hardware drivers any time soon...but then I would have said that about MFC as well. You don't work for HP by any chance?

'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd

[Mike Dimmick]

MFC is generally not gaining major new features or changes in how the framework works, but it has been steadily enhanced in VS 7.0, 7.1 and 8.0 (2002, 2003, 2005) and there's no reason to suppose that this will not also happen in 9.0 (2008, Orcas). See for example MFC Updates for Vista Common Controls[^]. For an existing product using MFC, there's no reason not to continue using it.

Stability. What an interesting concept. -- Chris Maunder

[Sam_c]

if its embedded software development you do... then forget .net for your job. unless your working with CE which has a stripped .net framework i believe. if you want to have a go at .net for fun/personal use. i'd say C# if your coming from c++ background, i find it a lot easier to move between c++ and c# than VB.net and MC++ is just a pain in the a***. hey either way have fun, read a few articles give them all a go and see what you think ;)

Code Project Lounge 101 by John Cardinal

[ednrgc]

Unfortunately, I don't think .NET is a solution for device drivers at all. Too much overhead. The entire framework has to be loaded to load the driver. I think the best choice is to stay with a native compiled language, like VC++ or BC++, or even Delphi :wtf:.

[NormDroid]

I'd say WTL, it's lightweight I wouldn't bother with MFC, it's on 'limp-along' release cycle until they finally deprecate it.

Roger Irrelevant "he's completely hatstand"

[NormDroid]

I did hear (some while back) that this would be possible in future (which I don't know) versions of .net.

Roger Irrelevant "he's completely hatstand"

[ednrgc]

No matter what future versions hold, the fact remains that you have to load an entire framework before the driver loads. This is insane for drivers.

[Prakash Nadar]

mate, you have run out of options, working VC++ on .net framework is too much hard work. So you may have to start with C#, but after a couple of days writing code in C#, you will see how stupid that language is. i would stick to VC++.net, but you will find that your project manager is not too eager on performance but ease of programming, that is C# I had gone through this exact situation as yours, but luckly I found a company that works on ansi C/C++ so I have given entirely the microsoft platform.

[Rama Krishna Vavilala]

gvisgr8 wrote:

Who am I? Do you know me....

Sure! Kyle

[NormDroid]

Oh vote me down I'm only tell the truth, keep sticking with MFC and you'll be fine for a job in the future - not.

Roger Irrelevant "he's completely hatstand"

[El Corazon]

norm .net wrote:

Oh vote me down I'm only tell the truth

A case of shooting the messenger because they don't like the message?

_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)

[Member 96]

Duncan Edwards Jones wrote:

You don't work for HP by any chance?

:laugh:

---

"I don't want more choice. I just want better things!" - Edina Monsoon

[Bob Nadler]

My advice: If you want to write managed code, learn C#, not VC++.Net. VC++.Net is seriously ugly and nobody uses it. With .NET it's pretty easy straight forward to wrap your unmanaged device level code with COM Interop and use it from C#.

Bob on Medical Device Software

[Rick York]

I thought voting was a measure of agreement with the post. Apparently there are some who disagree with it.

[Lost User]

gvisgr8 wrote:

I mostly work for Hardware Drivers.(Kinda embedded)

Then MFC, C++ and .Net are totally useless.

Truth is the subjection of reality to an individuals perception