ATL工程抉择合并PS，合并之后的stub功能在什么文件里面实现呢
ATL工程选择合并PS，合并之后的stub功能在什么文件里面实现呢?
所谓合并proxy/stub代码，只是PS的工程没有了，但是有PS工程的时候会有一个xxx_p.c文件的，合并之后
xdlldata.c的内容比dlldata.c的内容还要少啊。这个proxy/stub在哪里?
------解决方案--------------------
http://stackoverflow.com/questions/9582733/what-is-the-foops-project-in-my-foo-atl-solution-for
选择了就帮你做Marshal，不选就用default的
*PS project contains implementations for Proxy and Stub. They are not standard, instead they are generated by MIDL for interfaces exported from your ATL server. These interfaces are declared in the *.IDL file. The ouput of the project is DLL. You may read this article to get more details.
You may remove PS project from the solution in case if you do not define any custom interfaces in you *.IDL file or if you define only interfaces which have dual and oleautomation modifiers. In that case a standard typelib marshaller will be used.
所谓合并proxy/stub代码，只是PS的工程没有了，但是有PS工程的时候会有一个xxx_p.c文件的，合并之后
xdlldata.c的内容比dlldata.c的内容还要少啊。这个proxy/stub在哪里?
------解决方案--------------------
http://stackoverflow.com/questions/9582733/what-is-the-foops-project-in-my-foo-atl-solution-for
选择了就帮你做Marshal，不选就用default的
*PS project contains implementations for Proxy and Stub. They are not standard, instead they are generated by MIDL for interfaces exported from your ATL server. These interfaces are declared in the *.IDL file. The ouput of the project is DLL. You may read this article to get more details.
You may remove PS project from the solution in case if you do not define any custom interfaces in you *.IDL file or if you define only interfaces which have dual and oleautomation modifiers. In that case a standard typelib marshaller will be used.