Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. MFC/VC++ to .NET ????

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

Scheduled Pinned Locked Moved The Lounge
c++hardwarecsharpdotnetquestion
16 Posts 13 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G gvisgr8

    I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

    E Offline
    E Offline
    ednrgc
    wrote on last edited by
    #5

    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:.

    N 1 Reply Last reply
    0
    • G gvisgr8

      I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

      N Offline
      N Offline
      NormDroid
      wrote on last edited by
      #6

      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"

      N 1 Reply Last reply
      0
      • E 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:.

        N Offline
        N Offline
        NormDroid
        wrote on last edited by
        #7

        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"

        E 1 Reply Last reply
        0
        • N 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"

          E Offline
          E Offline
          ednrgc
          wrote on last edited by
          #8

          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.

          1 Reply Last reply
          0
          • G gvisgr8

            I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

            P Offline
            P Offline
            Prakash Nadar
            wrote on last edited by
            #9

            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.

            1 Reply Last reply
            0
            • G gvisgr8

              I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

              R Offline
              R Offline
              Rama Krishna Vavilala
              wrote on last edited by
              #10

              gvisgr8 wrote:

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

              Sure! Kyle

              1 Reply Last reply
              0
              • N 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"

                N Offline
                N Offline
                NormDroid
                wrote on last edited by
                #11

                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"

                E 1 Reply Last reply
                0
                • N 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"

                  E Offline
                  E Offline
                  El Corazon
                  wrote on last edited by
                  #12

                  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)

                  R 1 Reply Last reply
                  0
                  • D 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

                    M Offline
                    M Offline
                    Member 96
                    wrote on last edited by
                    #13

                    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

                    1 Reply Last reply
                    0
                    • G gvisgr8

                      I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

                      B Offline
                      B Offline
                      Bob Nadler
                      wrote on last edited by
                      #14

                      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

                      1 Reply Last reply
                      0
                      • E 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)

                        R Offline
                        R Offline
                        Rick York
                        wrote on last edited by
                        #15

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

                        1 Reply Last reply
                        0
                        • G gvisgr8

                          I am currently working in VC++(MFC) .I am a bit confused over Microsoft's attitude towards MFC. They are stressing now more on their .NET framework. I am planning to try my hand on .NET also but don't know where to start. What could be successor of MFC/VC++ . Whether I should start with VC++.Net or something else. I mostly work for Hardware Drivers.(Kinda embedded)

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

                          L Offline
                          L Offline
                          Lost User
                          wrote on last edited by
                          #16

                          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

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups