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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. VC7 compiled projects still work on 98/ME?

VC7 compiled projects still work on 98/ME?

Scheduled Pinned Locked Moved C / C++ / MFC
questioncsharpc++helpannouncement
13 Posts 4 Posters 4 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.
  • R RickGavin

    Hi all, I asked this question a while ago and people said "yes, but I don't know how". Was looking to upgrade from using VC6 to VC.NET 2003, but I have some apps that still get used on Windows 98/ME etc. It seems like compiling with VC.NET makes the app require MFC7 to which the older windows only have MFC4.2. Is there a way to make the compiler user MFC4.2? I have been looking into the VC.NET project setttings and haven't seen anything about an MFC version to use. Thanks in advanced for any help, Rick

    D Offline
    D Offline
    David Crow
    wrote on last edited by
    #2

    If Windows 98/Me supports the .Net framework, then MFC 7.x will be installed. Does that help?


    "One must learn from the bite of the fire to leave it alone." - Native American Proverb

    R 1 Reply Last reply
    0
    • D David Crow

      If Windows 98/Me supports the .Net framework, then MFC 7.x will be installed. Does that help?


      "One must learn from the bite of the fire to leave it alone." - Native American Proverb

      R Offline
      R Offline
      RickGavin
      wrote on last edited by
      #3

      I can't require the client(s), who are large corporations in some cases, to upgrade all of their old machines. so no. I have to be able to compile the code to use the older MFC. Was just hoping there was away so i could use the new IDE. -Rick

      D 1 Reply Last reply
      0
      • R RickGavin

        I can't require the client(s), who are large corporations in some cases, to upgrade all of their old machines. so no. I have to be able to compile the code to use the older MFC. Was just hoping there was away so i could use the new IDE. -Rick

        D Offline
        D Offline
        David Crow
        wrote on last edited by
        #4

        You can successfully have both compilers on your machine at the same time. Is that an option?


        "One must learn from the bite of the fire to leave it alone." - Native American Proverb

        R 1 Reply Last reply
        0
        • D David Crow

          You can successfully have both compilers on your machine at the same time. Is that an option?


          "One must learn from the bite of the fire to leave it alone." - Native American Proverb

          R Offline
          R Offline
          RickGavin
          wrote on last edited by
          #5

          yes, I do have both VS6 and VS7 on my dev machine, but I thought it says once you open a project in VS7 it converts it and project will no longer work in VS6. Is that really the only solution, to just have both environemnts, develop in VC7, then "tweak" it to compile in VC6 when needed? -Rick

          D 1 Reply Last reply
          0
          • R RickGavin

            yes, I do have both VS6 and VS7 on my dev machine, but I thought it says once you open a project in VS7 it converts it and project will no longer work in VS6. Is that really the only solution, to just have both environemnts, develop in VC7, then "tweak" it to compile in VC6 when needed? -Rick

            D Offline
            D Offline
            David Crow
            wrote on last edited by
            #6

            Since you cannot use any of the features within VS7 (the target machine prohibits this), why would you want to convert the project to that platform?


            "One must learn from the bite of the fire to leave it alone." - Native American Proverb

            R 1 Reply Last reply
            0
            • D David Crow

              Since you cannot use any of the features within VS7 (the target machine prohibits this), why would you want to convert the project to that platform?


              "One must learn from the bite of the fire to leave it alone." - Native American Proverb

              R Offline
              R Offline
              RickGavin
              wrote on last edited by
              #7

              purely for the nicer editor. and I may be crazy, but installing VC6 on an XP machine seems to make the machine slower in general, boot, execution, etc.

              D 1 Reply Last reply
              0
              • R RickGavin

                purely for the nicer editor. and I may be crazy, but installing VC6 on an XP machine seems to make the machine slower in general, boot, execution, etc.

                D Offline
                D Offline
                David Crow
                wrote on last edited by
                #8

                RickGavin wrote: purely for the nicer editor. I suppose there's no harm in actually opening a .cpp or .h file solely for editing purposes.


                "One must learn from the bite of the fire to leave it alone." - Native American Proverb

                R 1 Reply Last reply
                0
                • D David Crow

                  RickGavin wrote: purely for the nicer editor. I suppose there's no harm in actually opening a .cpp or .h file solely for editing purposes.


                  "One must learn from the bite of the fire to leave it alone." - Native American Proverb

                  R Offline
                  R Offline
                  RickGavin
                  wrote on last edited by
                  #9

                  my development isn't only limitted to those older projects.. and i would like to get learn some of the new features offered by the newer VS7. Basically, I don't want to HAVE to have both VS6 and VS7 installed. As I said, i have seen some odd performance decreases on several machines after installing VS6 so I would like to get away from installing it on future machines. Just seems there should be a way to compile for older MFC support in VS7. that is my question, if anyone knows. -Rick

                  D 1 Reply Last reply
                  0
                  • R RickGavin

                    my development isn't only limitted to those older projects.. and i would like to get learn some of the new features offered by the newer VS7. Basically, I don't want to HAVE to have both VS6 and VS7 installed. As I said, i have seen some odd performance decreases on several machines after installing VS6 so I would like to get away from installing it on future machines. Just seems there should be a way to compile for older MFC support in VS7. that is my question, if anyone knows. -Rick

                    D Offline
                    D Offline
                    David Crow
                    wrote on last edited by
                    #10

                    RickGavin wrote: Basically, I don't want to HAVE to have both VS6 and VS7 installed. From all that I've read and seen, this is how everyone does it. RickGavin wrote: Just seems there should be a way to compile for older MFC support in VS7. that is my question, if anyone knows. I don't see how this is possible since both libraries (MFC42 and MFC7.x) export roughly the same symbols. A clash is unavoidable. You might try posing your question to the microsoft.public.dotnet.languages.vc newsgroup and see if you can get any other response.


                    "One must learn from the bite of the fire to leave it alone." - Native American Proverb

                    R 1 Reply Last reply
                    0
                    • D David Crow

                      RickGavin wrote: Basically, I don't want to HAVE to have both VS6 and VS7 installed. From all that I've read and seen, this is how everyone does it. RickGavin wrote: Just seems there should be a way to compile for older MFC support in VS7. that is my question, if anyone knows. I don't see how this is possible since both libraries (MFC42 and MFC7.x) export roughly the same symbols. A clash is unavoidable. You might try posing your question to the microsoft.public.dotnet.languages.vc newsgroup and see if you can get any other response.


                      "One must learn from the bite of the fire to leave it alone." - Native American Proverb

                      R Offline
                      R Offline
                      RickGavin
                      wrote on last edited by
                      #11

                      DavidCrow wrote: I don't see how this is possible since both libraries (MFC42 and MFC7.x) export roughly the same symbols. A clash is unavoidable. If it was possible to set at the project level to use a specific MFC version of LIBs so that the compile would export the "correct" set, then, there wouldn't be a conflict, theoretically. Upon MFC selection, then the editor would then not offer classes that don't exist for the lower specified version, didn't seem like that big of a stretch, but I suppose its MFC7 only as another thing to "make" people upgrade. I guess I have been using java to long, most everything you can just swap out newer/older versions and recompile, as long as you aren't using something "new" version specific. DavidCrow wrote: You might try posing your question to the microsoft.public.dotnet.languages.vc newsgroup and see if you can get any other response. thanks, i'll give this a try. -Rick

                      1 Reply Last reply
                      0
                      • R RickGavin

                        Hi all, I asked this question a while ago and people said "yes, but I don't know how". Was looking to upgrade from using VC6 to VC.NET 2003, but I have some apps that still get used on Windows 98/ME etc. It seems like compiling with VC.NET makes the app require MFC7 to which the older windows only have MFC4.2. Is there a way to make the compiler user MFC4.2? I have been looking into the VC.NET project setttings and haven't seen anything about an MFC version to use. Thanks in advanced for any help, Rick

                        PJ ArendsP Offline
                        PJ ArendsP Offline
                        PJ Arends
                        wrote on last edited by
                        #12

                        I got two suggestions. The first is to distribute the MFC7 files with your app. The MFC files are redistributable. Or you could statically link MFC. The second, which I have not tried, would be to copy the file Afx.h to your project directory, and include it in your stdafx.h file. The file Afx.h is the file that links the mfc libs to your app. This may or may not work, but might be worth a try.


                        "You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ???  You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!

                        Within you lies the power for good; Use it!

                        A 1 Reply Last reply
                        0
                        • PJ ArendsP PJ Arends

                          I got two suggestions. The first is to distribute the MFC7 files with your app. The MFC files are redistributable. Or you could statically link MFC. The second, which I have not tried, would be to copy the file Afx.h to your project directory, and include it in your stdafx.h file. The file Afx.h is the file that links the mfc libs to your app. This may or may not work, but might be worth a try.


                          "You're obviously a superstar." - Christian Graus about me - 12 Feb '03 "Obviously ???  You're definitely a superstar!!!" - mYkel - 21 Jun '04 "There's not enough blatant self-congratulatory backslapping in the world today..." - HumblePie - 21 Jun '05 Within you lies the power for good - Use it!

                          A Offline
                          A Offline
                          Anonymous
                          wrote on last edited by
                          #13

                          Put on VC7 directories to visual c 6 directories(IN OPTIONS) and delete the vc7 directories, then the compiler will use the old libs... include files, etc...

                          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