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. Porting VC++ 6.0 -> VC++.net 2003 Help Requested

Porting VC++ 6.0 -> VC++.net 2003 Help Requested

Scheduled Pinned Locked Moved C / C++ / MFC
helpcsharpc++sysadminquestion
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.
  • L Offline
    L Offline
    Larry J Siddens
    wrote on last edited by
    #1

    So far so good in porting our code from 6.0 to .net2003. I have done a small part of this so far and most of the problems can be easly corrected. But, one item that I'm not having any success with is a define that is used in one of our files. The PR_EMS_AB_PROXY_ADDRESSES is defined in the EMSABTAG.H file in \VC98\Include. The problem is that .net2003 does not use the same file. After looking up this define in the MSDN library, I see that is is now part of the Exchage Server SDK. I cannot find any downloads from the MSDN site (guess M$ wants $$ for this SDK!) so the problem can be fixed. Does anyone out there who has ported from 6.0 to .net or someone developing with the .net using this define? If so, what do I need to use to get this to compile and keep the functionality? Thank You In Advance Larry J. Siddens Cornerstone Communications TAME THE DOCUMENT MONSTER www.unifier.biz

    V 1 Reply Last reply
    0
    • L Larry J Siddens

      So far so good in porting our code from 6.0 to .net2003. I have done a small part of this so far and most of the problems can be easly corrected. But, one item that I'm not having any success with is a define that is used in one of our files. The PR_EMS_AB_PROXY_ADDRESSES is defined in the EMSABTAG.H file in \VC98\Include. The problem is that .net2003 does not use the same file. After looking up this define in the MSDN library, I see that is is now part of the Exchage Server SDK. I cannot find any downloads from the MSDN site (guess M$ wants $$ for this SDK!) so the problem can be fixed. Does anyone out there who has ported from 6.0 to .net or someone developing with the .net using this define? If so, what do I need to use to get this to compile and keep the functionality? Thank You In Advance Larry J. Siddens Cornerstone Communications TAME THE DOCUMENT MONSTER www.unifier.biz

      V Offline
      V Offline
      valikac
      wrote on last edited by
      #2

      Check out Microsoft Platform SDK. http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ Kuphryn

      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