Welcome to MSDN Blogs Sign in | Join | Help

March 2009 - Posts

If you have started using Web Services API and building either clients to web services or web services in native code, here is an event where the product team that works on the API can help you. On May 19-21 there will be WWSAPI-specific "virtual lab" Read More...
If you have attended MIX 2009, you may already know that with Windows Azure Tools and SDK March 2009 CTP it is now possible to bring native C/C++ code onto the Azure Services cloud. If you are like me who was not at MIX 2009, you may find a compilation Read More...
If you speak Italian, there are two great resources to learn more about connecting your native C/C++ code and web services. Raffaele Rialdi has started series of posts on his blog about how to use API for building both web services and clients to them Read More...
If you are interested in learning more about Windows Web Services API and how to use them to connect native code and web services, here are the upcoming events for you. 1. Microsoft Virtual TechDays for Developers take place on April 1, 2009. You can Read More...
I have seen several questions about how to fill out a binding template for CreateServiceProxy(). Here are two examples which I believe should help you with this task. In the first example, I increase the size of messages allowed for the client to send Read More...
I have uploaded the solution I have been using during MVP summit to demonstrate Windows Web Services API. This solution demonstrates that using WWSAPI, it is possible two build both clients and web services completely in native code. Both clients and web services built using WWSAPI can interoperate with WCF based clients and web services and exchange data between them. Avoiding managed-native code Interop when it comes to presenting a native code computational engine as a web service can have significant performance advantages. In this demo, the native code wrapper of the native code computational engine is 4-6 times faster than managed code wrapper because of the cost of managed-native code interop. You may download the solution from MSDN Code Gallery page and find instructions for building and running it in the post. Read More...
 
Page view tracker