From: Nick on
Hi there,

I've just ported a C++ project from VS 2005 onto vs 2008, completely fresh
PC with all the same SDK's installed and configured that I was using with VS
2005.

Unfortunately on compilation I am told that "__RPC_in" causes a syntax
error, after Googling I found that apparently it is included in the header
file "rpcsal.h", though why I didn't need to include this before I have no
idea.

After including this just before "wmsdk.h" I recieve a new error saying that
"PROPERTYKEY" is causing a syntax error, again I googled to find that it is
included in "wtypes.h". After including this just before "rpcsal.h" the
errors remain.

Unfortunately there seems to be a massive different with the Platform SDK
for VS 2005 and VS 2008, which I kind of expected, but why it has to cause
so many problems I have no idea. At current my list of Include paths go as
follows,

....

C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include
C:\Program Files\Microsoft Platform SDK for Windows Server 2003
R2\Samples\Multimedia\DirectShow\BaseClasses
C:\WTL80\include
C:\Program Files\Microsoft DirectX SDK (December 2006)\Include
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(WindowsSdkDir)\include
$(FrameworkSDKDir)include
C:\WMSDK\WMFSDK11\include

....

If I shift around WMFSDK11 include directory the list of errors changes but
doesn't go away, so what I tried doing was exclusively including the path to
the WMFSDK "wtypes.h" & "rpsal.h" which in turn causes more problems.

I have these paths in exactly the same order that I do on the VS 2005 system
with the exception that WMFSDK11 becomes WMFSDK95, I only changed it to 11
to see if it would resolve this issue.

Any idea what I'm doing wrong? The application uses DirectShow, and
WindowsMedia and is targeted at XP SP2 and above.

Thanks a million for any help in advance!

Nick.



From: Nick on
Ahaaaa!! I've got it compiling now without error...

> C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003
> R2\Samples\Multimedia\DirectShow\BaseClasses
> C:\WTL80\include
> C:\WMSDK\WMFSDK95\include
> C:\Program Files\Microsoft DirectX SDK (December 2006)\Include
> $(VCInstallDir)include
> $(VCInstallDir)atlmfc\include
> $(WindowsSdkDir)\include
> $(FrameworkSDKDir)include

^Corrected Include list...

"Nick" <a(a)a.com> wrote in message
news:%23FFRWu5oIHA.4904(a)TK2MSFTNGP03.phx.gbl...
> Hi there,
>
> I've just ported a C++ project from VS 2005 onto vs 2008, completely fresh
> PC with all the same SDK's installed and configured that I was using with
> VS 2005.
>
> Unfortunately on compilation I am told that "__RPC_in" causes a syntax
> error, after Googling I found that apparently it is included in the header
> file "rpcsal.h", though why I didn't need to include this before I have no
> idea.
>
> After including this just before "wmsdk.h" I recieve a new error saying
> that "PROPERTYKEY" is causing a syntax error, again I googled to find that
> it is included in "wtypes.h". After including this just before "rpcsal.h"
> the errors remain.
>
> Unfortunately there seems to be a massive different with the Platform SDK
> for VS 2005 and VS 2008, which I kind of expected, but why it has to cause
> so many problems I have no idea. At current my list of Include paths go
> as follows,
>
> ...
>
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003
> R2\Samples\Multimedia\DirectShow\BaseClasses
> C:\WTL80\include
> C:\Program Files\Microsoft DirectX SDK (December 2006)\Include
> $(VCInstallDir)include
> $(VCInstallDir)atlmfc\include
> $(WindowsSdkDir)\include
> $(FrameworkSDKDir)include
> C:\WMSDK\WMFSDK11\include
>
> ...
>
> If I shift around WMFSDK11 include directory the list of errors changes
> but doesn't go away, so what I tried doing was exclusively including the
> path to the WMFSDK "wtypes.h" & "rpsal.h" which in turn causes more
> problems.
>
> I have these paths in exactly the same order that I do on the VS 2005
> system with the exception that WMFSDK11 becomes WMFSDK95, I only changed
> it to 11 to see if it would resolve this issue.
>
> Any idea what I'm doing wrong? The application uses DirectShow, and
> WindowsMedia and is targeted at XP SP2 and above.
>
> Thanks a million for any help in advance!
>
> Nick.
>
>
>