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. General Programming
  3. Visual Studio
  4. sharing a code base with vc6

sharing a code base with vc6

Scheduled Pinned Locked Moved Visual Studio
csharpc++visual-studiocomdata-structures
2 Posts 2 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.
  • C Offline
    C Offline
    Chris Losinger
    wrote on last edited by
    #1

    has anyone found a good way to share a (C++) codebase between VS.net and VC6 ? i have a VC6 workspace that contains a dozen or so sub-projects (half static libs, the rest EXEs and DLLs). to satisfy all of my wonderful customers, i need to build both VC6 and VC7 versions of the static libs. right now i'm doing this the hard way: i do all my work in VC6; when i do a release, i build the VC6 versions, and save the workspace; then i copy the source tree to a new folder; open the workspace in VS.net, convert everything and rebuild. it's a surprisingly error-prone process. what i'd like is to just point both VC6 and VC7 at the same set of source files. but i'm afraid that VC7 is going to tweak the VC6 workspace/project (.dsw/.dsp) files and make my life (even more) miserable. anyone have any experience with this kind of thing? -c


    Please stand by

    ThumbNailer

    O 1 Reply Last reply
    0
    • C Chris Losinger

      has anyone found a good way to share a (C++) codebase between VS.net and VC6 ? i have a VC6 workspace that contains a dozen or so sub-projects (half static libs, the rest EXEs and DLLs). to satisfy all of my wonderful customers, i need to build both VC6 and VC7 versions of the static libs. right now i'm doing this the hard way: i do all my work in VC6; when i do a release, i build the VC6 versions, and save the workspace; then i copy the source tree to a new folder; open the workspace in VS.net, convert everything and rebuild. it's a surprisingly error-prone process. what i'd like is to just point both VC6 and VC7 at the same set of source files. but i'm afraid that VC7 is going to tweak the VC6 workspace/project (.dsw/.dsp) files and make my life (even more) miserable. anyone have any experience with this kind of thing? -c


      Please stand by

      ThumbNailer

      O Offline
      O Offline
      Oliver Anhuth
      wrote on last edited by
      #2

      Chris Losinger wrote: has anyone found a good way to share a (C++) codebase between VS.net and VC6 Yes we have. Just create a VS.NET solution and add the files from the VC6 project without copying or moving them. There is no problem from using the same source file from different projects or solutions! There are some cases where a VC6 source gives a compile error in VS.NET and in rare cases VC6 does not compile VS.NET sources. But with some minor modifications it is possible to have a cross compiler code base. Oliver

      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