Re: Compiling the Exchange 2003 SDK

I find it odd that you'd ask this considering you already referenced the
answer in another thread:
I wrote that response based on my opinion, and a few other people's comments
(also opinions).It is important for me to have my facts correct, it's nice
to get information closer to the source.

Thanks,

Russ Mangel

"Stephen Griffin [MSFT]" <sgriffin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ejao8rzJGHA.648@xxxxxxxxxxxxxxxxxxxxxxx
I find it odd that you'd ask this considering you already referenced the
answer in another thread:
http://blogs.msdn.com/jasonjoh/archive/2004/08/01/204585.aspx

Use the old EDK as a reference. Don't link in the lib files. And we
haven't touched the old projects in years, don't know why we'd start
changing them now.
"Russell Mangel" <russell@xxxxxxxxx> wrote in message
news:O0PUqZtJGHA.3260@xxxxxxxxxxxxxxxxxxxxxxx
Could you elaborate a bit on this for me and all the new people who wish
to learn MAPI?

1. Does Microsoft encourage the use of the Exchange 2003 SDK
(Specifically the C++ .lib (library files)). Or does Microsoft recommend
that we use it only for a reference and use pieces of ideas/source code?
In short, should we use it? Your opinion?
2. Will Microsoft add new methods to the SDK, using VC 6.0, in the
future? I understand that the project will not be converted to new
versions of Visual Studio. In short, is the VS 6.0 project absolutely
frozen?

Thanks,
Russell Mangel

"Stephen Griffin [MSFT]" <sgriffin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%239e9TinJGHA.3904@xxxxxxxxxxxxxxxxxxxxxxx
The project is still in Visual Studio 6.0 because we haven't touched it
in years. We have no plans on updating it.

"Russell Mangel" <russell@xxxxxxxxx> wrote in message
news:OcdulljJGHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
I downloaded the Exchange Exchange 2003 SDK Documentation and Samples
June 2005 from:
http://www.microsoft.com/downloads/details.aspx?familyid=bc9ce968-7fc5-40b6-9def-37f11bee0d22&displaylang=en

I have noticed that the Exchange SDK project is still in Visual Studio
6.0 format. I tried compiling it using Visual Studio 2005 RTM, it will
not compile.

I don't understand why the project is still in Visual Studio 6.0, as it
has been deprecated 9/30/2005. MainStream support ended 9/30/2004.
http://support.microsoft.com/lifecycle/?p1=3003

Will this be fixed in the near future?

Thanks
Russell Mangel
Las Vegas, NV












.

Relevant Pages

  • Re: .NET 3.0 Framework and VS.NET 2003
    ... need to be running Visual Studio 2005 with SP-1, and Windows XP with SP-1 ... Installing the Software Required to Work With WPF and WCF Applications ... Download and install the Windows SDK. ...
    (microsoft.public.dotnet.general)
  • Re: C compiler v15.x vom SDK bzw. Visual Studio
    ... Es ist so das ab diesem SDK auch gar kein VC ... zu setzen und so auch Visual Studio, ... laesst sich leider auch nicht waehrend der Installation auswaehlen. ... kenne mich damit aber nicht so aus) dass fuer die VC Komponenten vom ...
    (microsoft.public.de.vc)
  • Re: VS7.NET and TAPI classes
    ... "Kevin Blackwell" schrieb im Newsbeitrag ... I have 3 development directories. ... > C:\Program Files\Microsoft Visual Studio ... >> From the Microsoft SDK directory. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: Evaluating D2005, help needed.
    ... on machines that are limited to 512 MB. ... Visual Studio is going to be very much fun on such limited machines either, ... be faced there than just the choice of dev tool, if I may be so bold. ... Everything in this post is mere opinion. ...
    (borland.public.delphi.non-technical)
  • SmartPhone C# build fails
    ... I installed the SmartPhone 2003 SDK yesterday and I'm having trouble ... I'm using Visual Studio .NET 2003 on a WinXP Pro machine. ... Smartphone, ... repairing my Visual Studio install, and adding the SDK back in - but ...
    (microsoft.public.dotnet.framework.compactframework)