vsphp

I'm in the process of moving our VSIP package to Orcas. I quickly ran into a problem compiling the header files.

The issue is with __RPC__deref_out not been recognized. The header file generating the issue is designer.h that comes with Orcas VSIP SDK

Here is the error output for one of the instances where this is generated:

c:\svn-debug\vs.php\common\inc\designer.h(170) : error C2143: syntax error : missing ')' before 'type'
c:\svn-debug\vs.php\common\inc\designer.h(170) : error C2081: '__RPC__deref_out' : name in formal parameter list illegal
c:\svn-debug\vs.php\common\inc\designer.h(170) : error C2143: syntax error : missing ';' before 'type'
c:\svn-debug\vs.php\common\inc\designer.h(170) : error C2059: syntax error : ')'

Any suggestions

I can't wait to get VS.Php running on Orcas.

Thanks


Re: Visual Studio Extensibility Moving to Orcas

Ed Dore

Are you using the latest Orcas CTP drop of the Visual Studio SDK (April '07), and Orcas Beta1

This particular header file (designer.h) is typically included by way of the vsshell.h, which in turn is usually included in your precompiled header.

In looking at designer.h (line 170), I'm wondering why this is erroring out here. The IActiveDesignerVtbl definition is located in a conditional #if defined block, that should not be active if you are compiling a C++ file.

Note, the Figs sample includes the vsshell.h without any problems, so I'm, guessing that the above error is probably due to a bad compiler setting or where/how you are including the designer.h in your project. That being said, __RPC__deref_out is defined in Rpcsal.h, so you could also try setting the Advanced "Show Includes" setting to true, on both your Orcas and Whidbey builds, and see if you can discern a difference in the ordering of the various include files leading up to designer.h and rpcsal.h.

Sincerely,






Re: Visual Studio Extensibility Moving to Orcas

vsphp

I'm using Orcas Beta 1 (9.0.20404.0 Beta 1) and using the May 2007 Orcas SDK.

I tried various samples including Figs and MyCLang and both are having this issue. Try compiling initguid.c which is included in both projects.

I'm going to try the June SDK.

Thanks




Re: Visual Studio Extensibility Moving to Orcas

vsphp

Figs still can't compile on June SDK. When compiling initguid.c I get the same compile errors.




Re: Visual Studio Extensibility Moving to Orcas

Ed Dore

These all compile just fine on my system (though I get an LNK4099 warning because of a bad atlsd.pdb file, and the regit post build doesn't succeed). Can you do an include trace and verify that your pulling the right headers into this project.

Use the "Show Includes" compiler option and then check the paths of the include files.

Sincerely,